Re: split check target into check and test targets

2010-03-02 Thread Steffen Dettmer
On Wed, Feb 24, 2010 at 7:17 PM, John Calcote john.calc...@gmail.com wrote: Alexander's solution is great, though. I'm going to use that one myself. For this, you'd need to change all Makefile.ams and it isn't working recursively... What is with having AC_SUBST(TESTS) in configure.in and

Re: Problem of: variable `main_SOURCES' is defined but no program or library has `main' as canonical name (possible typo)

2010-03-02 Thread Steffen Dettmer
bin_PROGRA*M*S = main ahh great, so it caught the typo :-) oki, Steffen

Multiplatform autotools; all OK on Linux, warning on Windows

2010-03-02 Thread Joost Kraaijeveld
Hi, I am not really sure that this a question for this list but maybe there is a kind sole that has the answer over here I have a Autools based project that I *really* want to compile both on Linux and Windows using gcc (mingw on Windows) using Autotools. I get these warnings: *** Warning:

Re: split check target into check and test targets

2010-03-02 Thread Ralf Wildenhues
Hello, * Steffen Dettmer wrote on Tue, Mar 02, 2010 at 11:00:39AM CET: On Wed, Feb 24, 2010 at 7:17 PM, John Calcote wrote: Alexander's solution is great, though. I'm going to use that one myself. For this, you'd need to change all Makefile.ams and it isn't working recursively... Yes.

Re: Public header files

2010-03-02 Thread Jef Driesen
On 01/03/10 19:35, Ralf Wildenhues wrote: Hello Jef, * Jef Driesen wrote on Mon, Mar 01, 2010 at 01:33:46PM CET: How do I get information generated by autotools into my public header files? For instance I want to define version numbers somewhere in my configure.ac file, and have the same

Re: Public header files

2010-03-02 Thread Ralf Wildenhues
* Jef Driesen wrote on Tue, Mar 02, 2010 at 10:03:35PM CET: On 01/03/10 19:35, Ralf Wildenhues wrote: * Jef Driesen wrote on Mon, Mar 01, 2010 at 01:33:46PM CET: Since a config.h header files is not supposed to be public, that's not an option. But how can I do this correctly? Use a second

Re: cross-compiling on 64 to 32-bit Linuxlocalhost/

2010-03-02 Thread Grégory Pakosz
You need a bi-arch system, that is, one that has the system libraries both in a 64-bit variant and in a 32-bit variant (typically in /lib64 and /lib, respectively). For compiling in 32-bit mode, I use ./configure --host=i686-pc-linux-gnu \ --prefix=/arch/x86-linux/gnu \

Re: distcheck and canonical_*

2010-03-02 Thread Steffen Dettmer
On Fri, Feb 26, 2010 at 2:55 PM, NightStrike nightstr...@gmail.com wrote: When doing a make distcheck, why is for instance the --host option not propagated to configure without explicitly setting DISTCHECK_CONFIGURE_FLAGS? erm... isn't --host enabling cross-compiling? And when cross-compiling,

Re: cross-compiling on 64 to 32-bit Linuxlocalhost/

2010-03-02 Thread John Calcote
Hi Gregory, On 3/2/2010 4:14 PM, Grégory Pakosz wrote: ./configure --host=i686-pc-linux-gnu \ --prefix=/arch/x86-linux/gnu \ CC=gcc -m32 -march=i586 \ CXX=g++ -m32 -march=i586 \ LDFLAGS=-m32 I'm curious about why setting

Re: distcheck and canonical_*

2010-03-02 Thread Ralf Wildenhues
* Steffen Dettmer wrote on Wed, Mar 03, 2010 at 12:21:32AM CET: On Fri, Feb 26, 2010 at 2:55 PM, NightStrike wrote: When doing a make distcheck, why is for instance the --host option not propagated to configure without explicitly setting DISTCHECK_CONFIGURE_FLAGS? erm... isn't --host