Hi Christoph and Georgi, On 12/03/2012 15:20, Christoph Egger wrote:
Georgi Naplatanov<gosho@oles.biz> writes:My sbuild (0.62.5-1~bpo60+1) configuration is very simple: ~/.sbuildrc $distribution = 'unstable'; $chroot_mode = 'schroot';$maintainer_name='kfreebsd-amd64 Build Daemon (fasch)<buildd_kfreebsd-amd64-fasch@buildd.debian.org>'; $purge_build_directory="always"; $sbuild_mode = "buildd";
I'm not a sbuild expert (far from it...) but from sbuild manpage :
SBUILD_MODE
=> "buildd" (exit status does not report build failures)
for use in a buildd setup.
=> "buildd" also currently implies enabling of "legacy features"
such as chroot symlinks in the build directory and the creation
of current symlinks in the build directory.
Do you know which "legacy features" are enabled by this flag ?
As a side note, I've already had some issues with bind mount (aka
nullfs) and handling of $ORIGIN rpath handling with some kernel / libc
flavor (see [1] and [2]).
I know that it's not the same error but maybe there is some other hidden
breakage in eglibc like this one which create some internal ld.so
corruption ?
[1] http://anonscm.debian.org/viewvc/glibc-bsd/trunk/glibc-ports/kfreebsd/dl-origin.c?view=log [2] http://lists.debian.org/alpine.LRH.2.02.1108211305210.22182@sci.felk.cvut.cz
Regards, -- Damien