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

2009-09-17 Thread Steffen Dettmer
Hi, recent versions check if $CC supports fopen, FILE* and so on. This breaks environments that don't have / libc.a. Wouldn't the autoconf way to be to /* undef HAVE_STDIO_H */ but leave the source code to handle this instead of aborting? Is it possible to writing something in configure.in to k

how to support compilers that cannot create executables?

2009-09-17 Thread Steffen Dettmer
Hi, when compiling libraries, it technically is not required to have a compiler to create executables. We might have a lib with unit tests where the unit tests work on linux and windows only, but not on a small embedded platform. On this platform it might be complicated, special and non-standard t

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

2009-09-17 Thread Ralf Wildenhues
Hello Steffen, * 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 environments that don't have / libc.a. This is a 2.64 regression and has been fixed since in the git tree:

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

2009-09-17 Thread Ralf Wildenhues
* 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 environments that don't have / libc.a. > > This is a 2.64 regression and has been f

Re: how to support compilers that cannot create executables?

2009-09-17 Thread Ralf Wildenhues
Hello Steffen, * Steffen Dettmer wrote on Thu, Sep 17, 2009 at 05:19:46PM CEST: > when compiling libraries, it technically is not required to have a > compiler to create executables. We might have a lib with unit tests > where the unit tests work on linux and windows only, but not on a > small emb

how to retrieve expanded variables from configure?

2009-09-17 Thread none none
hi all 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 achive is extract an expanded representation of all variables configure c