From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2022.10.2 and 2023.07.1 released
Date: Thu, 21 Dec 2023 11:19:00 +0100 [thread overview]
Message-ID: <ZYQRFKcfImbZbP5u@lenoch> (raw)
In-Reply-To: <ZYQHiKZQq2CBlIXt@pengutronix.de>
On Thu, Dec 21, 2023 at 10:38:16AM +0100, Michael Olbrich wrote:
> Hi,
>
> On Wed, Dec 20, 2023 at 05:48:31PM +0100, Ladislav Michl wrote:
> > On Tue, Nov 21, 2023 at 08:46:31AM +0100, Michael Olbrich wrote:
> > > I'm happy to announce that I've just released OSELAS.Toolchain-2022.10.2
> > > and 2023.07.1.
> > >
> > > This is a bugfix only release. There are no major update. The relevant
> > > changes are:
> > >
> > > - gcc was updated to the 12-20231117 and 13-20231118 snapshot releases.
> > > Note, that for the 2023.07.1 toolchain the reported version is now
> > > 13.2.1 so the platformconfig in PTXdist BSPs must be updated
> > > accordingly.
> > > - glibc was updated to 2.36-121-g88d5d70b1e89 and 2.37-48-g8e20aedfd7fc in
> > > the respective stable branch.
> > > - All patches from the binutils stable branches that seemed relevant
> > > have been cherry-picked.
> > > - The gcc fortran compiler is now enabled in all Linux toolchains
> > >
> > > Download the release here:
> > > https://public.pengutronix.de/oselas/toolchain/
> > >
> > > Debian / Ubuntu Packages will be available at
> > > http://debian.pengutronix.de/
> >
> > I finally got time to update all my BSPs to newer toolchain. However, it does
> > not fly without force-overwrite:
> > ladis@lenoch:~$ sudo dpkg --force-overwrite -i /var/cache/apt/archives/oselas.toolchain-2023.07.1-arm-v7a-linux-gnueabi-gcc-13.2.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized-dbgsym_2023.07.1-1~deb12+1_amd64.deb
> > (Reading database ... 621067 files and directories currently installed.)
> > Preparing to unpack .../oselas.toolchain-2023.07.1-arm-v7a-linux-gnueabi-gcc-13.2.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized-dbgsym_2023.07.1-1~deb12+1_amd64.deb ...
> > Unpacking oselas.toolchain-2023.07.1-arm-v7a-linux-gnueabi-gcc-13.2.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized-dbgsym (2023.07.1-1~deb12+1) ...
> > dpkg: warning: overriding problem because --force enabled:
> > dpkg: warning: trying to overwrite '/usr/lib/debug/.build-id/0c/9b7ee1580684fbdac23548ca46c1c34408e49b.debug', which is also in package oselas.toolchain-2023.07.1-x86-64-unknown-linux-gnu-gcc-13.2.1-clang-16.0.6-glibc-2.37-binutils-2.40-kernel-6.3.6-sanitized-dbgsym 2023.07.1-1~deb12+1
> [...]
>
> Don't install the *-dbgsym packages unless you really need them. They
> contain the debug symbols for the compiler itself etc. not the target
> libraries. So you will only need them if you want to debug a crashing gcc
> or something like that.
Thanks, that's what I was doing, but turned out problem was too much pressure
on VM on build host, so random crashes occured.
> I'm not sure what those debug files are for, but my guess ist libLLVM.so
> or something like that. Stuff that does not change with the selected target
> architecture. And the builds are sufficiently reproducible that the
> build-id is the same.
Ah, that is very nice gotcha ;-)
> Regards,
> Michael
Thank you,
ladis
prev parent reply other threads:[~2023-12-21 10:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 7:46 Michael Olbrich
2023-12-20 16:48 ` Ladislav Michl
2023-12-21 9:38 ` Michael Olbrich
2023-12-21 10:19 ` Ladislav Michl [this message]
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=ZYQRFKcfImbZbP5u@lenoch \
--to=oss-lists@triops.cz \
--cc=ptxdist@pengutronix.de \
/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