On Sat, Apr 7, 2012 at 4:38 PM, Lev Serebryakov <l...@serebryakov.spb.ru> wrote: > Hello, MSPGCC. > > Maybe, it is not proper list to ask. But gcc-specific lists are very > noisy and I'm not subscribed to any of them. > > I'm trying to update FreeBSD ports to latest LTS reelease, announced > yesterday. > Previous (gxx 4.5.x) release builds without any problems. I've > changed version numbers, and leave all commands the same. Result is > error: > > gmake[2]: Entering directory > `/usr/home/lev/FreeBSD-commiter/ports/devel/msp430-gcc/work/build/lto-plugin' > gmake all-am > gmake[3]: Entering directory > `/usr/home/lev/FreeBSD-commiter/ports/devel/msp430-gcc/work/build/lto-plugin' > /bin/sh ./libtool --tag=CC --tag=disable-static --mode=compile cc > -DHAVE_CONFIG_H -I. -I.././../gcc-4.6.3/lto-plugin > -I.././../gcc-4.6.3/lto-plugin/../include -DHAVE_CONFIG_H -Wall -O2 -pipe > -fno-strict-aliasing -c -o lto-plugin.lo > .././../gcc-4.6.3/lto-plugin/lto-plugin.c > libtool: compile: cc -DHAVE_CONFIG_H -I. -I.././../gcc-4.6.3/lto-plugin > -I.././../gcc-4.6.3/lto-plugin/../include -DHAVE_CONFIG_H -Wall -O2 -pipe > -fno-strict-aliasing -c .././../gcc-4.6.3/lto-plugin/lto-plugin.c -fPIC > -DPIC -o .libs/lto-plugin.o > /bin/sh ./libtool --tag=CC --tag=disable-static --mode=link cc -Wall -O2 > -pipe -fno-strict-aliasing -module -bindir > /usr/local/libexec/gcc/msp430/4.6.3 -Wc,../libiberty/libiberty.a -o > liblto_plugin.la -rpath /usr/local/libexec/gcc/msp430/4.6.3 lto-plugin.lo > libtool: link: cc -shared .libs/lto-plugin.o ../libiberty/libiberty.a > -Wl,-soname -Wl,liblto_plugin.so.0 -o .libs/liblto_plugin.so.0 > /usr/bin/ld: ../libiberty/libiberty.a(argv.o): relocation R_X86_64_32S can > not be used when making a shared object; recompile with -fPIC > ../libiberty/libiberty.a: could not read symbols: Bad value > gmake[3]: *** [liblto_plugin.la] Error 1 > > So, libibery.a was build as non-PIC library and LTO plugin could > not be linked with it. > > Is here any solution other than disabling LTO plugin?
Dunno; I've never explicitly enabled or disabled LTO or any plugins. The only configuration I test is the one documented in the build instructions. Peter > > -- > // Black Lion AKA Lev Serebryakov <l...@serebryakov.spb.ru> > > > ------------------------------------------------------------------------------ > For Developers, A Lot Can Happen In A Second. > Boundary is the first to Know...and Tell You. > Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > http://p.sf.net/sfu/Boundary-d2dvs2 > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
