This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
Re: testresults, linuxppc-2000, powerpc-unknown-linux-gnu
- To: Phil Edwards <pedwards at disaster dot jaj dot com>
- Subject: Re: testresults, linuxppc-2000, powerpc-unknown-linux-gnu
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: Mon, 27 Nov 2000 17:33:47 -0800 (PST)
- cc: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>, libstdc++ at sources dot redhat dot com
> For non-native-tools building, I use a unified GCC+binutils source tree,
> and just use --with-gnu-ld (with no =pathname argument). The configure
> and build pick up on the presence of GNU ld sources living *right there*
> and behave correctly, but if the sources aren't *right there* then weirdness
> and pain happens later. As long as it's unified, it's okay.
hmm. for native sun builds, i did used the unified gcc+src directory,
much as Phil described. It works pretty well.
BTW, if other people have results on BSD and Solaris (with
--enable-debug) please post them.
-benjamin