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++/109926] fatal error: fenv.h: No such file or directory for canadian compilation of i586-msdosdjgpp
Date: Mon, 22 May 2023 10:32:39 +0000 [thread overview]
Message-ID: <bug-109926-4-4yRu3Vw8HH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109926-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109926
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Comment on attachment 55135
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55135
config
configure:18893: checking fenv.h usability
configure:18893: i586-msdosdjgpp-c++ -c -g -O2 -std=c++11 -fno-exceptions
conftest.cpp >&5
configure:18893: $? = 0
configure:18893: result: yes
configure:18893: checking fenv.h presence
configure:18893: i586-msdosdjgpp-c++ -E conftest.cpp
configure:18893: $? = 0
configure:18893: result: yes
configure:18893: checking for fenv.h
configure:18893: result: yes
This means configure is finding fenv.h in your sysroot.
next prev parent reply other threads:[~2023-05-22 10:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-21 19:22 [Bug libstdc++/109926] New: " unlvsur at live dot com
2023-05-21 19:22 ` [Bug libstdc++/109926] " unlvsur at live dot com
2023-05-21 19:28 ` pinskia at gcc dot gnu.org
2023-05-21 19:28 ` unlvsur at live dot com
2023-05-21 19:38 ` unlvsur at live dot com
2023-05-22 9:10 ` redi at gcc dot gnu.org
2023-05-22 9:19 ` redi at gcc dot gnu.org
2023-05-22 9:21 ` unlvsur at live dot com
2023-05-22 10:32 ` redi at gcc dot gnu.org [this message]
2024-03-30 13:25 ` unlvsur at live dot com
2024-03-30 13:26 ` unlvsur at live dot com
2024-03-30 13:42 ` unlvsur at live 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-109926-4-4yRu3Vw8HH@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).