This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] ARM: Use different linker path for hardfloat ABI
- From: Konstantinos Margaritis <konstantinos dot margaritis at linaro dot org>
- To: Mike Frysinger <vapier at gentoo dot org>
- Cc: cross-distro at lists dot linaro dot org, Dennis Gilmore <dennis at gilmore dot net dot au>, libc-ports at sourceware dot org, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>, Richard Earnshaw <rearnsha at arm dot com>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Thu, 5 Apr 2012 18:24:15 +0300
- Subject: Re: [PATCH] ARM: Use different linker path for hardfloat ABI
- References: <20120329193401.GA14860@dannf.org> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org>
On Thu, 5 Apr 2012 11:08:56 -0400
Mike Frysinger <email@example.com> wrote:
> i don't think that's true. on an x86_64 system, the 64bit libs are in
> /lib64/. some distros tried to (pointlessly imo) resist and force 64bits into
> /lib/ when the native ABI was x86_64 (Gentoo included), but those are legacy
> imo, and afaik, they didn't break the ldso paths.
> so in a setup that only has hardfloat binaries, you'd have all the libs in
> /libhf/, not just the ldso.
That's exactly my concern. If /libhf is chosen for the dymamic linker path, but it's not adopted by everyone else for libraries and other files, then at best you'd have a symlink, at worst a dir with only one file inside.
> the implication in supporting both hardfloat and softfloat simultaneously is
> that you'd could have them both installed. thus putting them both in /lib/
> doesn't make much sense if you're still going to need /libhf/ to hold
> everything else.
That case has only any chance of realization in a multiarch environment such as Debian/Ubuntu. The rest won't be affected at all. And the dynamic linkers -different filename of course- are the only libs that will be in /lib straight, the rest will be in /lib/<triplet>. So there is no danger of any conflict, at least not with libraries.
Konstantinos Margaritis <firstname.lastname@example.org>