public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r9-9378] maintainer-scripts: Disable multilib when generating libstdc++ docs
Date: Tue, 20 Apr 2021 18:53:05 +0000 (GMT)	[thread overview]
Message-ID: <20210420185305.5D59D39960EC@sourceware.org> (raw)

https://gcc.gnu.org/g:9c01c3136aadf8777a95342184b9060e20e86a0a

commit r9-9378-g9c01c3136aadf8777a95342184b9060e20e86a0a
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Apr 8 14:48:23 2021 +0100

    maintainer-scripts: Disable multilib when generating libstdc++ docs
    
    This allows the docs to be generated on hosts without the necessary
    files present for multilib support.
    
    maintainer-scripts/ChangeLog:
    
            * generate_libstdcxx_web_docs: Add --disable-multilib to
            configure command.
    
    (cherry picked from commit acbbb82ea3e2ae145e59ffca6f1ec0699b5f7383)

Diff:
---
 maintainer-scripts/generate_libstdcxx_web_docs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/maintainer-scripts/generate_libstdcxx_web_docs b/maintainer-scripts/generate_libstdcxx_web_docs
index 74886356bc7..29572172761 100755
--- a/maintainer-scripts/generate_libstdcxx_web_docs
+++ b/maintainer-scripts/generate_libstdcxx_web_docs
@@ -43,7 +43,7 @@ do
   [ $dir == 'libstdc++-v3' ] || disabled_libs="$disabled_libs --disable-$dir"
 done
 set -x
-${SRCDIR}/configure --enable-languages=c,c++ --disable-gcc $disabled_libs --docdir=/docs
+${SRCDIR}/configure --enable-languages=c,c++ --disable-gcc --disable-multilib $disabled_libs --docdir=/docs
 eval `grep '^target=' config.log`
 make configure-target
 # If the following step fails with an error like


                 reply	other threads:[~2021-04-20 18:53 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=20210420185305.5D59D39960EC@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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).