public inbox for glibc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org>
To: glibc-cvs@sourceware.org
Subject: [glibc] build-many-glibcs.py: Do not build C++ PCHs by default
Date: Wed, 18 Dec 2019 07:48:00 -0000	[thread overview]
Message-ID: <20191218074800.14769.qmail@sourceware.org> (raw)

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

commit 3aec0c3912859bcf0432c700a8fbdcb23b45545f
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Dec 17 16:23:08 2019 +0100

    build-many-glibcs.py: Do not build C++ PCHs by default
    
    They are not used during the subsequent glibc build, so creating them
    merely wastes time.

Diff:
---
 scripts/build-many-glibcs.py | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/scripts/build-many-glibcs.py b/scripts/build-many-glibcs.py
index 193d497..92cc613 100755
--- a/scripts/build-many-glibcs.py
+++ b/scripts/build-many-glibcs.py
@@ -1382,9 +1382,12 @@ class Config(object):
         else:
             tool_build = 'gcc'
             # libsanitizer commonly breaks because of glibc header
-            # changes, or on unusual targets.
+            # changes, or on unusual targets.  C++ pre-compiled
+            # headers are not used during the glibc build and are
+            # expensive to create.
             if not self.ctx.full_gcc:
-                cfg_opts += ['--disable-libsanitizer']
+                cfg_opts += ['--disable-libsanitizer',
+                             '--disable-libstdcxx-pch']
             langs = 'all' if self.ctx.full_gcc else 'c,c++'
             cfg_opts += ['--enable-languages=%s' % langs,
                          '--enable-shared', '--enable-threads']


                 reply	other threads:[~2019-12-18  7:48 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=20191218074800.14769.qmail@sourceware.org \
    --to=fw@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).