public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels 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: Wed, 12 Feb 2014 15:44:00 -0000 [thread overview] Message-ID: <bug-60160-4-tBqhSi9c4F@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60160-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60160 --- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- libstdc++ also causes problems: /var/tmp/gcc_build_dir_/./prev-gcc/xg++ -B/var/tmp/gcc_build_dir_/./prev-gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -nostdinc++ -B/var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/l ibstdc++-v3/src/.libs -B/var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs -I/var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/ x86_64-pc-linux-gnu -I/var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/libstdc++-v3/include -I/var/tmp/gcc/libstdc++-v3/libsupc++ -L/var/tmp/gcc_build_dir_/prev-x86_64-pc-lin ux-gnu/libstdc++-v3/src/.libs -L/var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs -march=native -O3 -pipe -flto=jobserver -frandom-seed=1 -fprof ile-generate -fno-lto -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedan tic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -DGENERATOR_FILE -Wl,-O1,--hash-style=gnu,--as-needed,--gc-sections,--icf=safe,--icf-iterati ons=3 -o build/genconstants \ build/genconstants.o build/read-md.o build/errors.o .././libiberty/libiberty.a /var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so: error: undefined reference to 'std::istream::ignore(long)' /var/tmp/gcc_build_dir_/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs/libstdc++.so: error: undefined reference to 'std::basic_istream<wchar_t, std::char_traits<wchar_t> >:: ignore(long)'
next prev parent reply other threads:[~2014-02-12 15:44 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 [this message] 2014-08-23 13:43 ` glisse at gcc dot gnu.org 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-tBqhSi9c4F@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).