This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/44959] [4.6 Regression] bootstrap failed at Comparing stages 2 and 3


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44959

--- Comment #44 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #43 from Hin-Tak Leung <htl10 at users dot sourceforge.net> ---
> (In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #40)
>> Please try this on your system and tell us how you end up with
>> bootstrap-debug instead of none.
>
> Hmm, sorry, redherring. I think I found the difference - it depends on which
> strip I am using - the one in /usr/local/bin/ gives bootstrap-debug, while the
> one in /sbin/ gives none. (problem of having some GNU variety of utilities in
> /usr/local/bin, and whethe that's in front of $PATH).

Makes sense: binutils support for Tru64 UNIX is known to be harmful (as
you just discovered) or broken (gas cannot even assemble hello world
compiler output), so nobody else every even tried binutils or parts
thereof.

Given that GCC 4.7 is the last release to support Tru64 UNIX, the
release branch will soon be closed with the advent of GCC 4.9, and
you're the only one ever to report this issue, I'll leave the bug as
WONTFIX.

Thanks for your detective work.

    Rainer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]