I use Arch x86_64 - so far without a problem. But I've found recently that there's a few AUR packages that I'm unable to compile. (e.g., virtualbox-modules)
Seems like the build needs the /usr/include/gnu/stubs-32.h file, which isn't installed on my Arch64 system. (glibc installs stubs-64.h instead.)
But according to this thread, it appears that many distros work around this by having a 32-bit glibc package for this purpose:
http://gcc.gnu.org/ml/gcc-help/2007-12/msg00055.html
Does Arch have such a thing? Didn't look like it from surfing the packages in the repos (and AUR), but thought I'd ask anyway.
If not, I'm not opposed to writing a new packages for this, but I'm not sure quite how to build a 32-bit glibc package that doesn't conflict with the 64-bit one.
Anyone have any advice here?
Thanks,
DR
David Rosenstrauch wrote:
I use Arch x86_64 - so far without a problem. But I've found recently that there's a few AUR packages that I'm unable to compile. (e.g., virtualbox-modules)
Seems like the build needs the /usr/include/gnu/stubs-32.h file, which isn't installed on my Arch64 system. (glibc installs stubs-64.h instead.)
But according to this thread, it appears that many distros work around this by having a 32-bit glibc package for this purpose:
http://gcc.gnu.org/ml/gcc-help/2007-12/msg00055.html
Does Arch have such a thing? Didn't look like it from surfing the packages in the repos (and AUR), but thought I'd ask anyway.
If not, I'm not opposed to writing a new packages for this, but I'm not sure quite how to build a 32-bit glibc package that doesn't conflict with the 64-bit one.
Anyone have any advice here?
Thanks,
DR
Use a 32 bit chroot for 32 bit stuff. Arch doesn't (and hopefully will never ever) support multilib.
Glenn
RedShift schrieb:
Use a 32 bit chroot for 32 bit stuff. Arch doesn't (and hopefully will never ever) support multilib.
That are my hopes, too.
Having an arch32-chroot myself, I can say it works like a charm! There's a wonderfull article in the wiki: http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
* On Thursday, August 21 2008, Johannes Held wrote:
RedShift schrieb:
Use a 32 bit chroot for 32 bit stuff. Arch doesn't (and hopefully will never ever) support multilib.
That are my hopes, too.
A 32 bit chroot is an option, but you can get multilib functionalities from the various bin32- or lib32- prefixed packages in community and unsupported.
Those packages work for some people, but they aren't as robust as a chroot for reasons discussed here: http://archlinux.org/pipermail/arch-dev-public/2008-July/006907.html
Adam Vogt wrote:
- On Thursday, August 21 2008, Johannes Held wrote:
RedShift schrieb:
Use a 32 bit chroot for 32 bit stuff. Arch doesn't (and hopefully will never ever) support multilib.
That are my hopes, too.
A 32 bit chroot is an option, but you can get multilib functionalities from the various bin32- or lib32- prefixed packages in community and unsupported.
Those packages work for some people, but they aren't as robust as a chroot for reasons discussed here: http://archlinux.org/pipermail/arch-dev-public/2008-July/006907.html
Interesting discussion. (I read through the whole thread.)
Unfortunately, as Roman noted, this issue doesn't only come down to closed source apps. Virtualbox OSE apparently can't build without 32-bit support too.
http://archlinux.org/pipermail/arch-dev-public/2008-July/006944.html
DR
On Thu, Aug 21, 2008 at 7:41 PM, David Rosenstrauch darose@darose.net wrote:
Interesting discussion. (I read through the whole thread.)
Unfortunately, as Roman noted, this issue doesn't only come down to closed source apps. Virtualbox OSE apparently can't build without 32-bit support too.
http://archlinux.org/pipermail/arch-dev-public/2008-July/006944.html
DR
Arch64 is not designed and will never support multilib. If you care about that, use i686, or do all the hard work yourself.
Greg
Johannes Held wrote:
RedShift schrieb:
Use a 32 bit chroot for 32 bit stuff. Arch doesn't (and hopefully will never ever) support multilib.
That are my hopes, too.
Having an arch32-chroot myself, I can say it works like a charm! There's a wonderfull article in the wiki: http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
Ugh. Looks like a lot of work.
DR
David Rosenstrauch schrieb:
Johannes Held wrote:
http://wiki.archlinux.org/index.php/Arch64_Install_bundled_32bit_system
Ugh. Looks like a lot of work.
Basically no. Because the only thing you need to do, is telling pacman to do a "complete" new installation, but please into /arch32 and using i686-repofiles. tata.
using dchroot to start apps is really cool. I aliased "alias firefox = dchroot -d firefox" and it's simply no problem. Ok, sometimes I have to do two updates but that doesn't hurt!
On Donnerstag, 21. August 2008 18:40 David Rosenstrauch wrote:
Ugh. Looks like a lot of work.
Yes, that is for me the only but biggest disadvantage. It is a little bit strange to have two distributions only because you wants to compile one or two packages for your second 686 pc.
I'm a little bit disapointed, not from arch64 or another 64bit distribution, it is because as all starts i read that 64bit processors can run 32bit apps at the same time with nearly the same performance and so i was so i innocent to believe that i can install 64bit and 32bit apps together. Now some times later my favorit distribution use chroot and the other ones who use multilib be not my favorits.
Again, i can understand and respect that arch64 goes his way. But to install the 686 version of archlinux inside of arch64 is realy not a fantastic solution for me normal user and it sounds too hard because my dream is to use "gcc -m32" in a PKGBUILD without thinking too much about it. But what is perfect? -)
See you, Attila
On Thursday 21 August 2008 00:40:57 RedShift wrote:
Use a 32 bit chroot for 32 bit stuff. Arch doesn't (and hopefully will never ever) support multilib.
I'm not so optimistic. lots of users demand it, hence someone will implement it. Just like that retarded mad drivers... or the qt pacthes...
arch-general@lists.archlinux.org