> CPPFLAGS=-I/usr/local/include ./configure
Bzzt. Please pass variable settings as arguments to configure:
./configure CPPFLAGS=-I/usr/local/include
not as environment variables. It has the advantage that
./config.status --recheck
(which may be triggered from a makefile
Hello Alfred,
* Alfred M. Szmidt wrote on Sat, Mar 06, 2010 at 10:09:57AM CET:
> CPPFLAGS=-I/usr/local/include ./configure
Bzzt. Please pass variable settings as arguments to configure:
./configure CPPFLAGS=-I/usr/local/include
not as environment variables. It has the advantage that
./co
On Sat, Mar 6, 2010 at 01:14 UTC, Harlan Stenn wrote:
> You could look at the configure.ac in ntp-dev (or any recent
> ntp-stable), say:
>
> http://ntp.bkbits.net:8080/ntp-dev/configure.ac?REV=4b6a0c4clgted0re5ogPZQx0QgLLPw
>
> and find the hunk of code starting with:
>
> AC_MSG_CHECKING([for ope
If the file is; /usr/local/include/package/header.h
and source is; #include
what goes in configure.ac?
You shouldn't put anything into configure.ac; if you wish to tell your
compiler where to find non-standard headers (i.e. anything the
compiler doesn't search by default) you should do
You could look at the configure.ac in ntp-dev (or any recent
ntp-stable), say:
http://ntp.bkbits.net:8080/ntp-dev/configure.ac?REV=4b6a0c4clgted0re5ogPZQx0QgLLPw
and find the hunk of code starting with:
AC_MSG_CHECKING([for openssl include directory])
and decide for yourself if there is a be
On Fri, Mar 5, 2010 at 21:13 UTC, Charles Brown wrote:
> If the file is; /usr/local/include/package/header.h
> and source is; #include
> what goes in configure.ac?
>
> AC_CHECK_HEADER([package/header.h]) just says 'no'.
AC_CHECK_HEADER and AC_CHECK_HEADERS aren't designed for this
situation -- t
On Fri, Mar 5, 2010 at 4:13 PM, Charles Brown wrote:
> Dave Hart wrote:
>>
>> On Fri, Mar 5, 2010 at 19:25 UTC, Charles Brown wrote:
>> >
>> > Very new to automake, and can't find an answer to this; What would be
>> put in
>> > configure.ac to determine whether the detected preprocessor/compile
Dave Hart wrote:
On Fri, Mar 5, 2010 at 19:25 UTC, Charles Brown wrote:
>
> Very new to automake, and can't find an answer to this; What would be
put in
> configure.ac to determine whether the detected preprocessor/compiler
> automatically supplies -I/usr/local/include (for example, g++ doe
* Charles Brown wrote on Fri, Mar 05, 2010 at 09:37:00PM CET:
> Ralf Wildenhues wrote:
> >
> >Well if you need the flag at configure time, add it to CPPFLAGS, either
> >by the user as above, or by you in configure.ac. But I would reserve
> >this to the user; she might have a broken version of the
Ralf Wildenhues wrote:
Hello Charles,
* Charles Brown wrote on Fri, Mar 05, 2010 at 08:25:53PM CET:
> Very new to automake,
Well, welcome then!
thank you.
Well if you need the flag at configure time, add it to CPPFLAGS, either
by the user as above, or by you in configure.ac. But I would
On Fri, Mar 5, 2010 at 19:25 UTC, Charles Brown wrote:
>
> Very new to automake, and can't find an answer to this; What would be put in
> configure.ac to determine whether the detected preprocessor/compiler
> automatically supplies -I/usr/local/include (for example, g++ does, but sun
> CC does not)
Hello Charles,
* Charles Brown wrote on Fri, Mar 05, 2010 at 08:25:53PM CET:
> Very new to automake,
Well, welcome then!
> and can't find an answer to this; What would
> be put in configure.ac to determine whether the detected
> preprocessor/compiler automatically supplies -I/usr/local/include
>
Very new to automake, and can't find an answer to this; What would be
put in configure.ac to determine whether the detected
preprocessor/compiler automatically supplies -I/usr/local/include (for
example, g++ does, but sun CC does not), and if not, how to add it to
some CFLAGS variable?
I tr
13 matches
Mail list logo
