public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/60160] Building with -flto in CFLAGS_FOR_TARGET / CXXFLAGS_FOR_TARGET
Date: Sat, 23 Aug 2014 13:43:00 -0000	[thread overview]
Message-ID: <bug-60160-4-bu5VsNnvnk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60160-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60160

--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
ISTR that building with CFLAGS_FOR_TARGET="-g -O2 -flto -ffat-lto-objects",
same for CXXFLAGS_FOR_TARGET, and --disable-bootstrap used to complete, but now
it fails during the link of .libs/libstdc++.so.6.0.21:

lto1: fatal error: /tmp/ccRgW0QI.ltrans5.o: section
_ZTVSd.localalias.316.lto_priv.752 is missing
compilation terminated.
lto-wrapper: fatal error: /tmp/gcc-lto/build/./gcc/xgcc returned 1 exit status
compilation terminated.
/usr/bin/ld: lto-wrapper failed
collect2: error: ld returned 1 exit status

I don't remember ever seeing that "section ... is missing" error before.


Exact line I used:
/data/repos/gcc/trunk/configure --prefix=/tmp/gcc-lto/inst
--enable-languages=c,c++ --with-system-zlib --disable-nls
--enable-libstdcxx-time=yes --disable-bootstrap --disable-libgomp
--disable-libitm --disable-libquadmath --disable-libatomic --disable-libssp
--disable-multilib --disable-libsanitizer --disable-libvtv --disable-libcilkrts


  parent reply	other threads:[~2014-08-23 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 15:19 [Bug bootstrap/60160] New: " d.g.gorbachev at gmail dot com
2014-02-12 15:38 ` [Bug bootstrap/60160] " glisse at gcc dot gnu.org
2014-02-12 15:44 ` trippels at gcc dot gnu.org
2014-08-23 13:43 ` glisse at gcc dot gnu.org [this message]
2014-08-23 14:39 ` d.g.gorbachev at gmail dot com
2022-04-08 12:34 ` rdiezmail-gcc at yahoo dot de
2022-04-08 12:49 ` rguenth at gcc dot gnu.org
2023-02-02  8:39 ` a.heider at gmail dot com
2023-02-02 12:56 ` a.heider at gmail dot com

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-60160-4-bu5VsNnvnk@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).