public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bootmgr at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/101655] canadian compile of libgcc uses native cc as the compiler instead of the target cross compiler
Date: Fri, 30 Jul 2021 04:30:26 +0000 [thread overview]
Message-ID: <bug-101655-4-zhI9dj2gsg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101655-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101655
--- Comment #11 from bootmgr at 163 dot com <bootmgr at 163 dot com> ---
(In reply to Andreas Schwab from comment #10)
> In a canadian cross, you don't compile the target libraries. They are
> already built while building the cross compiler.
Isn't this a bug?
I manually reconfigured libgcc, and it can detect x86_46-w64-mingw32-{gcc,g++}.
But I did not continue to build it.
Why can't the target library be used for Canadian cross?
I have another question. Why can't libgcc,libquadmath,libvtv and libstdc++
detect the CFLAGS,CXXFLAGS or CPPFALGS environment variable when I build cross
compiler?
next prev parent reply other threads:[~2021-07-30 4:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 2:56 [Bug libgcc/101655] New: " unlvsur at live dot com
2021-07-28 3:00 ` [Bug libgcc/101655] " unlvsur at live dot com
2021-07-28 3:06 ` unlvsur at live dot com
2021-07-28 3:11 ` unlvsur at live dot com
2021-07-28 3:16 ` unlvsur at live dot com
2021-07-28 3:22 ` pinskia at gcc dot gnu.org
2021-07-28 3:29 ` unlvsur at live dot com
2021-07-28 3:31 ` unlvsur at live dot com
2021-07-28 3:37 ` unlvsur at live dot com
2021-07-28 3:46 ` unlvsur at live dot com
2021-07-28 7:35 ` schwab@linux-m68k.org
2021-07-30 4:30 ` bootmgr at 163 dot com [this message]
2021-08-16 7:35 ` schwab@linux-m68k.org
2021-09-10 10:31 ` unlvsur at live dot com
2021-09-10 10:31 ` unlvsur at live dot com
2021-09-10 10:33 ` unlvsur at live dot com
2022-03-10 18:31 ` 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-101655-4-zhI9dj2gsg@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).