public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Samuel Thibault <sthibaul@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] hurd: Enable x86_64 build script
Date: Tue,  2 May 2023 20:24:17 +0000 (GMT)	[thread overview]
Message-ID: <20230502202417.4C5C93858D33@sourceware.org> (raw)

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

commit cd87e368439ce97d2a2c95894e1851f4c0ff4443
Author: Samuel Thibault <samuel.thibault@ens-lyon.org>
Date:   Tue May 2 21:40:31 2023 +0200

    hurd: Enable x86_64 build script
    
    This now passes crossbuilds.

Diff:
---
 NEWS                         | 5 +++++
 README                       | 2 +-
 scripts/build-many-glibcs.py | 3 +++
 3 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/NEWS b/NEWS
index 40964d2ee0..054d81fc81 100644
--- a/NEWS
+++ b/NEWS
@@ -24,6 +24,11 @@ Major new features:
 * A new tunable, glibc.pthread.stack_hugetlb, can be used to disable
   Transparent Huge Pages (THP) in stack allocation at pthread_create.
 
+* Support for x86_64 running on Hurd has been added.  This port requires
+  as least binutils 2.40 and GCC 13:
+
+    - x86_64-gnu
+
 Deprecated and removed features, and other changes affecting compatibility:
 
 * In the Linux kernel for the hppa/parisc architecture some of the
diff --git a/README b/README
index 63f3a1bebf..9532b97986 100644
--- a/README
+++ b/README
@@ -12,7 +12,7 @@ implement the operating system behavior seen by user applications.
 In GNU/Hurd systems, it works with a microkernel and Hurd servers.
 
 The GNU C Library implements much of the POSIX.1 functionality in the
-GNU/Hurd system, using configurations i[4567]86-*-gnu.
+GNU/Hurd system, using configurations i[4567]86-*-gnu and x86_64-gnu.
 
 When working with Linux kernels, this version of the GNU C Library
 requires Linux kernel version 3.2 or later.
diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 97b6862167..95726c4a29 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -465,6 +465,9 @@ class Context(object):
                                        'ccopts': '-m32 -march=i486'},
                                       {'arch': 'i586',
                                        'ccopts': '-m32 -march=i586'}])
+        self.add_config(arch='x86_64',
+                        os_name='gnu',
+                        gcc_cfg=['--disable-multilib'])
 
     def add_config(self, **args):
         """Add an individual build configuration."""

                 reply	other threads:[~2023-05-02 20:24 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=20230502202417.4C5C93858D33@sourceware.org \
    --to=sthibaul@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).