From: Joseph Myers <josmyers@redhat.com>
To: libc-alpha@sourceware.org
Subject: Use --enable-obsolete in build-many-glibcs.py for nios2-linux-gnu
Date: Fri, 19 Apr 2024 16:51:47 +0000 (UTC) [thread overview]
Message-ID: <6b21bfdb-3ed6-a554-4fd0-cb47d038a7dd@redhat.com> (raw)
Until GCC removes Nios II support (at which point we should do so as
well), this is now needed for GCC 14 / mainline to build for
nios2-linux-gnu target.
Tested with build-many-glibcs.py (GCC mainline) for nios2-linux-gnu.
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index ecc743e672..35dac538e5 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -358,7 +358,8 @@ class Context(object):
{'variant': 'n64',
'ccopts': '-mabi=64'}])
self.add_config(arch='nios2',
- os_name='linux-gnu')
+ os_name='linux-gnu',
+ gcc_cfg=['--enable-obsolete'])
self.add_config(arch='or1k',
os_name='linux-gnu',
variant='soft',
--
Joseph S. Myers
josmyers@redhat.com
next reply other threads:[~2024-04-19 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 16:51 Joseph Myers [this message]
2024-04-19 16:59 ` Use --enable-obsolete in build-many-glibcs.py for nios2-linux-gnu H.J. Lu
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b21bfdb-3ed6-a554-4fd0-cb47d038a7dd@redhat.com \
--to=josmyers@redhat.com \
--cc=libc-alpha@sourceware.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).