Summary: | sys-devel/autoconf-2.13 installs wrongly with et_EE locale | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Priit Laes (IRC: plaes) <plaes> |
Component: | [OLD] Unspecified | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | mozilla |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Priit Laes (IRC: plaes)
2011-01-18 10:12:30 UTC
what version of autoconf wrapper do you have installed? if [ "${WANT_AUTOCONF}" = "2.1" ] && [ "${0##*/}" = "autom4te" ] ; then err "Autoconf 2.13 doesn't contain autom4te.\n" \ " Either unset WANT_AUTOCONF or don't execute anything\n" \ " that would use autom4te." fi This is straight out of the ac-wrapper.sh the syntax in ebuild is correct, your file seems to be corrupt, please re-emerge autoconf-wrapper and try again. If it fails feel free to reopen with autoconf-wrapper version included in your report. I have following autoconf-* packages installed (and reinstalled), but issue still remains: sys-devel/autoconf-2.13 sys-devel/autoconf-2.68 sys-devel/autoconf-wrapper-10-r1 OK, I figured out that this issue is et_EE locale specific: [snip] plaes@sol ~ $ qlist autoconf-2.13 /usr/bin/autoscan--program-suffix-2.13 /usr/bin/ifnames--program-suffix-2.13 /usr/bin/autoreconf--program-suffix-2.13 /usr/bin/autoheader--program-suffix-2.13 /usr/bin/autoconf--program-suffix-2.13 /usr/bin/autoupdate--program-suffix-2.13 /usr/share/doc/autoconf-2.13/ChangeLog.bz2 /usr/share/doc/autoconf-2.13/ChangeLog.0.bz2 /usr/share/doc/autoconf-2.13/NEWS.bz2 /usr/share/doc/autoconf-2.13/ChangeLog.1.bz2 /usr/share/doc/autoconf-2.13/AUTHORS.bz2 /usr/share/doc/autoconf-2.13/README.bz2 /usr/share/doc/autoconf-2.13/TODO.bz2 /usr/share/info/autoconf-2.13.info.bz2 /--dat/usr/share/autoconf/acspecific.m4 /--dat/usr/share/autoconf/acprograms /--dat/usr/share/autoconf/acconfig.h /--dat/usr/share/autoconf/autoheader.m4f /--dat/usr/share/autoconf/acmakevars /--dat/usr/share/autoconf/acoldnames.m4 /--dat/usr/share/autoconf/autoconf.m4f /--dat/usr/share/autoconf/acheaders /--dat/usr/share/autoconf/autoheader.m4 /--dat/usr/share/autoconf/acidentifiers /--dat/usr/share/autoconf/acfunctions /--dat/usr/share/autoconf/autoconf.m4 /--dat/usr/share/autoconf/acgeneral.m4 [/snip] (In reply to comment #4) > OK, I figured out that this issue is et_EE locale specific: > [snip] > plaes@sol ~ $ qlist autoconf-2.13 > /usr/bin/autoscan--program-suffix-2.13 > /usr/bin/ifnames--program-suffix-2.13 > /usr/bin/autoreconf--program-suffix-2.13 > /usr/bin/autoheader--program-suffix-2.13 > /usr/bin/autoconf--program-suffix-2.13 > /usr/bin/autoupdate--program-suffix-2.13 > /usr/share/doc/autoconf-2.13/ChangeLog.bz2 > /usr/share/doc/autoconf-2.13/ChangeLog.0.bz2 > /usr/share/doc/autoconf-2.13/NEWS.bz2 > /usr/share/doc/autoconf-2.13/ChangeLog.1.bz2 > /usr/share/doc/autoconf-2.13/AUTHORS.bz2 > /usr/share/doc/autoconf-2.13/README.bz2 > /usr/share/doc/autoconf-2.13/TODO.bz2 > /usr/share/info/autoconf-2.13.info.bz2 > /--dat/usr/share/autoconf/acspecific.m4 > /--dat/usr/share/autoconf/acprograms > /--dat/usr/share/autoconf/acconfig.h > /--dat/usr/share/autoconf/autoheader.m4f > /--dat/usr/share/autoconf/acmakevars > /--dat/usr/share/autoconf/acoldnames.m4 > /--dat/usr/share/autoconf/autoconf.m4f > /--dat/usr/share/autoconf/acheaders > /--dat/usr/share/autoconf/autoheader.m4 > /--dat/usr/share/autoconf/acidentifiers > /--dat/usr/share/autoconf/acfunctions > /--dat/usr/share/autoconf/autoconf.m4 > /--dat/usr/share/autoconf/acgeneral.m4 > [/snip] > That does not make any sense as we force C for everyone when compiling. This is then for the old autoconf versions slot... autoconf-2.13 has many many locale problems. there is absolutely no value in attempting to fix them. if a package is still using it, it is broken and needs to update to autoconf-2.6x+. bouncing back to mozilla on the assumption that its code is still based on autoconf-2.13. vapier we all know mozilla is not moving forward with autoconf-2.6, the only plausible solution is to force C in autoconf-2.13 and be done with it. If you wish to see mozilla move to autoconf-2.6 please feel free to provide the patch and I will ensure it gets into the right hands to have it land upstream. how you choose to hack up the mozilla ebuild is up to you. autoconf-2.13 isnt going to be patched in any way. As this is no a mozilla problem but an autoconf-2.13 issue. There is nothing the mozilla team can or will be able to do to address the problem. that's crap. the bugs in autoconf-2.13 have long been fixed with quite a number of overhauls in newer autoconf. by insisting on still using autoconf-2.13, you insist on keeping those bugs. which means you can figure out how to workaround them locally. (In reply to comment #11) > that's crap. the bugs in autoconf-2.13 have long been fixed with quite a > number of overhauls in newer autoconf. by insisting on still using > autoconf-2.13, you insist on keeping those bugs. which means you can figure > out how to workaround them locally. Is not my job to work around broken autoconf, if you want to see autoconf-2.13 dep updated on mozilla products write the patch and send it upstream. it is your job to make sure the ebuilds you're maintaining arent full of bugs that affect users. how you decide to accomplish that job is your prerogative. (In reply to comment #13) > it is your job to make sure the ebuilds you're maintaining arent full of bugs > that affect users. how you decide to accomplish that job is your prerogative. Hog wash, the simple solution is to force LC_ALL=C when emerging autoconf-2.13 the bug has nothing do with mozilla itself but with autoconf-2.13 the problem is that firefox is using long dead versions of tools. by willfully making that decision, they get to pick up the pieces when things break because they're using tools that are known to be broken. their issues have long been fixed in newer versions. expecting people to back port random (and huge) chunks of codes to old, dead, and unsupported programs is beyond unreasonable. i never said that hacking around the issue in the firefox ebuild is unacceptable. you're the ebuild maintainer, so that's your call. emerging xulrunner works just fine for me with LANG=et_EE.UTF8. the original reporter should see if this is still an issue for them, and if so, post the output of `qlist -Iv auto{conf,make}` also, in looking at the xulrunner ebuild, some notes: - exporting LANG, LC_ALL, LC_MESSAGES, and LC_CTYPE makes no sense. simply export LC_ALL=C and that overrides all other locale env vars. - this should not be done in pkg_setup as this is a src-only issue. i'd move the settings to the top of src_prepare(). Uhoh... SpanKY, the real issue is that autoconf-2.13 is installed to a wrong location when LC_ALL=et_EE and it's "binary" ends up at "/usr/bin/autoconf--program-suffix-2.13". So basically *every* other program depending on it would fail regardless of locale settings afterwards... thanks for re-iterating that. i thought the install issue was with xulrunner itself, not autoconf. http://sources.gentoo.org/sys-devel/autoconf/autoconf-2.13.ebuild?r1=1.18&r2=1.19 |