On Tue, 3 Feb 2009, Paul Elliott wrote:
All of the .rpm based distros that I use recommend putting
./configure --libdir=%_libdir .
in the .spec file. %_libdir is is /usr/lib or /usr/lib64
It seems that this is not quite enough logic. For example, I noticed
in a log that a user sent to m
On Tue, Feb 3, 2009 at 10:19 AM, Paul Elliott wrote:
...
> The Debian based distros that I have used don't need anything done
> because /usr/lib works for 64bit.
Well, I probably messed up my Centos 5.2 64-bit system by using old
habits and adding packages without paying attention to whether they
On Tue, Feb 3, 2009 at 7:50 AM, Peter Breitenlohner ...
wrote:
> On Tue, 3 Feb 2009, Eric Blake wrote:
...
>> According to Tom Browder on 2/3/2009 6:23 AM:
...
>>> put in my site file (taken from the autoconf manual, para.14.8):
>>>
>>> test "$libdir" = NONE && libdir=${prefix}/lib64
>>>
>>> Corr
On Mon, 2 Feb 2009, Tom Browder wrote:
Is there any way to have configure test for a 64-bit system and then
put libraries in a default place, say /usr/local/lib64, instead of the
default /usr/local/lib as so many GNU packages do at the moment?
I know I can use ./configure --libdir=/usr/local/li
On Tue, Feb 03, 2009 at 05:50:21AM -0700, Eric Blake wrote:
> According to Tom Browder on 2/2/2009 1:53 PM:
> > Is there any way to have configure test for a 64-bit system and then
> > put libraries in a default place, say /usr/local/lib64, instead of the
> > default /usr/local/lib as so many GNU p
Peter Breitenlohner mppmu.mpg.de> writes:
> > test "$libdir" = NONE && libdir='${prefix}/lib64'
>
> Hi Eric, Tom,
>
> both of you are wrong (at least for Autoconf 2.63). It ought to be
>
> test "$libdir" = '${exec_prefix}/lib' && libdir='${exec_prefix}/lib64'
Yes, thanks for the corrections.
On Tue, 3 Feb 2009, Eric Blake wrote:
According to Tom Browder on 2/3/2009 6:23 AM:
Aha! So I, as a user, can do that even if they don't. So I should
put in my site file (taken from the autoconf manual, para.14.8):
test "$libdir" = NONE && libdir=${prefix}/lib64
Correct?
Almost. I'd r
On Tue, Feb 3, 2009 at 7:28 AM, Eric Blake wrote:
...
> According to Tom Browder on 2/3/2009 6:23 AM:
...
>> Aha! So I, as a user, can do that even if they don't. So I should
>> put in my site file (taken from the autoconf manual, para.14.8):
>>
>> test "$libdir" = NONE && libdir=${prefix}/lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom Browder on 2/3/2009 6:23 AM:
>> The BEST way to do this is for distros that want /usr/local/lib64 to be
>> the default to install a /usr/local/config.site that makes this happen
>> automatically. Since it is the distro that is choosin
On Tue, Feb 3, 2009 at 6:50 AM, Eric Blake wrote:
...
> According to Tom Browder on 2/2/2009 1:53 PM:
>> Is there any way to have configure test for a 64-bit system and then
>> put libraries in a default place, say /usr/local/lib64, instead of the
>> default /usr/local/lib as so many GNU packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom Browder on 2/2/2009 1:53 PM:
> Is there any way to have configure test for a 64-bit system and then
> put libraries in a default place, say /usr/local/lib64, instead of the
> default /usr/local/lib as so many GNU packages do at the mom
Tom Browder writes:
> Is there any way to have configure test for a 64-bit system and then
> put libraries in a default place, say /usr/local/lib64, instead of the
> default /usr/local/lib as so many GNU packages do at the moment?
>
> I know I can use ./configure --libdir=/usr/local/lib64 but wou
Is there any way to have configure test for a 64-bit system and then
put libraries in a default place, say /usr/local/lib64, instead of the
default /usr/local/lib as so many GNU packages do at the moment?
I know I can use ./configure --libdir=/usr/local/lib64 but would like
the package to take car
13 matches
Mail list logo
