[Top][All Lists]

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

Re: MinGW/Cygwin wrapper bug

From: Ralf Wildenhues
Subject: Re: MinGW/Cygwin wrapper bug
Date: Tue, 4 Dec 2007 22:18:33 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

* Bob Friesenhahn wrote on Tue, Dec 04, 2007 at 10:09:25PM CET:
> I am not sure how to wrap it up in a test.  The problem is not an 
> obscure error since it is always present.  I am surprised that I am 
> the only one who has reported the problem.

OK so here's a try of mine.  Can you confirm that this exposes the bug,
i.e., the last line prints 1 instead of 0?

Or is it rather that you have a problem at link time?  Then the last
mode=link should fail iff, on the line marked XXX, `int a' is replaced
with `int b'.

Which of the two suspected setups is the failing one?


: ${LIBTOOL=libtool}
: ${CC=gcc}
mkdir -p $instdir $libdir $bindir
echo 'int a () { return 1; }' > a.c             # XXX
$LIBTOOL --mode=compile $CC -c a.c
$LIBTOOL --mode=link $CC -o -rpath $libdir a.lo
$LIBTOOL --mode=install cp $libdir/

echo 'int a () { return 0; }' > a.c
$LIBTOOL --mode=compile $CC -c a.c
$LIBTOOL --mode=link $CC -o -rpath $libdir a.lo

echo 'extern int a (); int main () { return a (); }' > m.c
$CC -c m.c

$LIBTOOL --mode=link $CC -o m m.o
./m; echo $?

reply via email to

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