public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails
Date: Wed, 20 Oct 2021 03:20:06 +0000	[thread overview]
Message-ID: <bug-100017-4-WPqnUbhrRV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100017-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #28 from cqwrteur <unlvsur at live dot com> ---
(In reply to Ofer Shinaar from comment #27)
> (In reply to cqwrteur from comment #23)
> > (In reply to Jonathan Wakely from comment #22)
> > > *** Bug 101060 has been marked as a duplicate of this bug. ***
> > 
> > I can confirm Yujie Yang's patch works. Just add -nostdinc++ to configure
> > and configure.ac in gcc root repository (not in gcc subdirectory nor
> > libstdc++-v3 subdirectory)
> > 
> > Yes. So it is very easy to fix.
> 
> and what if I do want to use libstdc++ ? the first soultion allows me that

no. it does not affect how libstdc++ builds. It is a bug in the build process
that the GCC will prefer finding headers in the C++ cross compiler. It should
not use C++ standard library headers in your cross compiler.

Add -nostdinc++ is adding a toggle at the build process that fixes all sorts of
issues that relate to the build of libstdc++.

It won't affect you for using it after the build.

There are some other problems of Canadian compilation here, like copying wrong
DLLs when you build with multilibs. Those are separate issues.

  parent reply	other threads:[~2021-10-20  3:20 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 11:45 [Bug libstdc++/100017] New: error: 'fenv_t' has not been declared in '::' x86_64-w64-mingw32 host cross toolchain fails to build unlvsur at live dot com
2021-04-10 11:47 ` [Bug libstdc++/100017] " unlvsur at live dot com
2021-04-10 11:54 ` unlvsur at live dot com
2021-04-10 12:00 ` unlvsur at live dot com
2021-04-10 12:03 ` unlvsur at live dot com
2021-04-10 13:42 ` unlvsur at live dot com
2021-04-21 15:40 ` redi at gcc dot gnu.org
2021-04-21 16:29 ` redi at gcc dot gnu.org
2021-04-21 17:50 ` redi at gcc dot gnu.org
2021-04-23 21:06 ` unlvsur at live dot com
2021-04-23 21:24 ` unlvsur at live dot com
2021-04-23 21:31 ` unlvsur at live dot com
2021-04-25 23:21 ` davem at devkitpro dot org
2021-06-13 15:26 ` [Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- " belyshev at depni dot sinp.msu.ru
2021-06-28 19:52 ` dilfridge at gentoo dot org
2021-06-28 20:00 ` iains at gcc dot gnu.org
2021-06-29  8:24 ` redi at gcc dot gnu.org
2021-06-29  9:09 ` davem at devkitpro dot org
2021-07-06  6:44 ` rguenth at gcc dot gnu.org
2021-07-12 13:43 ` ofer.shinaar at wdc dot com
2021-07-28  7:06 ` rguenth at gcc dot gnu.org
2021-08-04  7:45 ` yangyujie at alumni dot sjtu.edu.cn
2021-08-04 16:30 ` unlvsur at live dot com
2021-08-24 11:09 ` redi at gcc dot gnu.org
2021-08-24 11:11 ` unlvsur at live dot com
2021-08-24 12:28 ` unlvsur at live dot com
2021-09-07 12:06 ` abrodkin at synopsys dot com
2021-09-07 18:16 ` [Bug libstdc++/100017] [11/12 regression] error: 'fenv_t' has not been declared in '::' -- canadian compilation fails unlvsur at live dot com
2021-10-19 16:05 ` ofer.shinaar at wdc dot com
2021-10-20  3:20 ` unlvsur at live dot com [this message]
2021-11-01 18:12 ` vvinayag at arm dot com
2021-11-07 18:55 ` aladjev.andrew at gmail dot com
2021-11-07 18:59 ` unlvsur at live dot com
2021-11-07 19:08 ` aladjev.andrew at gmail dot com
2021-11-07 19:14 ` unlvsur at live dot com
2021-11-07 19:15 ` unlvsur at live dot com
2021-11-07 19:24 ` aladjev.andrew at gmail dot com
2021-11-07 19:29 ` unlvsur at live dot com
2021-11-07 19:31 ` unlvsur at live dot com
2021-11-07 19:36 ` aladjev.andrew at gmail dot com
2021-11-07 19:38 ` unlvsur at live dot com
2021-11-07 19:40 ` unlvsur at live dot com
2021-11-07 19:41 ` unlvsur at live dot com
2021-11-16 21:10 ` unlvsur at live dot com
2021-11-16 21:23 ` redi at gcc dot gnu.org
2021-11-30 23:17 ` unlvsur at live dot com
2021-12-06 11:38 ` redi at gcc dot gnu.org
2021-12-10 11:54 ` vvinayag at arm dot com
2021-12-10 12:12 ` redi at gcc dot gnu.org
2021-12-21  1:06 ` unlvsur at live dot com
2021-12-21  1:07 ` unlvsur at live dot com
2021-12-21  9:34 ` unlvsur at live dot com
2021-12-21  9:44 ` unlvsur at live dot com
2021-12-28 20:09 ` kallisti5 at unixzen dot com
2022-01-06 15:52 ` redi at gcc dot gnu.org
2022-01-06 15:53 ` unlvsur at live dot com
2022-01-06 15:55 ` redi at gcc dot gnu.org
2022-01-06 15:57 ` unlvsur at live dot com
2022-01-06 16:38 ` kallisti5 at unixzen dot com
2022-01-06 16:55 ` jakub at gcc dot gnu.org
2022-01-06 17:22 ` unlvsur at live dot com
2022-01-06 17:24 ` unlvsur at live dot com
2022-01-06 17:27 ` unlvsur at live dot com
2022-01-06 17:41 ` unlvsur at live dot com
2022-01-06 17:59 ` redi at gcc dot gnu.org
2022-01-06 18:00 ` unlvsur at live dot com
2022-01-06 18:03 ` kallisti5 at unixzen dot com
2022-01-06 18:08 ` unlvsur at live dot com
2022-01-06 18:21 ` redi at gcc dot gnu.org
2022-01-06 19:34 ` kallisti5 at unixzen dot com
2022-01-06 20:33 ` redi at gcc dot gnu.org
2022-01-06 20:42 ` jakub at gcc dot gnu.org
2022-01-06 20:51 ` redi at gcc dot gnu.org
2022-01-06 20:54 ` redi at gcc dot gnu.org
2022-01-06 21:00 ` jakub at gcc dot gnu.org
2022-01-06 22:41 ` unlvsur at live dot com
2022-01-06 22:42 ` unlvsur at live dot com
2022-01-06 23:33 ` unlvsur at live dot com
2022-01-07  0:10 ` redi at gcc dot gnu.org
2022-01-10 12:18 ` cvs-commit at gcc dot gnu.org
2022-01-10 14:10 ` [Bug libstdc++/100017] [11 " stammark at gcc dot gnu.org
2022-01-10 15:49 ` redi at gcc dot gnu.org
2022-01-10 18:57 ` cvs-commit at gcc dot gnu.org
2022-01-10 18:58 ` 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-100017-4-WPqnUbhrRV@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).