From: Josip Rodin <[EMAIL PROTECTED]>
Date: Tue, 30 Oct 2007 00:37:13 +0100
> I'd try doing a debootstrap of lenny (that's Debian "testing"),
> and then inside it, run one or more of those 'dpkg-query -S libc.so.6'.
Thanks for the info.
While waiting for you to reply I created a lenny buildd
build root on my SunFire 280R using:
debootstrap --variant=buildd lenny /org/buildd/chroots/lenny \
http://mirrors.kernel.org/debian
basically following roughly the instructions at:
http://www.debian.org/devel/buildd/setting-up
And then once chroot'ed into the lenny build root you have
to setup a few manual things like /proc, /sys/, and /dev/pts
mounts for anything to work:
chroot /org/buildd/chroots/lenny
mount -t proc none /proc
mount -t sysfs none /sys
mount -t devpts none /dev/pts
So, it's a lot more than just running the appropriate debootstrap
command.
I have done a GCC package build and am now running a libc6 build under
this lenny chroot and haven't hit any problems yet.
This is with a stock 2.6.23.1 kernel.
BTW, in your buildroot, can you do something like:
strace -o x.log dpkg-query -S libc.so.6
and send me that "x.log" file?
That might give some important clues.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
