public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/50935] All slim LTO tests FAIL on 32-bit Solaris
Date: Mon, 21 Nov 2011 17:07:00 -0000	[thread overview]
Message-ID: <bug-50935-4-hF7ILdURZ8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50935-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50935

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-11-21 16:50:54 UTC ---
I forgot: while one could use ACX_LARGEFILE everywhere in GCC (and I
tried that using --disable-largefile when configuring gcc works with a
default-configured gld), I'd rather not cripple all of gcc for the
benefit of the lto-plugin.

Using the macro in lto-plugin alone doesn't work either: the plugin is
linked with libiberty, and gld SEGVs all over the place if libiberty
isn't built with largefile support.  Since libiberty is also linked into
all the compiler executables, we're effectively back to using
ACX_LARGEFILE/--disable-largefile everywhere.

    Rainer


  parent reply	other threads:[~2011-11-21 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 15:54 [Bug lto/50935] New: " ro at gcc dot gnu.org
2011-11-01  9:27 ` [Bug lto/50935] " rguenth at gcc dot gnu.org
2011-11-02  9:18 ` ro at CeBiTec dot Uni-Bielefeld.DE
2011-11-21 17:05 ` ro at gcc dot gnu.org
2011-11-21 17:07 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-11-21 17:54 ` bonzini at gnu dot org
2011-11-21 18:05 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-03-22  9:15 ` rguenth at gcc dot gnu.org
2012-07-02 13:07 ` rguenth 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-50935-4-hF7ILdURZ8@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: link
Be 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).