FS#24271 - [gcc] gcc_pure64.patch

Attached to Project: Arch Linux
Opened by Jan Alexander Steffens (heftig) - Saturday, 14 May 2011, 09:57 GMT
Last edited by Allan McRae (Allan) - Thursday, 30 June 2011, 15:34 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture x86_64
Severity Very Low
Priority Low
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

gcc_pure64.patch changes the linker location for the 32-bit linker from /lib/ld-linux.so.2 to
/lib32/ld-linux.so.2. I had to revert that for gcc-multilib, since we do not use /lib32 at all (and neither do any 32-bit binaries, as far as I know).

Please use the gcc_pure64.patch from gcc-multilib. This would make it a tad easier to maintain for me.

Since core GCC has no multilib support, I don't think this results in any changes.
This task depends upon

Closed by  Allan McRae (Allan)
Thursday, 30 June 2011, 15:34 GMT
Reason for closing:  Won't implement
Additional comments about closing:  See final comment
Comment by Rob McCathie (korrode) - Thursday, 16 June 2011, 15:41 GMT
Is this patch needed at all?
My understanding is most distro's 64 bit releases keep the dynamic linker in /lib64, plus that's how upstream does it, why do we deviate?

I know of at least one distro that binaries I produce do not run on (out-of-the-box), being openSUSE, which does not by default provide a symlink in /lib (and why should they, by upstream standards they don't have any need to).

Sorry if there's some important reason why this pacth is needed that i'm just not seeing/understanding.
Comment by Allan McRae (Allan) - Friday, 17 June 2011, 08:34 GMT
Arch x86_64 is a pure 64-bit implementation (but now with optional multilib...). So the /lib64 folder makes no sense.
Comment by Rob McCathie (korrode) - Saturday, 18 June 2011, 08:14 GMT
Still seems like unnecessary modifications to upstream source. I compiled the gcc package without the patch being applied and now binaries i compile are looking for the dynamic linker in /lib64, which works on both Arch (due to existing symlink) and other distros, so i'm happy... there's already a few packages I compile myself rather than using what's in the repos, guess one more wont hurt.
Comment by Allan McRae (Allan) - Thursday, 30 June 2011, 15:34 GMT
I'm going to close this as a won't fix for the following reason. Arch64 is designed to be pure 64 bit. That means /lib is for 64bit libraries. In fact, by default that is all we should have. I am 95% sure I can get rid of the /lib64 folder and will do this in a future toolchain update.

Putting the 32bit linker (ld-linux.so.2) in /lib is wrong. It should go in /lib32. The use of /usr/lib32 for all other 32bit libraries just confirms this.

Loading...