[SOLVED] gcc-multilib vs cross32-gcc

skodabenz · 2010-08-14 06:05:41

What is the difference between gcc-multilib from http://supraverse.net/arch and cross32-gcc from community repo? I currently use gcc-multilib. If cross32-gcc provides the same functionality, how do I use this gcc for compiling 32-bit binaries.

I use gcc-multilib mainly to compile grub-legacy, grub2 for bios and grub2 for i386 UEFI. Can anyone try compiling grub2-efi-bzr (with _EFI_ARCH=i386 in the PKGBUILD) in Arch64 using cross32-gcc. I maintain that package and i am willing to modify the PKGBUILD to use cross32-gcc in case of cross-compiling. Thanks in advance.

Last edited by skodabenz (2011-01-30 19:37:06)

RetroX · 2010-08-14 14:33:45

cross32-gcc is actually just the 32-bit gcc package for 64-bit platforms. gcc-multilib includes just about every architecture, which is why it's 68 MB instead of about16.

Also, the gcc-multilib package is neat, but it doesn't seem to be maintained very well. It doesn't actually specify that it conflicts with the regular GCC, and it seems to be out of date currently.

Last edited by RetroX (2010-08-14 14:37:09)

skodabenz · 2010-08-14 17:34:05

I also like gcc-multilib. It is not possible to go completely 64-bit as programs like bootloaders, wine, some gpu driver utilities etc will run only as 32-bit (lib32-catalyst-utils). By Arch-devs' own admission, the grub PKGBUILD includes the following comment -

if [ "$CARCH" = "x86_64" ]; then
echo "this package has to be built on i686, won't compile on x86_64"
sleep 5

Also even grub2 for bios needs i386 elf output support which is provided only by gcc-multilib (or cross32-gcc). I do not need support for ppc, arm and other arch, but I do not like to install 1 more gcc package just for the sake of compiling 4 packages. I also don't like a 32-bit chroot as I need to install 2 arch versions of same package and a program running inside a chroot is not able to access files outside the chroot.

Is it possible to include gcc-multilib in the community repo by some TU?

dcc24 · 2010-08-14 19:47:29

The following was from an old thread at linuxforums.org. I think about this everytime the chicken/egg problem regarding gcc-multilib comes up:

It's obvious that you need a c compiler to compile a c compiler written in c. You either need a different version of c, or obtain the version you want (and the library) in a precompiled package. You could compile or cross-compile the source on another machine. The very first C compiler was probably written in a high level language.
This begs the question, how did the first person catch a cold?

Funny

Last edited by dcc24 (2010-08-14 19:47:48)

Marenz · 2010-08-16 18:43:52

RetroX wrote:

cross32-gcc is actually just the 32-bit gcc package for 64-bit platforms. gcc-multilib includes just about every architecture, which is why it's 68 MB instead of about16.
Also, the gcc-multilib package is neat, but it doesn't seem to be maintained very well. It doesn't actually specify that it conflicts with the regular GCC, and it seems to be out of date currently.

Well, yes, I don't have the time and right now not even the hardware to update it (my 64bit desktop is pretty far away right now), sorry about that.
If anyone is willing to step in here, be my guest. Just provide me with the packages. I can also offer write access to the related git repositroy with the PKGBUILDs.

--Marenz

Rip-Rip · 2010-08-16 19:16:57

dcc24 wrote:

The following was from an old thread at linuxforums.org. I think about this everytime the chicken/egg problem regarding gcc-multilib comes up:
It's obvious that you need a c compiler to compile a c compiler written in c. You either need a different version of c, or obtain the version you want (and the library) in a precompiled package. You could compile or cross-compile the source on another machine. The very first C compiler was probably written in a high level language.
This begs the question, how did the first person catch a cold?
Funny

Read this if you want to know how Ken Thompson wrote the first C compiler http://cm.bell-labs.com/who/ken/trust.html

RetroX · 2010-08-21 16:06:29

Marenz wrote:

RetroX wrote:
cross32-gcc is actually just the 32-bit gcc package for 64-bit platforms. gcc-multilib includes just about every architecture, which is why it's 68 MB instead of about16.
Also, the gcc-multilib package is neat, but it doesn't seem to be maintained very well. It doesn't actually specify that it conflicts with the regular GCC, and it seems to be out of date currently.

Well, yes, I don't have the time and right now not even the hardware to update it (my 64bit desktop is pretty far away right now), sorry about that.
If anyone is willing to step in here, be my guest. Just provide me with the packages. I can also offer write access to the related git repositroy with the PKGBUILDs.

--Marenz

Ah, that's fine. I guess that I'll just use the cross32-gcc.

And I didn't notice that this topic was a week old. D:

Sorry about that.

Last edited by RetroX (2010-08-21 16:07:45)

skodabenz · 2010-08-22 16:38:47

Official multilib support is coming - https://wiki.archlinux.org/index.php/Multilib_Project

Last edited by skodabenz (2010-08-23 06:49:28)

Arch Linux

#1 2010-08-14 06:05:41

[SOLVED] gcc-multilib vs cross32-gcc

#2 2010-08-14 14:33:45

Re: [SOLVED] gcc-multilib vs cross32-gcc

#3 2010-08-14 17:34:05

Re: [SOLVED] gcc-multilib vs cross32-gcc

#4 2010-08-14 19:47:29

Re: [SOLVED] gcc-multilib vs cross32-gcc

#5 2010-08-16 18:43:52

Re: [SOLVED] gcc-multilib vs cross32-gcc

#6 2010-08-16 19:16:57

Re: [SOLVED] gcc-multilib vs cross32-gcc

#7 2010-08-21 16:06:29

Re: [SOLVED] gcc-multilib vs cross32-gcc

#8 2010-08-22 16:38:47

Re: [SOLVED] gcc-multilib vs cross32-gcc

Board footer