Hello Santiago, Am Mon, Mar 03, 2025 at 01:53:25PM +0100 schrieb Santiago Vila: > El 3/3/25 a las 13:20, Helge Kreutzmann escribió: > > > I would really worry if it also fails to build that way. For now it > > > seems there is something wrong in your system, or maybe you have > > > discovered an undeclared build-conflict, or your testing system > > > contains packages not in testing. > > > > I pasted the build log on my system, if that gives you a hint? > > I see very funny differences: > > (in what follows, "before" is mine and "after" is yours) > > -checking for gcc version... 14 > +./configure: line 4566: SH_GCC_VERSION: command not found > > [...] > > -checking for gethostbyname in -lnsl... no > +checking for gethostbyname in -lnsl... yes > checking for socket in -lsocket... no > -checking for gethostbyname in -lnsl... (cached) no > +checking for gethostbyname in -lnsl... (cached) yes > > [...] > > -checking for attr/xattr.h... no > -checking for sys/acl.h... no > +./configure: line 7337: sh_CHECK_XATTR: command not found > +./configure: line 7350: sh_CHECK_POSIX_ACL: command not found > > Looks like your system is messed up in a very fundamental level.
Ok. So far, this has not been visible.
$ gcc --version
gcc (Debian 14.2.0-16) 14.2.0
Copyright (C) 2024 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> I wonder if this is the only package which fails to build for you,
> or maybe your gcc does not work at all.
It does work. A few hours ago I just complied a small programme, and
once in while I compile Debian packages (mainly to see if I can do an
L10n NMU).
> If gcc is really ok, I would try this:
>
> diff -ru good-tree bad-tree
>
> where good-tree is a samhain-4.1.4 directory where you have
> successfully built the package, and bad-tree is a directory
> where the build failed.
>
> To reduce the number of differences, compare the build in
> your native trixie system with a build in a trixie chroot.
Please find the diff attached. One == good-tree and two = bad-tree
> The config.log file created by configure is probably the
> most interesting one:
>
> diff -ru good-tree/config.log bad-tree/config.log
Also attached. It' pretty difficult to read, but e.g.
-gcc version 14.2.0 (Debian 14.2.0-17)
+gcc version 14.2.0 (Debian 14.2.0-16)
> Because configure performs a series of individual checks,
> you might want to find out which of those checks is failing,
> or giving a different result, to see what's wrong in your
> system.
I see one difference: On the "failing" system, both mawk and gawk are
installed, in the chroot only mawk.
But this does not change the "good" build (succeeds with both). So
this is a false hint.
Next, on the good (chroot) only:
configure:4515: checking for ld used by x86_64-linux-gnu-gcc
configure:4581: result: /usr/bin/X11/ld
configure:4588: checking if the linker (/usr/bin/X11/ld) is GNU ld
configure:4605: result: yes
Howver, ld is installed in both environments, and /usr/bin/X11/ld is
present the same way in both.
On the good build (only) I have:
configure:4663: checking for gcc version
configure:4679: result: 14
(and in subsequent lines these appear only on the good chroot).
Later on, only on the good system:
configure:6302: checking whether _POSIX_SOURCE is necessary
…
And then later on it diverges more.
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).
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/
samhian_config.log.diff.xz
Description: application/xz
samdiff.xz
Description: application/xz
signature.asc
Description: PGP signature
