Re: armel qualification for Wheezy
On Thu, 2012-05-24 at 15:36 -0400, Lennart Sorensen wrote:
> On Thu, May 24, 2012 at 07:12:25PM +0100, Tixy wrote:
> > On Thu, 2012-05-24 at 12:22 -0400, Lennart Sorensen wrote:
> > > How are you doing the build using qemu's cpu emulator? I remember last
> > > I played with it I had issues with shared libraries where the command
> > > i wanted to run needed to find its shared libraries, but if I set the
> > > LD_LIBRARY_PATH, then qemu tried to use the other CPUs libraries and
> > > wouldn't run. Has this been fixed somehow?
> > >
> > > Static binaries were fine of course.
> >
> > Here is the crib sheet I wrote when I set this up, it was on a Debian
> > Wheezy system, but my ARM chroot contains Ubuntu Precise as that is what
> > I am targeting in my day job. (Hopefully Debian will work too.)
> >
> >
> > # in these instructions "/arm" is the directory where I installed my
> > # chroot and "tixy" is my linux username, replace as appropriate...
> > #
> > # /data is where I have all my source code and other files so I add that
> > # to schroot fstab below, do similar with directories where you have
> > # files you want to access inside the chroot. (Note, home directories
> > # are already available.)
> >
> > su
> > apt-get install debootstrap qemu-user-static binfmt-support schroot
> > debootstrap --foreign --arch=armhf --variant=buildd precise /arm \
> > http://ports.ubuntu.com/ubuntu-ports
> > cp /usr/bin/qemu-arm-static /arm/usr/bin
> > chroot /arm
> > /debootstrap/debootstrap --second-stage
> > exit
> >
> > # Add to /etc/schroot/schroot.conf
> > [arm]
> > description=ARM Chroot
> > type=directory
> > directory=/arm
> > users=tixy
> > groups=tixy
> > root-groups=root
> > aliases=default
> >
> > # Edit /etc/schroot/default/fstab to add
> > /data /data none rw,bind 0 0
> > /run /run none rw,bind 0 0
> >
> > # Edit /arm/etc/apt/sources.list to have
> > deb http://ports.ubuntu.com/ precise main universe
> > deb-src http://ports.ubuntu.com/ precise main universe
> > deb http://ports.ubuntu.com/ precise-security main universe
> > deb-src http://ports.ubuntu.com/ precise-security main universe
> > deb http://ports.ubuntu.com/ precise-updates main universe
> > deb-src http://ports.ubuntu.com/ precise-updates main universe
> >
> > schroot -c arm
> > adduser tixy
> > usermod -a -G sudo tixy
> > # As above doesn't seem to work, edit /etc/sudoes to add
> > tixy ALL=(ALL:ALL) ALL
> > exit
> > exit
> >
> > # Any time you want to enter the chroot do
> >
> > schroot -c arm
>
> OK, so the qemu is actually static. That probably solves the problem
> I had with it a few years ago.
>
> Where does anything tell the system to use qemu to run stiff?
>
> I could understand if binmisc was setup for it, but I see nothing that
> should make it get used.
Magic? ;-) Something in the packaging of binfmt-support and/or
qemu-user-static?
I was just following instructions I picked up on the web. I can assure
you the work because I had a disk crash a while back and did a system
re-install including following these instructions to setup my ARM chroot
again. (That's one of the reasons I write my own crib sheets when I do a
task like this :-)
--
Tixy
Reply to: