public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/47225] [4.6 regression]: cross-compile fails while configuring libgcc with "xgcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found" Date: Wed, 02 Feb 2011 04:53:00 -0000 [thread overview] Message-ID: <bug-47225-4-NfEt4QWmRn@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47225-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47225 --- Comment #17 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2011-02-02 04:53:05 UTC --- It appears to me that one possible solution is to add the -shared flag to liblto_plugin_la_LDFLAGS. This will cause libtool to fail the link if it can't create a dynamic library, so you'd know the ltoplugin is not supported on that platform. Of course, ideally we'd report it earlier, but I don't quite see how to accomplish that. Testing whether shared libraries remained enabled in lto-plugin/configure is another viable option, but even that feels too late, and it wouldn't catch all cases: libtoolo might configure itself to build shared libraries, and decide that it can't do that for the specific case of lto-plugin (say, on a platform that doesn't support shared libs with undefined symbols, given that we don't pass -no-undefined, or for other reasons, such as non-dynamic dependency libs on platforms that can't have non-PIC in shared libs) Will the former do? Any other thoughts or wishes?
next prev parent reply other threads:[~2011-02-02 4:53 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-08 17:59 [Bug lto/47225] New: [4.6.0 " John.Tytgat at aaug dot net 2011-01-08 18:06 ` Jan Hubicka 2011-01-08 18:07 ` [Bug lto/47225] " hubicka at ucw dot cz 2011-01-08 18:54 ` John.Tytgat at aaug dot net 2011-01-08 18:58 ` Jan Hubicka 2011-01-08 18:58 ` hubicka at ucw dot cz 2011-01-08 19:16 ` Jan Hubicka 2011-01-08 19:16 ` hubicka at ucw dot cz 2011-01-08 19:45 ` hubicka at gcc dot gnu.org 2011-01-08 20:04 ` John.Tytgat at aaug dot net 2011-01-09 14:47 ` hubicka at gcc dot gnu.org 2011-01-09 17:25 ` hubicka at gcc dot gnu.org 2011-01-10 11:51 ` fxcoudert at gcc dot gnu.org 2011-01-10 12:12 ` Jan Hubicka 2011-01-10 12:42 ` hubicka at ucw dot cz 2011-01-11 13:05 ` [Bug lto/47225] [4.6 " rguenth at gcc dot gnu.org 2011-01-11 13:06 ` rguenth at gcc dot gnu.org 2011-01-11 13:35 ` hubicka at gcc dot gnu.org 2011-01-23 1:02 ` hubicka at gcc dot gnu.org 2011-01-24 22:53 ` burnus at gcc dot gnu.org 2011-02-01 21:34 ` aoliva at gcc dot gnu.org 2011-02-02 4:53 ` aoliva at gcc dot gnu.org [this message] 2011-02-02 7:32 ` aoliva at gcc dot gnu.org 2011-02-03 17:12 ` jakub at gcc dot gnu.org 2011-02-06 15:54 ` ktietz at gcc dot gnu.org 2011-02-06 16:58 ` tschwinge at gcc dot gnu.org 2011-02-07 9:04 ` ktietz at gcc dot gnu.org 2011-02-07 9:49 ` tschwinge at gcc dot gnu.org 2011-02-07 10:10 ` bonzini at gnu dot org 2011-02-07 18:55 ` iains at gcc dot gnu.org 2011-02-07 19:42 ` ktietz at gcc dot gnu.org 2011-02-07 20:35 ` ktietz at gcc dot gnu.org 2011-02-07 20:53 ` iains at gcc dot gnu.org 2011-02-07 20:55 ` ktietz at gcc dot gnu.org 2011-02-07 21:05 ` iains at gcc dot gnu.org 2011-02-07 21:32 ` iains at gcc dot gnu.org 2011-02-07 23:14 ` tschwinge at gcc dot gnu.org 2011-02-08 0:15 ` iains at gcc dot gnu.org 2011-02-08 8:56 ` bonzini at gnu dot org 2011-02-08 10:01 ` iains at gcc dot gnu.org 2011-02-08 10:04 ` bonzini at gnu dot org 2011-02-08 10:18 ` iains at gcc dot gnu.org 2011-02-10 12:09 ` jakub at gcc dot gnu.org 2011-02-10 12:15 ` iains at gcc dot gnu.org 2011-02-11 15:33 ` aoliva at gcc dot gnu.org 2011-02-12 12:06 ` aoliva at gcc dot gnu.org 2011-02-12 12:14 ` aoliva at gcc dot gnu.org 2011-02-28 19:26 ` ktietz at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-47225-4-NfEt4QWmRn@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).