[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Adding $includedir and $libdir in CPPFLAGS and LDFLAGS
From: |
Alexandre Duret-Lutz |
Subject: |
Re: Adding $includedir and $libdir in CPPFLAGS and LDFLAGS |
Date: |
28 Dec 2001 10:25:46 +0100 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 |
>>> "John" == John D Burger <address@hidden> writes:
[...]
John> I've tried:
John> AC_INIT(libspec, 1.0, address@hidden)
John> CPPFLAGS="-I$includedir $CPPFLAGS"
John> LDFLAGS="-L$libdir $LDFLAGS"
John> ...
Aside: you may want to protect your code against the following
issue described in the GCC manual:
| * Use of `-I/usr/include' may cause trouble.
|
| Many systems come with header files that won't work with GCC unless
| corrected by `fixincludes'. The corrected header files go in a new
| directory; GCC searches this directory before `/usr/include'. If
| you use `-I/usr/include', this tells GCC to search `/usr/include'
| earlier on, before the corrected headers. The result is that you
| get the uncorrected header files.
John> but this doesn't quite work - ac_cpp and friends end up with an
John> unexpanded ${prefix} or ${exec_prefix}, I believe.
Appart from the `NONE' stuff, is that a problem?
IIRC autoconf will `eval' any call to ac_cpp and friends.
[...]
You might also like
http://www.gnu.org/software/ac-archive/Installed_Packages/smr_with_build_path.html
--
Alexandre Duret-Lutz