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.
I wonder if this is the only package which fails to build for you,
or maybe your gcc does not work at all.
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.
The config.log file created by configure is probably the
most interesting one:
diff -ru good-tree/config.log bad-tree/config.log
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.
Thanks.
