public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bib_aab at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/104856] Build gcc with a target not containing '-gnu' gets added to gnat target
Date: Wed, 09 Mar 2022 18:52:17 +0000 [thread overview]
Message-ID: <bug-104856-4-QqrboJ3HFD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104856-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104856
--- Comment #3 from Bib <bib_aab at hotmail dot com> ---
I tried rebuilding with:
../configure --prefix=/opt/gcc11a --enable-languages=c,c++,ada
--enable-offload-targets=nvptx-none, --without-cuda-driver
--enable-checking=release --disable-werror --enable-ssp --disable-libssp
--disable-libvtv --disable-libcc1 --disable-plugin
--with-bugurl=https://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --with-gcc-major-version-only
--enable-linker-build-id --enable-linux-futex --enable-gnu-indirect-function
--program-suffix=-11 --without-system-libunwind --with-tune=generic
--build=x86_64-suse-linux --host=x86_64-suse-linux --target=x86_64-suse-linux
--disable-multilib
And it still happens:
big-iron:/home/src/build/gcc-11.2.0/build$ find /opt/gcc11a/ -name s-oscons.ads
-exec grep -Hi Target_Name {} \;
/opt/gcc11a/lib64/gcc/x86_64-suse-linux/11/adainclude/s-oscons.ads:
Target_Name : constant String := "x86_64-suse-linux-gnu";
next prev parent reply other threads:[~2022-03-09 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 16:04 [Bug ada/104856] New: " bib_aab at hotmail dot com
2022-03-09 16:43 ` [Bug ada/104856] " ebotcazou at gcc dot gnu.org
2022-03-09 17:28 ` schwab@linux-m68k.org
2022-03-09 18:52 ` bib_aab at hotmail dot com [this message]
2022-03-09 18:54 ` bib_aab at hotmail dot com
2022-03-10 8:38 ` rguenth at gcc dot gnu.org
2022-03-10 9:20 ` ebotcazou 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-104856-4-QqrboJ3HFD@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).