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] Update build-many-glibcs.py for binutils ia64 obsoletion. Date: Thu, 13 Aug 2020 18:51:25 +0000 (GMT) [thread overview] Message-ID: <20200813185125.974B73857C5B@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=23a7896d065a99057c06a1bd22c2bbee175b0ae4 commit 23a7896d065a99057c06a1bd22c2bbee175b0ae4 Author: Joseph Myers <joseph@codesourcery.com> Date: Thu Aug 13 18:51:10 2020 +0000 Update build-many-glibcs.py for binutils ia64 obsoletion. Since binutils has obsoleted ia64 support, use --enable-obsolete for now when configuring binutils for ia64 in build-many-glibcs.py (which requires adding support for architecture-specific binutils configure options there). As with other obsoletions, the removal of support for ia64 in any of (binutils, GCC, Linux kernel) should imply its removal from glibc. Tested with build-many-glibcs.py for ia64-linux-gnu (compilers and glibcs build). Diff: --- scripts/build-many-glibcs.py | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py index 325591b2c6..3bd5fd795e 100755 --- a/scripts/build-many-glibcs.py +++ b/scripts/build-many-glibcs.py @@ -212,7 +212,8 @@ class Context(object): os_name='gnu') self.add_config(arch='ia64', os_name='linux-gnu', - first_gcc_cfg=['--with-system-libunwind']) + first_gcc_cfg=['--with-system-libunwind'], + binutils_cfg=['--enable-obsolete']) self.add_config(arch='m68k', os_name='linux-gnu', gcc_cfg=['--disable-multilib']) @@ -1264,7 +1265,8 @@ class Config(object): """A configuration for building a compiler and associated libraries.""" def __init__(self, ctx, arch, os_name, variant=None, gcc_cfg=None, - first_gcc_cfg=None, glibcs=None, extra_glibcs=None): + first_gcc_cfg=None, binutils_cfg=None, glibcs=None, + extra_glibcs=None): """Initialize a Config object.""" self.ctx = ctx self.arch = arch @@ -1283,6 +1285,10 @@ class Config(object): self.first_gcc_cfg = [] else: self.first_gcc_cfg = first_gcc_cfg + if binutils_cfg is None: + self.binutils_cfg = [] + else: + self.binutils_cfg = binutils_cfg if glibcs is None: glibcs = [{'variant': variant}] if extra_glibcs is None: @@ -1316,7 +1322,7 @@ class Config(object): '--disable-gdbserver', '--disable-libdecnumber', '--disable-readline', - '--disable-sim']) + '--disable-sim'] + self.binutils_cfg) if self.os.startswith('linux'): install_linux_headers(LinuxHeadersPolicyForBuild(self), cmdlist) self.build_gcc(cmdlist, True)
reply other threads:[~2020-08-13 18:51 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=20200813185125.974B73857C5B@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: linkBe 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).