Re: support for non-standard C compilers (without fopen, FILE*, ...)

Hi, thanks for your quick reply. On Thu, Sep 17, 2009 at 7:53 PM, wrote: > * Ralf Wildenhues wrote on Thu, Sep 17, 2009 at 07:50:10PM CEST: > > * Steffen Dettmer wrote on Thu, Sep 17, 2009 at 05:12:31PM CEST: > > > recent versions check if $CC supports fopen, FILE* and so on. This > > > breaks e

Re: how to support compilers that cannot create executables?

On Thu, Sep 17, 2009 at 8:20 PM, Ralf Wildenhues wrote: > Hello Steffen, > > * Steffen Dettmer wrote on Thu, Sep 17, 2009 at 05:19:46PM CEST: >> However, configure usually checks if the compiler can create >> executables. Can (should) this be prevented? Ohh I missed that this would mean no AC_CHE

Re: how to support compilers that cannot create executables?

* Steffen Dettmer wrote on Fri, Sep 18, 2009 at 12:19:19PM CEST: > On Thu, Sep 17, 2009 at 8:20 PM, Ralf Wildenhues wrote: > > * Steffen Dettmer wrote on Thu, Sep 17, 2009 at 05:19:46PM CEST: > >> However, configure usually checks if the compiler can create > >> executables. Can (should) this be pr

Re: support for non-standard C compilers (without fopen, FILE*, ...)

* Steffen Dettmer wrote on Fri, Sep 18, 2009 at 11:49:20AM CEST: > On Thu, Sep 17, 2009 at 7:53 PM, wrote: > > * Ralf Wildenhues wrote on Thu, Sep 17, 2009 at 07:50:10PM CEST: > > > * Steffen Dettmer wrote on Thu, Sep 17, 2009 at 05:12:31PM CEST: > > > > recent versions check if $CC supports fopen,

Re: how to retrieve expanded variables from configure?

Hello, * none none wrote on Fri, Sep 18, 2009 at 08:02:14AM CEST: > im not very familiar with autoconf currently so im not sure my following > assumptions are correct > so, afaik, autoconf and its resulting configure script set many variables > e.g. exec_prefix or bindir, ... > > what i try to ac

AC_DEFUN: default values of optional arguments

How do I give an optional argument its default value? e.g., AC_DEFUN([FOO],[...]) FOO() should be equivalent to FOO([true]) do I write something like AC_DEFUN([FOO],[ opt=$2; test -z "$opt" && opt=true ]) ?? thanks. Sam. ___ Autoconf mailing list Aut

Re: AC_DEFUN: default values of optional arguments

* Sam Steingold wrote on Fri, Sep 18, 2009 at 07:49:04PM CEST: > How do I give an optional argument its default value? > e.g., > AC_DEFUN([FOO],[...]) > FOO() should be equivalent to FOO([true]) Use m4_default([$2], [true]). Cheers, Ralf ___ Autoconf

Re: AC_DEFUN: default values of optional arguments

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Sam Steingold on 9/18/2009 11:49 AM: > How do I give an optional argument its default value? m4_default([$2],[default text]) expands to $2 if it was provided, or default text otherwise. AC_DEFUN([FOO], [... opt=m4_default([$2],[true]) ]

Re: multilib and Makefile regeneration

* Paolo Bonzini wrote on Mon, Aug 31, 2009 at 11:53:17PM CEST: > On 08/31/2009 11:11 PM, Ralf Wildenhues wrote: > >The easiest for now would be (3), the coolest, most difficult and > >probably most dangerous one would be (2). Something like >