Re: cross-compiling question: static libraries and binaries to different places?

2002-03-08 Thread Guido Draheim
Es schrieb Dan Kegel: > > Guido Draheim wrote: > > ... See - the libtool crossgcc support (to which I did > > contribute some of the time) can simply ask the cross-gcc > > for the local searchpath via `gcc -print-search-dirs` - > > this is needed for win32 compiles atleast, and I have a > > patch

Re: cross-compiling question: static libraries and binaries to different places?

2002-03-08 Thread Guido Draheim
Es schrieb Guido Draheim: > crosscompiling linux-to-linux). Now the result is simply > grepped for the "libraries:" entry, at it usually spits > out a couple of directories very close the installation > of the crossgcc himself. > > [guidod@pc3 guidod]$ i386-mingw32-gcc -print-search-dirs | grep

Re: configure.in vs. configure.ac clash

2002-03-08 Thread Akim Demaille
| > gd> configure sometarget --prefix... 'CFLAGS=$expanded_RPM_CFLAGS' | > | | Manual section `Configuring Other Packages in Subdirectories' does say | nothing for such a requirement. Is it a feature? It is a feature (the feature itself, not the mis-documentation). CFLAGS are peers have been

Autoconf 2.53 is released

2002-03-08 Thread Akim Demaille
The Autoconf team is extremely pleased to announce Autoconf 2.53. We hope it will address your problems, and make your life easier. Enjoy! Akim, Alexandre, Jim, Paul, Tom. ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.53.tar.gz (973 kB) ftp://ftp.gnu.org/gnu/autoconf/autoconf-2.53.t

Re: cross-compiling question: static libraries and binaries to different places?

2002-03-08 Thread Dan Kegel
Guido Draheim wrote: > ... we do not > need any automake support when a staging area (a > chroot-like target host simulation-filetree) is > being used, it would just be a different DESTDIR, > and it would also provide the support for any > other build support file, like includeheaders or > some ot

Protection against stupid developers

2002-03-08 Thread Dan Kegel
I have three times now blown away scripts I've written and started autoconfisticating by forgetting to rename them .in before running configure. If I wrote a patch for autoconf that refuses to delete output files if the corresponding input file didn't exist, think the maintainer would accept it

Re: Protection against stupid developers

2002-03-08 Thread Dan Kegel
Dan Kegel wrote: > > I have three times now blown away scripts I've > written and started autoconfisticating by > forgetting to rename them .in before running configure. And twice now by accidentally putting in the .in suffix inside the AC_OUTPUT line. Autoconf ought to be able to catch that an

Re: Autoconf 2.53 is released

2002-03-08 Thread Bruce Korb
Akim Demaille wrote: > > The Autoconf team is extremely pleased to announce Autoconf 2.53. We > hope it will address your problems, and make your life easier. > - Double quoting macros > AC_TRY_CPP, AC_TRY_COMPILE, AC_TRY_LINK and AC_TRY_RUN. FYI: this will teach me for upgrading without th

Re: Autoconf 2.53 is released

2002-03-08 Thread akim
On Fri, Mar 08, 2002 at 05:57:52PM -0800, Bruce Korb wrote: > Akim Demaille wrote: > > > > The Autoconf team is extremely pleased to announce Autoconf 2.53. We > > hope it will address your problems, and make your life easier. > > > - Double quoting macros > > AC_TRY_CPP, AC_TRY_COMPILE, AC_T