-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Braden McDaniel wrote:
|
| I don't fully understand the problem you're describing; but perhaps you
| want to do something like this:
|
| save_LDFLAGS="$LDFLAGS"
| LDFLAGS="$LDFLAGS -Lwhatever"
| AC_CHECK_LIB(...)
| LDFLAGS="$save_LDFLAGS"
|
No, what I w
* Harald Dunkel wrote on Thu, Nov 04, 2004 at 09:48:49PM CET:
>
> My question is: How can I use AC_CHECK_LIB without setting
> a global LDFLAGS?
Why do you have to do that in the first place?
> Using automake I can specify linker flags per program, e.g.
>
> foo_LDFLAGS = -L/somepath/mylibs1
> b
Harald Dunkel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Braden McDaniel wrote:
|
| I don't fully understand the problem you're describing; but perhaps you
| want to do something like this:
|
| save_LDFLAGS="$LDFLAGS"
| LDFLAGS="$LDFLAGS -Lwhatever"
| AC_CHECK_LIB(...)
| LDFLAGS="$save_LD
Patrice Dumas wrote:
In the attached file there is a macro which could be used to test if a
backslash escapes characters, the test being the escape of '.
Hi Patrice, looks like a reasonable macro. However, might I suggest
that you send it to the Autoconf Macro Repository? That's usually the
pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Braden McDaniel wrote:
| Harald Dunkel wrote:
|
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Braden McDaniel wrote:
|> |
|> | I don't fully understand the problem you're describing; but perhaps you
|> | want to do something like this:
|> |
Patrice Dumas wrote:
I was planning on doing something similar for endianess detection, but
using the C code seems superior in most cases as it should work for
cross compilation. Will it be usefull to have a fortran only macro in
that case ?
No, I doubt that there's any reason to have more than o
Harald Dunkel wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Braden McDaniel wrote:
| Harald Dunkel wrote:
|
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Braden McDaniel wrote:
|> |
|> | I don't fully understand the problem you're describing; but perhaps
you
|> | want to do some
Patrice Dumas wrote:
It should not: the architecture is made for these tests to be
implementable independently of the language.
Currently, if I'm not wrong AC_CHECK_SIZEOF checks for C, as it
uses _AC_COMPUTE_INT([(long int) (sizeof ($1))].
This wont work for fortran and even less in a fortran only
If you run autoheader 2.59b on a configure.ac without a
AC_CONFIG_HEADERS, it will properly inform you
error: AC_CONFIG_HEADERS not found in configure.ac
Nevertheless the perl script continues which appends .in to nothing
thereby creating the hidden file ".in" and procedes all outputs all the
d