building LTO plugin fails for x86_64-unknown -linux-gnu
Richard Guenther
richard.guenther@gmail.com
Sun Oct 11 17:36:00 GMT 2009
On Sun, Oct 11, 2009 at 6:21 PM, Richard Guenther
<richard.guenther@gmail.com> wrote:
> On Sun, Oct 11, 2009 at 6:04 PM, Rainer Emrich
> <rainer@emrich-ebersheim.de> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> libtool: link: gcc -shared .libs/lto-plugin.o
>> -
>> -L/SCRATCH/tmp.dYgZv17836/Linux/x86_64-unknown-linux-gnu/openSUSE_10.3/install/lib64
>
> is there a libiberty in that path?
>
>> - -lelf
>> -
>> -L/SCRATCH/tmp.dYgZv17836/Linux/x86_64-unknown-linux-gnu/openSUSE_10.3/gcc-4.5.0/gcc-4.5.0/libiberty/pic
>
> it's supposed to be picked up from here instead.
Thus, I guess
Index: lto-plugin/Makefile.am
===================================================================
--- lto-plugin/Makefile.am (revision 152638)
+++ lto-plugin/Makefile.am (working copy)
@@ -16,4 +16,4 @@ AM_CFLAGS = -Wall -Werror
libexecsub_LTLIBRARIES = liblto_plugin.la
liblto_plugin_la_SOURCES = lto-plugin.c
-liblto_plugin_la_LIBADD = $(LIBELFLIBS) -L../libiberty/pic -liberty
+liblto_plugin_la_LIBADD = $(LIBELFLIBS) ../libiberty/pic/libiberty.a
would fix it.
Richard.
More information about the Gcc
mailing list