More explicit what's wrong with this: FAILED: Bootstrap (build config: lto; languages: all; trunk revision 217898) on x86_64-unknown-linux-gnu
See: https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg02259.html What's not in the log file sent to gcc-results: /usr/bin/ld: /dev/shm/wd4296/ccFei5Gg.ltrans0.ltrans.o: relocation R_X86_64_32S against `prime_tab.lto_priv.2' can not be used when making a shared o bject; recompile with -fPIC /dev/shm/wd4296/ccFei5Gg.ltrans0.ltrans.o: error adding symbols: Bad value collect2: error: ld returned 1 exit status Makefile:409: recipe for target 'libcc1.la' failed make[3]: *** [libcc1.la] Error 1 Kind regards, -- Toon Moene - e-mail: t...@moene.org - phone: +31 346 214290 Saturnushof 14, 3738 XG Maartensdijk, The Netherlands At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/ Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
Re: More explicit what's wrong with this: FAILED: Bootstrap (build config: lto; languages: all; trunk revision 217898) on x86_64-unknown-linux-gnu
On 2014.11.21 at 16:16 +0100, Toon Moene wrote: > See: https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg02259.html > > What's not in the log file sent to gcc-results: See: http://thread.gmane.org/gmane.comp.gcc.patches/327449 -- Markus
Re: More explicit what's wrong with this: FAILED: Bootstrap (build config: lto; languages: all; trunk revision 217898) on x86_64-unknown-linux-gnu
On Fri, Nov 21, 2014 at 7:23 AM, Markus Trippelsdorf wrote: > On 2014.11.21 at 16:16 +0100, Toon Moene wrote: >> See: https://gcc.gnu.org/ml/gcc-testresults/2014-11/msg02259.html >> >> What's not in the log file sent to gcc-results: > > See: http://thread.gmane.org/gmane.comp.gcc.patches/327449 > > -- > Markus Since there is no objection to back port LTO support from libtool upstream, I will check it in shortly. Thanks. -- H.J.
Bernd Schmidt appointed as nvptx port maintainer
I'm pleased to announce that Bernd Schmidt been appointed as maintainer for the nvptx port he recently contributed to GCC. Bernd, please add yourself as the maintainer for that port in the MAINTAINERS file. Thanks for your patience, Jeff