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 --disable-gdbserver in build-many-glibcs.py.
Date: Mon, 10 Feb 2020 22:18:00 -0000	[thread overview]
Message-ID: <20200210221827.126984.qmail@sourceware.org> (raw)

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

commit a179673f3d46e25f2a71c2a8f0c64b6d71ccaa6e
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Mon Feb 10 22:17:59 2020 +0000

    Use --disable-gdbserver in build-many-glibcs.py.
    
    Now that binutils-gdb has gdbserver at top level, an extra
    --disable-gdbserver configure option is needed when configuring
    binutils from a git checkout to avoid it also building gdbserver
    unnecessarily (although fairly harmlessly).  This patch updates the
    options used in build-many-glibcs.py accordingly (although this might
    end up not being needed depending on what happens regarding whether
    gdbserver gets built for host != target).
    
    Tested with a build-many-glibcs.py compilers build for
    aarch64-linux-gnu using binutils-gdb master.

Diff:
---
 scripts/build-many-glibcs.py | 1 +
 1 file changed, 1 insertion(+)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 3625e66..6add364 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -1290,6 +1290,7 @@ class Config(object):
         cmdlist.use_path(self.bindir)
         self.build_cross_tool(cmdlist, 'binutils', 'binutils',
                               ['--disable-gdb',
+                               '--disable-gdbserver',
                                '--disable-libdecnumber',
                                '--disable-readline',
                                '--disable-sim'])


                 reply	other threads:[~2020-02-10 22:18 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=20200210221827.126984.qmail@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).