public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] Use --enable-obsolete in build-many-glibcs.py for nios2-linux-gnu
Date: Fri, 19 Apr 2024 17:04:46 +0000 (GMT)	[thread overview]
Message-ID: <20240419170446.5BBBA3849ACF@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=f6d18bea387676e774e18ce410ace8c33a5c3511

commit f6d18bea387676e774e18ce410ace8c33a5c3511
Author: Joseph Myers <josmyers@redhat.com>
Date:   Fri Apr 19 17:03:56 2024 +0000

    Use --enable-obsolete in build-many-glibcs.py for nios2-linux-gnu
    
    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:
---
 scripts/build-many-glibcs.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

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',

                 reply	other threads:[~2024-04-19 17:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240419170446.5BBBA3849ACF@sourceware.org \
    --to=jsm28@sourceware.org \
    --cc=glibc-cvs@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).