RE: CONFIG_FILES

2004-12-28 Thread wolfgang haefelinger
Hi Stepan, thanks for the clarification. I was not aware of option --file. I have been reading the documentation - but ob- viously not hard enough :-) Best wishes, Wolfgang. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Stepan Kasal Sent: Monday, Dec

questions about using autoconf and naming convetions

2004-12-28 Thread james osburn
what is the following doing? /configure --target=i386-linux --host=i386-linux --build=i686-pc-linux-gnu thanks black_13 ___ Autoconf mailing list Autoconf@gnu.org http://lists.gnu.org/mailman/listinfo/autoconf

Re: AC_PROG_CC_C99

2004-12-28 Thread Dan Manthey
Hi. I'm new to this list, so I may be fuddled. Please flame me only for my own benefit. I'm using autoconf 2.59, so I copied the relevant parts of the new AC_PROG_CC_C99 macro to my aclocal.m4 to use it. I used the version Roger Leigh posted as a diff on December 2nd. I noticed two issues: I

Re: question regarding AC_CHECK_LIB

2004-12-28 Thread Noah Misch
> krishna wrote: > >1.How do i specify the additional paths which AC_CHECK_LIB should check? This is the typical idiom: save_LDFLAGS="$LDFLAGS" LDFLAGS="-L/dir $LDFLAGS" AC_CHECK_LIB(...) LDFLAGS="$save_LDFLAGS" You could wrap it in a macro: # AC_VAR_EXCURSION(VAR, VALUE, EXPRESSION) # ---

Re: questions about using autoconf and naming convetions

2004-12-28 Thread Stepan Kasal
Hi, On Tue, Dec 28, 2004 at 05:56:27PM +, james osburn wrote: > /configure --target=i386-linux --host=i386-linux --build=i686-pc-linux-gnu see: http://www.lns.cornell.edu/public/COMP/info/autoconf/Specifying-Names.html and http://www.lns.cornell.edu/public/COMP/info/autoconf/System-Type.html