[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Libtool HEAD testsuite

From: Duft Markus
Subject: RE: Libtool HEAD testsuite
Date: Tue, 30 Jan 2007 09:02:24 +0100

Ralf Wildenhues <mailto:address@hidden> wrote:
> Hello Markus,
> * Duft Markus wrote on Fri, Jan 19, 2007 at 05:28:41PM CET:
>> Sorry, i must correct myself. $EXEEXT *is* used *sometimes* and as
>> far as my situation is concerned, completely in the wrong places...
> Well, it matches the Cygwin semantics of .exe interpolation:
> <>.
> The other missing bit of data is that on Cygwin and MinGW, a C wrapper
> foo/tagdemo.exe for foo/.libs/tagdemo.exe is also created in addition
> to the shell wrapper foo/tagdemo.
> You don't describe your situation sufficiently well for somebody
> else to do anything about it.  Do you use Cygwin, MinGW, or Interix?
> Native or cross-compile + simulator?  What semantics does the system
> in question have wrt. suffix interpolation?  Find out about those
> semantics and post the link to its documentation.  How come you don't
> post the actual verbose test failure output, so we could see which
> tests have the problem?

The compiler i use is WGCC (still @ sourceforge ;o)) which i wrote
myself. The sematics for executable extensions are configurable, which
means one can set the default output filename in a configuration file.
The current default set by me is a.exe (like gcc...). It was a.out, but
that cause lots and lots of troubles with windows ;o// i will look
further into porting my patches to Interix/WGCC.

>> I don't claim to have found a solution for this, but at least for
>> now, and for me i got a workaround....
> Which you didn't post either (as a patch).  :-(

The workaround is to remove $EXEEXT from all the test files and
therefore patch to check for both files, one with and one
without exe extension. I know thet this is probably not a really good
solution (i attached the patch...). I didn't look at all tests by now,
so there may be others still having EXEEXT in them. I additionally don't
know if i can use $EXEEXT or @EXEEXT@ on defs.m4sh so i for now just
hardcoded the .exe...

Cheers, Markus

> Cheers,
> Ralf

Attachment: test-suite.patch
Description: test-suite.patch

reply via email to

[Prev in Thread] Current Thread [Next in Thread]