One of the steps that I run in the l10n repackages on staging-master was "autoconf" but on the mentioned slaves the autoconf points to the 2.61 version of it. I will be using the step "make -f client.mk configure --enable-application=browser" (since client.mk chooses the right autoconf) for l10n repackages to go around it but this bug is just to track this issue. Maybe the ref images should have the symlink
(In reply to comment #0) > I will be using the step "make -f client.mk configure > --enable-application=browser" (since client.mk chooses the right autoconf) for > l10n repackages to go around it but this bug is just to track this issue. > Maybe the ref images should have the symlink This is blocking for l10n I have to be able to run autoconf by either having a mozconfig with --enable-application=browser OR by having all the slaves with the symlink added properly
No longer blocks: 460791
Please determine how autoconf is setup on the xserves and do it the same way. This document should help: https://wiki.mozilla.org/ReferencePlatforms/Mac-10.5 If setting it up the same way doesn't solve your problem you should adjust your code to cope with this environment.
(In reply to comment #2) > If setting it up the same way doesn't solve your problem you should adjust your > code to cope with this environment. > The code has been adjusted in the l10n stuff, this does not block the l10n work anymore but it might be good to have the slaves set up according to the docs you mention
After some brief investigation I discovered a symlink from /opt/local/bin/autoconf-2.13 to /opt/local/bin/autoconf213. Armen, you can either create this symlink on the moz2-darwin9-* slaves, or update your code to call 'autoconf213' - either should work.
Looks like Armen fixed his code in https://bugzilla.mozilla.org/attachment.cgi?id=347383. Armen, in the future, can you update relevant bugs when you make a change like this? I'm closing this as WONTFIX now.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.