On Tue, 22 Mar 2011 20:19:15 -0400, Daniel Kahn Gillmor <[email protected]> wrote: > On 03/22/2011 08:11 PM, micah anderson wrote: > > > > I also encounter this issue, and Jamie's work-around works for me, at > > least so far as building the image. I'm not sure if the following ldd > > error is of concern: > > I'm not sure that this is related to http://bugs.debian.org/618260 -- do > you have reason to believe that this is related to the creation of > /dev/ttyS0 or other device nodes?
The reason I have to believe that it is related is that I got the same
error that jamie did.
> > ...
> > debirf> modules complete
> > debirf> creating debirf initrd ('nested')...
> > /usr/bin/ldd: line 161: /lib64/ld-linux-x86-64.so.2: cannot execute binary
> > file
> > 2577 blocks
> > 223 blocks
> > debirf> creating rootfs.cgz...
> > 339021 blocks
> > debirf> creating wrapper cgz...
> > 148195 blocks
> > debirf> debirf initrd created.
> > debirf> kernel: /var/tmp/debirf/rescue/vmlinuz-2.6.32-5-686-bigmem
> > debirf> initrd:
> > /var/tmp/debirf/rescue/debirf-rescue_squeeze_2.6.32-5-686-bigmem.cgz
>
>
> You appear to be building an i386 image, but nest is trying to use
> ld-linux-x86-64 (which is amd64). are you doing some sort of cross-arch
> build? If this is related to cross-architecture issues, could you file
> a separate bug about it?
No, I'm not doing anything fancy like cross-arch building.
micah
pgpGYcBDKLQMu.pgp
Description: PGP signature
