this is a tracker for all such fun issues related to the new x32 ABI. no reports should be here, just blocking bugs.
most packages should "just work" when compiled for x32, but i imagine we'll hit some that have certain assumptions either in the C code (like sizeof(unsigned long) == sizeof(time_t)), or the C/asm code (like __x64_64__ is always sizeof(void*) == 8).
see $URL for porting tips and possible patches by other projects
Quick question: Will I be able to run 32-bit prebuilt binaries without having to install emul packages? As far as I can understand this stuff, this won't work. So, what's the point? It will be so darn difficult to get necessary-evil pre-built binaries like skype, nvidia-drivers, adobe flash etc. Now, we will have to beg them to port their applications to a third ABI? 64-bit took ages for them...:(
the x86 abi ("32-bit") will behave the same -- you need the emul packages. otherwise, this isn't the location to debit the merits of x32.
not sure it belongs here, but https://bugs.gentoo.org/show_bug.cgi?id=447408 didn't show up when building with amd64 abi, only with x32. to some it might be a show-stopper just like all of the above. btw, I found another problem, with compiling ffmpeg, something about -fPIC missing.
(In reply to comment #3)
it is not. keep comments specific to a bug on the respective bug.
Just converted my internet gateway machine to Gentoo X32, as well as adding x32 multilib to my main PC, I'm surprised how few problems I've encountered.
I've just modified the rust eclass/ebuild to be able to bootstrap x32 from the amd64 dev-lang/rust-bin. Works really well with system-llvm (llvm14). Much lower memory usage from rustc and a good bit faster on my old PhenomII.
I'll create a new bug for it.
I know it's really late to suggest this, but why not have x32 abi enabled for the toolchain with the default amd64 profile? It would make porting/bug fixing much easier, and would probably get more people involved. All the infrastructure is already in place and working via abi_x86_32 multilib support.
As I mentioned above, I have added this to my existing installation, and it works fine, but it's far from an easy process to add it after the fact.
(In reply to Steven Newbury from comment #6)
> I know it's really late to suggest this, but why not have x32 abi enabled
> for the toolchain with the default amd64 profile?
The downside is increased build times and install size for glibc and gcc.
Also, existing installs would need to take special action to enable x32: users would need to enable sys-libs/glibc[multilib-boostrap] temporarily.