On Mon, 2009-10-26 at 18:14 +0100, Frans Pop wrote: > On Monday 26 October 2009, Ian Campbell wrote: > > I tried downgrading binutils, as you suggested in your next mail, to > > 2.19.91.20091006-1 from testing and still saw no issues. > > Hmmm. Another option is that it's due to a libc version skew. > > During a build libc6 is copied from the host system (because we need the > corresponding -pic), while libnss-* is unpacked from udebs. > So it could be that the buildds have a version of libc which really doesn't > provide the symbol. > > /me tests this theory by firing up his armel box, which promptly reproduces > the error > > After updating the system the problem disappears. So, that confirms the > reason is outdated buildd environments after an API change in libc (2.9 -> > 2.10). Nice one, thanks! I downgraded my chroot libc to 2.9-25 and reproduced the issue also. That libc has no _nss_files_parse_sgent, as expected: $ objdump -T /lib/libc.so.6 | grep nss_files_parse 00096c60 g DF .text 000002d0 GLIBC_PRIVATE _nss_files_parse_pwent 00095810 g DF .text 000002f5 GLIBC_PRIVATE _nss_files_parse_grent 000d1c60 g DF .text 000003d2 GLIBC_PRIVATE _nss_files_parse_spent > The first 2.10 upload was 18 Okt, so the problem should be only > about a week old. Is there a way to contact the build machine maintainers? Other than hoping they read this thread? Ian. -- Ian Campbell Quod erat demonstrandum. [Thus it is proven. For those who wondered WTF QED means.]
Attachment:
signature.asc
Description: This is a digitally signed message part