-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
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
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
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
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.
Eric Blake byu.net> writes:
> > I'm not trying to solve anything. I'm trying to suggest CFLAGS's
> > meaning should be documented in a place where maintainers might look
> > during development. I don't see how it hurts to add a sentence or two.
>
> The automake manual already mentions this, bu
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
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
-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 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
Hello everyone,
I have prepared a 'configure.ac' which tests both for Fortran compilers
and MPI library.
If configure is done using '--with-mpi' option then the configure looks
for MPI libs
and if succeed ad the option '-DMPI' for the compilation of some files
(F90) of the code.
So far everyth
Hello Sébastien,
* Sébastien Le Roux wrote on Tue, Feb 03, 2009 at 07:59:11PM CET:
>
> I have prepared a 'configure.ac' which tests both for Fortran
> compilers and MPI library. If configure is done using '--with-mpi'
> option then the configure looks for MPI libs and if succeed ad the
> option
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
The automake manual already mentions this,
I actually looked in the automake manual first. And the reference I got
to first (don't know why) is the one in the `Program variables' node,
which says "Some variables are inherited from Autoconf". So I went to
the Autoconf manual instead of lo
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
I should add that Sébastien's mail server does not accept mail from any
of my accounts, so on-list communication is the only one that will work.
Please stick to it.
Everyone else, sorry for the noise.
Cheers,
Ralf
___
Autoconf mailing list
Autoconf@gn
16 matches
Mail list logo
