Ralf Wildenhues [EMAIL PROTECTED] writes:
Hi Simon,
* Simon Josefsson wrote on Mon, Jan 30, 2006 at 10:40:56AM CET:
I wonder what the best idiom for gnulib should be. We probably do not
want to require automake CVS just yet. Should it be the one I'm using:
TESTS += test-gc$(EXEEXT)
Alexandre Duret-Lutz [EMAIL PROTECTED] writes:
SJ How about simply:
SJ tests_PROGRAMS += test-gc
[...]
SJ Or something, I'm not really sure. I have always found this
SJ redundancy a bit disturbing though.
I don't think a new syntax is necessary since you can do
TESTS =
Hi Simon,
* Simon Josefsson wrote on Mon, Jan 30, 2006 at 10:40:56AM CET:
I wonder what the best idiom for gnulib should be. We probably do not
want to require automake CVS just yet. Should it be the one I'm using:
TESTS += test-gc$(EXEEXT)
check_PROGRAMS += test-gc
or should we do
SJ == Simon Josefsson [EMAIL PROTECTED] writes:
SJ Ralf Wildenhues [EMAIL PROTECTED] writes:
Now I wonder how to best fix this in Automake:
- document the fact that $(EXEEXT) should be used in `TESTS', for the
benefit of cross-compilation,
- have Automake rewrite TESTS to add $(EXEEXT)
On Mon, 2006-01-23 at 21:51 +0100, Bruno Haible wrote:
[For the automake people: The problem is that a Makefile.am snippet like
TESTS = test-lock
check_PROGRAMS = test-lock
test_LOCK_LDFLAGS = -lmyspeciallib
when cross-compiling to mingw on a Unix system with 'wine', will
Hi Bruno,
* Bruno Haible wrote on Mon, Jan 23, 2006 at 09:51:57PM CET:
...
noinst_PROGRAMS =
check_PROGRAMS = test-lock$(EXEEXT)
TESTS = test-lock
check-am: all-am
$(MAKE) $(AM_MAKEFLAGS) $(check_PROGRAMS)
$(MAKE) $(AM_MAKEFLAGS) check-TESTS
check-TESTS: $(TESTS)
Ralf Corsepius [EMAIL PROTECTED] writes:
On Mon, 2006-01-23 at 21:51 +0100, Bruno Haible wrote:
[For the automake people: The problem is that a Makefile.am snippet like
TESTS = test-lock
check_PROGRAMS = test-lock
test_LOCK_LDFLAGS = -lmyspeciallib
when cross-compiling to
Ralf Wildenhues wrote:
check_PROGRAMS = test-lock$(EXEEXT)
TESTS = test-lock
...
What about @substituted@ values?
TESTS = @substituted@
You could treat it like @substituted@ in check_PROGRAMS, namely
- assume that $(EXEEXT) is contained in the substituted value,
- warn if
Ralf Corsepius wrote:
Due to lack of a mingw toolchain, I can't tell you exactly what goes
wrong for you.
3 likely candidates:
* The cross gcc doesn't produce *.exe's (This would be a gcc bug).
* You are not correctly invoking configure.
* Makefile bug somewhere.
Is there need to
On Tue, 2006-01-24 at 13:15 +0100, Simon Josefsson wrote:
Ralf Corsepius [EMAIL PROTECTED] writes:
On Mon, 2006-01-23 at 21:51 +0100, Bruno Haible wrote:
[For the automake people: The problem is that a Makefile.am snippet like
TESTS = test-lock
check_PROGRAMS = test-lock
[For the automake people: The problem is that a Makefile.am snippet like
TESTS = test-lock
check_PROGRAMS = test-lock
test_LOCK_LDFLAGS = -lmyspeciallib
when cross-compiling to mingw on a Unix system with 'wine', will cause
make check to build 'test-lock', rather than
Ralf Wildenhues [EMAIL PROTECTED] writes:
Hi Simon,
* Simon Josefsson wrote on Wed, Jan 18, 2006 at 02:01:27PM CET:
While testing mingw32 portability (GNU SASL now builds cleanly
cross-compiled to mingw32!) I encountered the following. It seems
$(EXEXT) is required for automake TESTS
Ralf Wildenhues [EMAIL PROTECTED] writes:
Hi Simon,
* Simon Josefsson wrote on Thu, Jan 19, 2006 at 09:42:17AM CET:
It doesn't seem to matter if I change noinst_PROGRAMS into
check_PROGRAMS, I still have to add $(EXEEXT) to the binaries in TESTS
for things to work.
TESTS += test-gc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 1/18/2006 12:57 PM:
Thanks for catching that! I suspect that many packages have the same
problem, because it appears only with the mingw platform. (No problem
with cygwin.)
Cygwin had no problem in this particular
[ Cc:ing bug-automake; this is
http://thread.gmane.org/gmane.comp.lib.gnulib.bugs/5240 ]
Hi Simon,
* Simon Josefsson wrote on Thu, Jan 19, 2006 at 10:50:43AM CET:
Ralf Wildenhues [EMAIL PROTECTED] writes:
* Simon Josefsson wrote on Thu, Jan 19, 2006 at 09:42:17AM CET:
It doesn't seem to
While testing mingw32 portability (GNU SASL now builds cleanly
cross-compiled to mingw32!) I encountered the following. It seems
$(EXEXT) is required for automake TESTS variables, otherwise
'make' misses out all CPPFLAGS etc: make check-TESTS make[2]:
Entering directory
Hi Simon,
* Simon Josefsson wrote on Wed, Jan 18, 2006 at 02:01:27PM CET:
While testing mingw32 portability (GNU SASL now builds cleanly
cross-compiled to mingw32!) I encountered the following. It seems
$(EXEXT) is required for automake TESTS variables, otherwise
'make' misses out all
17 matches
Mail list logo