At 1:44 PM +0200 4/3/00, Akim Demaille wrote:
> > "Geoff" == Geoff Hutchison <[EMAIL PROTECTED]> writes:
>
> >> But you can of course also write sh commands in your configure.in
> >> that compiles regex.c instead.
>
>Geoff> I think that's probably sufficient.
>
>If you mean compiling by han
> "Geoff" == Geoff Hutchison <[EMAIL PROTECTED]> writes:
>> But you can of course also write sh commands in your configure.in
>> that compiles regex.c instead.
Geoff> I think that's probably sufficient.
If you mean compiling by hand, don't do that. Use AC_TRY_COMPILE, or
AC_COMPILE_IFELSE
Geoff Hutchison <[EMAIL PROTECTED]> writes:
> I think that's probably sufficient. Is there any place in the
> autoconf manual that talks about how to access the programs you've
> already found? For example, what variable contains the path to the
> compiler? Is it ac_cxx_prog or something like t
At 2:36 AM +0200 4/1/00, Assar Westerlund wrote:
>[ I've redirected this to the autoconf mailing list ]
I didn't know it existed, I only saw comments about the automake one. Sorry!
>The simple and dirty approach is to #include .
Doh! As I said, I was drawing a blank. Of course this will work fi
[ I've redirected this to the autoconf mailing list ]
Geoff Hutchison <[EMAIL PROTECTED]> writes:
> Basically, I want an AC_TRY_RUN test that includes the regex.c file in
> compilation. Is this possible, or can you only compile/link the test
> program file?
The simple and dirty approach is to #
