Hello Santiago, thanks for your review. Am Mon, Mar 03, 2025 at 03:44:13PM +0100 schrieb Santiago Vila: > -gcc version 14.2.0 (Debian 14.2.0-17) > +gcc version 14.2.0 (Debian 14.2.0-16) > > Note: gcc-14 in trixie is still at version 14.2.0-16, so you > are still comparing the good build you made in unstable > with the build made natively on your trixie system.
Yes, currently I only have an Unstable and Stable chroot, not Trixie,
but of course I can install it.
> As a result, the diff has a lot of unwanted noise.
Yes, that's true. For my "analysis" I looked at the vimdiff, where I
had hoped to see the cause.
> Either upgrade your system to unstable and compare
> good and bad builds both made in unstable, or build it in a
> trixie chroot to compare good and bad builds both made in trixie.
Well, the first is not an option (I run in Testing on purpose). If I
find time I can maybe try the latter.
> Also, use deborphan from bookworm to remove any package which
> you don't really need, including binutils-gold (I don't think
> it's related but who knows).
No, unfortunately removing this and binutils-gold-x86-64-linux-gnu did
not change anything.
And I checked deborphan - it's removed from Debian for serious reasons
by it's maintainer, so I would not want to install an old version on
the system.
> If it still fails, you could start adding packages to your chroot which
> you know they are also installed in your native system until
> the build also fails in the chroot. If there is an undeclared
> build-conflict, that would be the way to tell.
Well, if I had an idea *which* package could cause this potential
hidden build-conflict I could try this, but for randomly adding
packages I'm afraid I'm lacking the time.
> > I guess my complier / building knowledge is more than exceeded here,> so
> > sorry, that I cannot be of any help further (but of course, I can
> > run further commands if necessary).
>
> If everything else fails, consider reinstalling your testing system
> from scratch. At some point, doing that will be less time-consuming
> than debugging the problem. Your system seems to be messed up.
Well, for debugging a potential problem in samhain (a programm I've
never used) this is a bit big "workload". And I'm really not conviced
that my system "is messed up". All other workloads, including
occassionally building programms, work fine (except the bugs
you can find under my name in the BTS, of course).
So if I find time today, I'll check the Trixie chroot output, but
otherwise I guess there's no further debugging possibly right now.
Greetings
Helge
--
Dr. Helge Kreutzmann deb...@helgefjell.de
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
