public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rwild at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/40974] cannot build gcc-4.4.1: fenv_t has not been declared Date: Tue, 22 Dec 2009 21:04:00 -0000 [thread overview] Message-ID: <20091222210427.4176.qmail@sourceware.org> (raw) In-Reply-To: <bug-40974-17891@http.gcc.gnu.org/bugzilla/> ------- Comment #20 from rwild at gcc dot gnu dot org 2009-12-22 21:04 ------- Created an attachment (id=19374) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19374&action=view) patch to turn off multiple inclusion guard for fenv.h C++ wrapper Comment #18 confirms #13. It is probably sufficient to turn off the inclusion guard for the include_next. However, it is also a slightly risky thing to do; and I'm not quite sure whether it is conceptually the right thing to do. (FWIW, gnulib uses split inclusion guards for include_next in a number of places.) (One risk is backward compatibility requirements stemming from including the header from the installed, possibly older, compiler.) Another strategy that comes to mind is to use -nostdinc++ and then add the other include headers manually, but that is likely even more risky. I'd be interested to see how the clfs build fares with this patch. If it succeeds, bonus points for also installing the just-built compiler and then trying to do another cross build using the just-installed compiler. Building and testing of a native compiler succeeded on x86_64-unknown-linux-gnu. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40974
next prev parent reply other threads:[~2009-12-22 21:04 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-08-05 16:44 [Bug libstdc++/40974] New: " booleandomain at gmail dot com 2009-08-05 22:26 ` [Bug libstdc++/40974] " paolo dot carlini at oracle dot com 2009-08-06 19:22 ` booleandomain at gmail dot com 2009-08-06 20:21 ` booleandomain at gmail dot com 2009-08-07 8:22 ` paolo dot carlini at oracle dot com 2009-08-07 9:46 ` bonzini at gnu dot org 2009-08-07 10:12 ` paolo dot carlini at oracle dot com 2009-08-07 10:45 ` bonzini at gnu dot org 2009-08-07 11:58 ` booleandomain at gmail dot com 2009-08-07 12:01 ` booleandomain at gmail dot com 2009-08-07 12:03 ` booleandomain at gmail dot com 2009-08-07 12:10 ` booleandomain at gmail dot com 2009-09-26 19:44 ` pinskia at gcc dot gnu dot org 2009-12-15 20:48 ` armand dot potter at free dot fr 2009-12-16 16:18 ` paolo dot carlini at oracle dot com 2009-12-16 17:30 ` bonzini at gnu dot org 2009-12-16 19:15 ` paolo dot carlini at oracle dot com 2009-12-16 21:52 ` rwild at gcc dot gnu dot org 2009-12-19 15:44 ` armand dot potter at free dot fr 2009-12-22 9:58 ` paolo dot carlini at oracle dot com 2009-12-22 21:04 ` rwild at gcc dot gnu dot org [this message] 2010-01-10 11:28 ` armand dot potter at free dot fr 2010-01-10 12:16 ` paolo dot carlini at oracle dot com 2010-01-10 12:18 ` paolo dot carlini at oracle dot com 2010-01-10 16:52 ` hjl dot tools at gmail dot com 2010-01-10 17:16 ` hjl dot tools at gmail dot com 2010-05-14 15:07 ` armin76 at gentoo dot org 2010-05-14 15:11 ` paolo dot carlini at oracle dot com 2010-05-14 15:50 ` dougsemler at gmail dot com 2010-05-16 17:32 ` rwild at gcc dot gnu dot org 2010-06-19 11:31 ` armin76 at gentoo dot org 2010-07-21 21:35 ` armand dot potter at free dot fr 2010-07-21 22:03 ` paolo dot carlini at oracle dot com 2010-07-25 15:20 ` paolo dot carlini at oracle dot com 2010-08-01 17:21 ` armand dot potter at free dot fr 2010-08-02 6:53 ` paolo dot carlini at oracle dot com 2010-08-10 21:51 ` pinskia at gcc dot gnu dot org 2010-08-10 21:53 ` [Bug libstdc++/40974] [4.3/4.4/4.5/4.6 Regression] " pinskia at gcc dot gnu dot org 2010-08-10 22:00 ` pinskia at gcc dot gnu dot org 2010-08-10 22:18 ` paolo dot carlini at oracle dot com 2010-08-10 22:19 ` pinskia at gcc dot gnu dot org 2010-08-11 1:12 ` pinskia at gcc dot gnu dot org 2010-08-11 1:20 ` pinskia at gcc dot gnu dot org 2010-08-11 1:24 ` paolo dot carlini at oracle dot com 2010-08-11 1:28 ` pinskia at gcc dot gnu dot org 2010-08-11 7:08 ` paolo dot carlini at oracle dot com 2010-09-02 8:24 ` boris at kolpackov dot net 2010-09-02 9:42 ` paolo dot carlini at oracle dot com 2010-09-02 12:45 ` bonzini at gnu dot org 2010-09-02 14:10 ` paolo dot carlini at oracle dot com 2010-09-02 14:13 ` paolo at gcc dot gnu dot org 2010-09-02 16:07 ` paolo dot carlini at oracle 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=20091222210427.4176.qmail@sourceware.org \ --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).