[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How does one specify linking to 64 bit libraries when there is a cho
Re: How does one specify linking to 64 bit libraries when there is a choice?
Mon, 20 Dec 2010 08:41:30 -0700
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:126.96.36.199) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Mnenhy/0.8.3 Thunderbird/3.1.7
On 12/20/2010 08:36 AM, Ralf Corsepius wrote:
>> If a distro insists on shipping 64-bit libraries under /usr/lib64, then
>> it would be in the distro's best interest to also ship a config.site
>> variable that defaults --libdir to the appropriate /usr/lib64 location.
> This isn't of much help on multi-arched architectures (such as
> Fedora/RHEL x86_64 systems), because any such default would only match
> to one of its supported architectures and be wrong on all others.
I disagree with your argument. config.site can be a full-powered shell
script, that examines $CC, $CFLAGS, and so forth to see if any request
for 32- or 64-bit compilation has been requested, and only set --libdir
to /usr/lib64 in the cases where it is compatible with the user's
selections. There's nothing that forces a well-written config.site to
cause a user to use a library location inconsistent with any other
options they passed.
Suggestions in improving the example config.site file here:
in order to be more robust to common multi-arch uses are more than welcome.
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
Description: OpenPGP digital signature