[arch-dev-public] Request for help: 32bit chroot handling in makechrootpkg
So I looked at this for about 5 minutes... and broke things. I have a 32bit chroot on my 64bit box, but cannot seem to work a call to "linux32" in properly. I am hoping that someone with more experience could look into this. I do know that "linux32 chroot /var/archroot32 /bin/bash" works find... but doing the same thing (linux32 chroot <path> <script>) in makechrootpkg tosses some ELIBBAD at me... So I gave up. If someone would mind giving me a hand, that'd be great. It would give the 64bit build machine the opportunity to work for i686 as well (for those out there with only 64bit hardware). Thanks in advance, Aaron
Aaron Griffin wrote:
So I looked at this for about 5 minutes... and broke things.
I have a 32bit chroot on my 64bit box, but cannot seem to work a call to "linux32" in properly. I am hoping that someone with more experience could look into this.
I do know that "linux32 chroot /var/archroot32 /bin/bash" works find... but doing the same thing (linux32 chroot <path> <script>) in makechrootpkg tosses some ELIBBAD at me...
So I gave up. If someone would mind giving me a hand, that'd be great. It would give the 64bit build machine the opportunity to work for i686 as well (for those out there with only 64bit hardware).
Thanks in advance, Aaron
I've had a similar problem with my makechroot scripts which I solved simply by running linux32 makechroot <params>. So yeah, the parent process already is a level down. Ugly but works. If you'd like, I could have a look at it. Cheers, Alex
Aaron Griffin schrieb:
I have a 32bit chroot on my 64bit box, but cannot seem to work a call to "linux32" in properly. I am hoping that someone with more experience could look into this.
I do know that "linux32 chroot /var/archroot32 /bin/bash" works find... but doing the same thing (linux32 chroot <path> <script>) in makechrootpkg tosses some ELIBBAD at me...
I have never seen such an error. However, you can chroot without using linux32. The only thing that will break is building the kernel or modules and maybe some tool that checks the uname output (I've only seen that in scripts that come with commercial applications). While it is desirable to have linux32 run automatically in such cases, it is not mandatory for everything. I use 'linux32 dhcroot ...' in scripts by the way and it always works.
On Tue, Apr 8, 2008 at 8:19 AM, Thomas Bächler
Aaron Griffin schrieb:
I have a 32bit chroot on my 64bit box, but cannot seem to work a call to "linux32" in properly. I am hoping that someone with more experience could look into this.
I do know that "linux32 chroot /var/archroot32 /bin/bash" works find... but doing the same thing (linux32 chroot <path> <script>) in makechrootpkg tosses some ELIBBAD at me...
I have never seen such an error. However, you can chroot without using linux32. The only thing that will break is building the kernel or modules and maybe some tool that checks the uname output (I've only seen that in scripts that come with commercial applications).
Doesn't every autoconf script call uname at some point to form the build system type?
While it is desirable to have linux32 run automatically in such cases, it is not mandatory for everything.
I use 'linux32 dhcroot ...' in scripts by the way and it always works.
Dan McGee schrieb:
I have never seen such an error. However, you can chroot without using linux32. The only thing that will break is building the kernel or modules and maybe some tool that checks the uname output (I've only seen that in scripts that come with commercial applications).
Doesn't every autoconf script call uname at some point to form the build system type?
No, they check for CARCH and/or CHOST, at least if they are present. configure always worked in the chroots, even when I didn't know about linux32.
participants (4)
-
Aaron Griffin
-
Alexander Baldeck
-
Dan McGee
-
Thomas Bächler