public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/109051] New: Configure takes long time for multibuild of run-time libraries
Date: Tue, 07 Mar 2023 12:32:29 +0000	[thread overview]
Message-ID: <bug-109051-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109051

            Bug ID: 109051
           Summary: Configure takes long time for multibuild of run-time
                    libraries
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-linux-gnu
            Target: arm-linux-gnueabi

I've just noticed that a slower cross compiler build can be killer by a builder
service:

[   24s] + ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-languages=c,c++ --enable-checking=release --disable-werror
--with-gxx-include-dir=/usr/include/c++/13
--with-libstdcxx-zoneinfo=/usr/share/zoneinfo --enable-ssp --disable-libssp
--disable-libvtv --enable-cet=auto --disable-libcc1 --disable-plugin
--with-bugurl=https://bugs.opensuse.org/ '--with-pkgversion=SUSE Linux'
--with-slibdir=/usr/arm-suse-linux-gnueabi/sys-root/lib64 --with-system-zlib
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --with-gcc-major-version-only
--enable-linux-futex --enable-gnu-indirect-function --program-suffix=-13
--program-prefix=arm-none-eabi- --target=arm-none-eabi --disable-nls
--with-sysroot=/usr/arm-suse-linux-gnueabi/sys-root
--with-build-sysroot=/usr/arm-suse-linux-gnueabi/sys-root
--with-build-time-tools=/usr/arm-suse-linux-gnueabi/bin --with-newlib
--enable-multilib --with-multilib-list=aprofile,rmprofile
--disable-decimal-float --disable-libffi --disable-libgomp --disable-libmudflap
--disable-libquadmath --disable-shared --disable-threads --disable-tls
--disable-bootstrap --enable-link-mutex --disable-libsanitizer
--build=x86_64-suse-linux --host=x86_64-suse-linux
...
[ 1113s]   esac;                                                        \
[ 1113s] done
[ 1113s] make[3]: Leaving directory
'/home/abuild/rpmbuild/BUILD/gcc-13.0.1+git6506/obj-x86_64-suse-linux/arm-none-eabi/libgcc'
[ 1762s] make[1]: Entering directory
'/home/abuild/rpmbuild/BUILD/gcc-13.0.1+git6506/obj-x86_64-suse-linux'
[ 1762s] Checking multilib configuration for libstdc++-v3...
[ 1762s] mkdir -p -- arm-none-eabi/libstdc++-v3
[ 1762s] Configuring in arm-none-eabi/libstdc++-v3

As seen, at this place there's no output and the step takes 600s on a pretty
fast machine. So please, emit an output so that it doesn't get killer by a
builder.

             reply	other threads:[~2023-03-07 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 12:32 marxin at gcc dot gnu.org [this message]
2023-03-07 12:34 ` [Bug bootstrap/109051] " marxin at gcc dot gnu.org
2023-03-07 12:38 ` rguenth at gcc dot gnu.org
2023-03-07 12:41 ` marxin at gcc dot gnu.org
2023-03-07 13:30 ` schwab@linux-m68k.org
2023-03-29 23:55 ` pinskia at gcc dot gnu.org

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=bug-109051-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).