From: ralfconn <mentadent47@yahoo.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: Mon, 25 Mar 2024 11:16:07 +0100 [thread overview]
Message-ID: <9d143578-1319-4e8f-8ff8-60deb26c728d@yahoo.com> (raw)
In-Reply-To: <924d722a-cdb8-0ed2-af36-d488a0277246@gmail.com>
Il 25/03/24 08:04, Dale ha scritto:
> Here is my update. I wanted to skip the system update and change
> profiles first. Then do the emerge -e world which would also update
> anything that was new as well. I'd only have to compile once tho.
> Well, that may have caused a problem. It may work for some but it
> didn't here. I first had to do my usual emerge -auDN world and get a
> clean run. I had one build to fail, had to work on that. Anyway, where
> it says update first, it is best to do that. It might work if you
> don't, might not. I'm now up to the part where I recompile everything.
> Oh the joy. At least it is a cool night so the extra heat will keep me
> warm. ROFL
>
As I noted in another thread, the profile switch involves a change in
the LDFLAGS, with the addition of the 'pack-relative-relocs' option.
https://rfc.archlinux.page/0023-pack-relative-relocs/ suggests that
adding this flag might trigger issues with tools not up-to-date. I
suppose that is why the gentoo devs instruct to rebuild binutils/gcc
before 'emerge -e', and that might be the reason why your first attempt
worked only partially.
BTW my update to split-usr 23-0 went pretty smoothly, next will be to go
with the merged-usr.
raf
next prev parent reply other threads:[~2024-03-25 10:16 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
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 [this message]
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=9d143578-1319-4e8f-8ff8-60deb26c728d@yahoo.com \
--to=mentadent47@yahoo.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