From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey.
Date: Sat, 23 Mar 2024 20:48:38 +0000 [thread overview]
Message-ID: <12406261.O9o76ZdvQC@rogueboard> (raw)
In-Reply-To: <c5a30119-4e15-9b02-05c7-f3a938d1dbe6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 9615 bytes --]
On Saturday, 23 March 2024 20:45:03 GMT Dale wrote:
> Howdy,
>
> I'm doing this in a chroot. This is *not* my live system. This is the
> mount info, in case it matters.
>
>
> root@fireball / # mount | grep gentoo
> /proc on /backup/gentoo-build/proc type proc (rw,relatime)
> sysfs on /backup/gentoo-build/sys type sysfs
> (rw,nosuid,nodev,noexec,relatime)
> debugfs on /backup/gentoo-build/sys/kernel/debug type debugfs
> (rw,nosuid,nodev,noexec,relatime)
> fusectl on /backup/gentoo-build/sys/fs/fuse/connections type fusectl
> (rw,nosuid,nodev,noexec,relatime)
> none on /backup/gentoo-build/sys/fs/cgroup type cgroup2
> (rw,nosuid,nodev,noexec,relatime,nsdelegate)
> devtmpfs on /backup/gentoo-build/dev type devtmpfs
> (rw,nosuid,noexec,size=10240k,nr_inodes=4104300,mode=755)
> devpts on /backup/gentoo-build/dev/pts type devpts
> (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
> tmpfs on /backup/gentoo-build/dev/shm type tmpfs (rw,nosuid,nodev,noexec)
> shm on /backup/gentoo-build/dev/shm type tmpfs
> (rw,nosuid,nodev,noexec,relatime)
> mqueue on /backup/gentoo-build/dev/mqueue type mqueue
> (rw,nosuid,nodev,noexec,relatime)
> /run on /backup/gentoo-build/run type tmpfs (rw,relatime)
> tmpfs on /backup/gentoo-build/run type tmpfs (rw,size=262144k,mode=755)
> root@fireball / #
>
>
> I've following the news item with this. This is early and already it
> has issues. Maybe switching is a bit early yet?? Anyway, this is what
> gcc fails with:
>
>
> make[3]: Entering directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libstdc++-v3/include' echo timestamp > stamp-pb
> echo timestamp > stamp-host
> make[3]: [Makefile:1820: x86_64-pc-linux-gnu/bits/largefile-config.h]
> Error 1 (ignored)
> echo 0 > stamp-namespace-version
> echo 1 > stamp-visibility
> echo 1 > stamp-extern-template
> echo 1 > stamp-dual-abi
> echo 1 > stamp-cxx11-abi
> echo 1 > stamp-allocator-new
> echo 'define _GLIBCXX_USE_FLOAT128 1' > stamp-float128
> sed -e '/^#pragma/b' \
>
>
> And further down, this:
>
>
> make[3]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libstdc++-v3/include' config.status: executing libtool commands
> config.status: executing generate-headers commands
> make[3]: Entering directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/libstdc++-v3/include' echo timestamp > stamp-pb
> echo timestamp > stamp-host
> make[3]: [Makefile:1819: x86_64-pc-linux-gnu/bits/largefile-config.h]
> Error 1 (ignored)
> make[3]: [Makefile:1820: x86_64-pc-linux-gnu/bits/largefile-config.h]
> Error 1 (ignored)
> echo 0 > stamp-namespace-version
> echo 1 > stamp-visibility
> echo 1 > stamp-extern-template
> echo 1 > stamp-dual-abi
> echo 1 > stamp-cxx11-abi
> echo 1 > stamp-allocator-new
> echo 'define _GLIBCXX_USE_FLOAT128 1' > stamp-float128
>
>
> And even further down:
>
>
> sed -e 's/\(UNUSED\)/_GLIBCXX_\1/g' \
> -e 's/\(GCC[ABCDEFGHIJKLMNOPQRSTUVWXYZ_]*_H\)/_GLIBCXX_\1/g' \
> -e 's/SUPPORTS_WEAK/__GXX_WEAK__/g' \
> -e 's/\([ABCDEFGHIJKLMNOPQRSTUVWXYZ_]*USE_WEAK\)/_GLIBCXX_\1/g' \
> -e 's,^#include "\(.*\)",#include <bits/\1>,g' \
> <
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/gcc-13-20240210/libstdc
> ++-v3/../libgcc/gthr-posix.h
> > x86_64-pc-linux-gnu/bits/gthr-default.h
>
> make[3]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libstdc++-v3/include' config.status: executing libtool commands
> config.status: executing generate-headers commands
> make[3]: Entering directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/libstdc++-v3/include' echo timestamp > stamp-pb
> echo timestamp > stamp-host
> make[3]: [Makefile:1819: x86_64-pc-linux-gnu/bits/largefile-config.h]
> Error 1 (ignored)
> make[3]: [Makefile:1820: x86_64-pc-linux-gnu/bits/largefile-config.h]
> Error 1 (ignored)
> echo 0 > stamp-namespace-version
> echo 1 > stamp-visibility
> echo 1 > stamp-extern-template
> echo 1 > stamp-dual-abi
> echo 1 > stamp-cxx11-abi
> echo 1 > stamp-allocator-new
> echo 'define _GLIBCXX_USE_FLOAT128 1' > stamp-float128
>
>
> Very close to the end, this:
>
>
> Makefile:901: warning: ignoring old recipe for target 'all-multi'
> make[8]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libatomic' make[8]: Entering directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libatomic' true DO=install multi-do # make
> /bin/mkdir -p
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib'
> /bin/sh ./libtool --mode=install /usr/bin/install -c libatomic.la
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib'
> libtool: install: /usr/bin/install -c .libs/libatomic.so.1.2.0
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib/libatom
> ic.so.1.2.0 libtool: install: (cd
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib &&
> { ln -s -f libatomic.so.1.2.0 libatomic.so.1 || { rm -f libatomic.so.1
> && ln -s libatomic.so.1.2.0 libatomic.so.1; }; })
> libtool: install: (cd
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib &&
> { ln -s -f libatomic.so.1.2.0 libatomic.so || { rm -f libatomic.so && ln
> -s libatomic.so.1.2.0 libatomic.so; }; })
> libtool: install: /usr/bin/install -c .libs/libatomic.lai
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib/libatom
> ic.la libtool: install: /usr/bin/install -c .libs/libatomic.a
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib/libatom
> ic.a libtool: install: chmod 644
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib/libatom
> ic.a libtool: install: /usr/x86_64-pc-linux-gnu/bin/ranlib
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib/libatom
> ic.a libtool: install: warning: remember to run `libtool --finish
> /usr/lib/../lib'
> make[8]: Nothing to be done for 'install-data-am'.
> make[8]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libatomic' make[7]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libatomic' make[6]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/32/libatomic' make[5]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/libatomic' /bin/mkdir -p
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64'
> /bin/sh ./libtool --mode=install /usr/bin/install -c libatomic.la
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64'
> libtool: install: /usr/bin/install -c .libs/libatomic.so.1.2.0
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libat
> omic.so.1.2.0 libtool: install: (cd
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64
> && { ln -s -f libatomic.so.1.2.0 libatomic.so.1 || { rm -f
> libatomic.so.1 && ln -s libatomic.so.1.2.0 libatomic.so.1; }; })
> libtool: install: (cd
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64
> && { ln -s -f libatomic.so.1.2.0 libatomic.so || { rm -f libatomic.so &&
> ln -s libatomic.so.1.2.0 libatomic.so; }; })
> libtool: install: /usr/bin/install -c .libs/libatomic.lai
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libat
> omic.la libtool: install: /usr/bin/install -c .libs/libatomic.a
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libat
> omic.a libtool: install: chmod 644
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libat
> omic.a libtool: install: /usr/x86_64-pc-linux-gnu/bin/ranlib
> /var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/image/usr/lib/../lib64/libat
> omic.a libtool: install: warning: remember to run `libtool --finish
> /usr/lib/../lib64'
> make[4]: Nothing to be done for 'install-data-am'.
> make[4]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/libatomic' make[3]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/libatomic' make[2]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build/x86_64-pc-linux-
> gnu/libatomic' make[1]: Leaving directory
> '/var/tmp/portage/sys-devel/gcc-13.2.1_p20240210/work/build'
> * ERROR: sys-devel/gcc-13.2.1_p20240210::gentoo failed (install phase):
> * (no error message)
>
>
>
> I saw where Peter mentioned in another thread gcc failing with no error
> message for him. This could be related. A solution to this may help
> more than just me. I'm not sure how to diagnose a failure when it gives
> no real error. Heck, having a error sometimes isn't much help. :/ I
> might add, the errors listed above didn't stop the compile until close
> to the end. It did seem to ignore them since it compiled a good while
> afterwards. I'm including in case those errors lead to the failure
> later on. They could be nothing or may be a clue.
>
> Open to ideas.
>
> Dale
>
> :-) :-)
Hmm ... my gcc is failing on one of my installations, with no error ... after
it built successfully once already, as part of the initial toolchain update.
:-/
OK, I'm out of ideas too. May have to sleep on this and look at it again
tomorrow.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-23 20:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 20:45 [gentoo-user] New profile, gcc-13.2.1_p20240210 fails to build. ATTN: Peter Humphrey Dale
2024-03-23 20:48 ` Michael [this message]
2024-03-23 21:28 ` Dale
2024-03-23 21:33 ` Michael
2024-03-23 21:49 ` Dale
2024-03-24 9:51 ` Paul Colquhoun
2024-03-25 7:04 ` Dale
2024-03-25 9:33 ` Michael
2024-03-25 10:16 ` ralfconn
2024-03-25 14:47 ` Peter Humphrey
2024-03-26 7:30 ` Paul Colquhoun
2024-03-25 14:44 ` Peter Humphrey
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=12406261.O9o76ZdvQC@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.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