public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80196] fenv_t not declared
Date: Fri, 06 May 2022 20:44:58 +0000	[thread overview]
Message-ID: <bug-80196-4-gASxX2nFkS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-80196-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Eddy L O Jansson from comment #15)
> For reasons that I'll skip, between the successful build of 12.0.1 and now I
> had added:
> 
> export
> CPLUS_INCLUDE_PATH=/opt/local/include/c++/12.0.1:/opt/local/include/c++/12.0.
> 1/x86_64-linux-gnu/
> 
> to my .bashrc

Don't do that. This causes GCC 12.1 to find the headers for GCC 12.0.1 instead
of the libc headers. That breaks the build, but is user error.

  parent reply	other threads:[~2022-05-06 20:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-80196-4@http.gcc.gnu.org/bugzilla/>
2021-06-18 19:44 ` gr.audio at gmail dot com
2021-06-28 19:55 ` dilfridge at gentoo dot org
2021-06-28 19:56 ` dilfridge at gentoo dot org
2021-07-24 13:35 ` isuruf at gmail dot com
2021-07-24 19:31 ` gr.audio at gmail dot com
2021-07-24 23:29 ` isuruf at gmail dot com
2021-08-20 22:00 ` bneumeier at gmail dot com
2021-08-20 23:29 ` gr.audio at gmail dot com
2022-05-06 18:56 ` eddy at klopper dot net
2022-05-06 20:44 ` redi at gcc dot gnu.org [this message]
2022-05-06 20:47 ` redi 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-80196-4-gASxX2nFkS@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).