Bug 416813 – sys-devel/gcc-4.4.7: non POSIX test construction in a configure script

• Status: RESOLVED WONTFIX
• Product: Gentoo/Alt

[Description Richard Yao (RETIRED) 2012-05-20 22:50:33 UTC]

I built sys-devel/gcc-4.4.7 so that I could revisit the solution to bug #362449 when I encountered the following messages in the emerge output:

 * Found a non POSIX test construction in a configure script
 * The configure checks of this package may not function properly
 * Please report this on Gentoo Bugzilla in Gentoo/Alt product for component FreeBSD.
 * http://bugs.gentoo.org/enter_bug.cgi?product=Gentoo%2FAlt&component=FreeBSD&op_sys=FreeBSD

[Comment 1 Alexis Ballier 2012-05-22 13:29:21 UTC]

well, as a gentoo developer you are expected to provide a bit more of information :)

as a gentoo/bsd developer, you are expected to provide a patch and assign the bug to the maintainer, as the vast majority of devs will have no clue about this and do not use fbsd :)

[Comment 2 Richard Yao (RETIRED) 2012-05-22 17:55:34 UTC]

Does this mean that I can join the Gentoo FreeBSD team? :)

[Comment 3 Alexis Ballier 2012-05-22 18:43:40 UTC]

if you plan to help i dont see any problem with it

[Comment 4 Naohiro Aota 2012-05-23 16:42:23 UTC]

# grep  "\\<test .*==" "${S}" -r --include configure .
./gcc-4.4.7/configure:if test `cat cygwin-cat-check` == a ; then

# grep -r cygwin-cat .
./gcc-4.4.7/config/acx.m4:echo a >cygwin-cat-check
./gcc-4.4.7/config/acx.m4:if test `cat cygwin-cat-check` == a ; then
./gcc-4.4.7/config/acx.m4:  rm cygwin-cat-check
./gcc-4.4.7/config/acx.m4:  rm cygwin-cat-check
./gcc-4.4.7/configure:echo a >cygwin-cat-check
./gcc-4.4.7/configure:if test `cat cygwin-cat-check` == a ; then
./gcc-4.4.7/configure:  rm cygwin-cat-check
./gcc-4.4.7/configure:  rm cygwin-cat-check

and it had been fixed in upstream.

http://gcc.gnu.org/ml/gcc-patches/2009-10/msg01459.html

[Comment 5 Alexis Ballier 2012-05-23 16:52:33 UTC]

closing as fixed then, since newer versions are fine, thanks

[Comment 6 Richard Yao (RETIRED) 2012-05-25 00:14:26 UTC]

(In reply to comment #5)
> closing as fixed then, since newer versions are fine, thanks

That mailing list email was from 2009. GCC 4.4.7 was released this year and we still have this problem. I would not call this fixed, but I am going to change it to won't fix. I have identified enough issues in GCC 4.4.7 that fixing them would take time that would be better spent elsewhere.