This is the mail archive of the gcc-patches@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]

Re: [patch lto-plugin]: Part 2 for PR lto/47225 - [4.6 regression]: cross-compile fails while configuring libgcc with "xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"


2011/2/7 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>:
> * Ralf Wildenhues wrote on Mon, Feb 07, 2011 at 07:43:37PM CET:
>> * Kai Tietz wrote on Mon, Feb 07, 2011 at 07:32:51PM CET:
>> > 2011/2/7 Andreas Krebbel <krebbel@linux.vnet.ibm.com>:
>
>> > > ?liblto_plugin_la_DEPENDENCIES = $(if $(wildcard \
>> > > - ? ? ? ../libiberty/pic/libiberty.a),../libiberty/pic/libiberty.a,)
>> > > + ? ? ? ../libiberty/pic/libiberty.a),$(Wl)../libiberty/pic/libiberty.a,)
>
>> > > which is used as rule dependency:
>> > >
>> > > liblto_plugin.la: $(liblto_plugin_la_OBJECTS) $(liblto_plugin_la_DEPENDENCIES)
>> > > ? ? ? ?$(liblto_plugin_la_LINK) -rpath $(libexecsubdir) $(liblto_plugin_la_OBJECTS)
>> > > $(liblto_plugin_la_LIBADD) $(LIBS)
>
>> What you can do however is just overwrite the automatically generated
>> dependencies, by adding
>> ? ?liblto_plugin_la_DEPENDENCIES =
>
> Hmm, I guess it'd be even better if we actually listed the dependencies
> here, but without the $(Wc):
>
> ??liblto_plugin_la_DEPENDENCIES = $(if $(wildcard \
> ?? ? ? ../libiberty/pic/libiberty.a),../libiberty/pic/libiberty.a,)
>
> Sorry for the noise.
>

Ok, here is current variant. I just tested it for x86_64-pc-linux-gnu
and it works here.
But for what actual the la_DEPENDENCIES are used here?

Kai

Attachment: l4.txt
Description: Text document


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