[Expat-bugs] [ expat-Bugs-1171906 ] expat-2005-01-28 snapshot in Mingw's msys 1.0

[SourceForge.net]

Bugs item #1171906, was opened at 03/28/05 07:41
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://test.sf.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Build control
Group: Platform Specific
>Status: Closed
Resolution: None
Priority: 5
Submitted By: heromyth (heromyth)
Assigned to: Gerrit P. Haase (siebenschlaefer)
Summary: expat-2005-01-28 snapshot in Mingw's msys 1.0

Initial Comment:
When I do Make, it is almost successful. At that time, I 
get the shared and statice libraries. 

During making, it show this:

 /bin/sh ./libtool --silent --mode=link gcc -I./lib -I. -O2 -
Wall -Wmissing-pr
ototypes -Wstrict-prototypes -fexceptions -
DHAVE_EXPAT_CONFIG_H -o examples/ele
ments examples/elements.o libexpat.la
./libtool: .libs/lt-examples/elements.c: No such file or 
directory
./libtool: .libs/lt-examples/elements.c: No such file or 
directory
./libtool: .libs/lt-examples/elements.c: No such file or 
directory
./libtool: .libs/lt-examples/elements.c: No such file or 
directory
./libtool: .libs/lt-examples/elements.c: No such file or 
directory
./libtool: .libs/lt-examples/elements.c: No such file or 
directory
gcc.exe: .libs/lt-examples/elements.c: No such file or 
directory
gcc.exe: no input files

SO I think there are some error in the file libtool. When I 
use another libtool of msys, it's OK.


----------------------------------------------------------------------

>Comment By: Nobody/Anonymous (nobody)
Date: 07/12/05 22:22

Message:
Logged In: NO 

This artifact has been closed automatically because no submitter feedback was received within administrator-specified timeout period.

----------------------------------------------------------------------

Comment By: Gerrit P. Haase (siebenschlaefer)
Date: 03/30/05 01:46

Message:
Logged In: YES 
user_id=76037

Older libtool releases have many bugs, for the latest expat
release an older buggy libtool was used, if you get better
results with newer libtool releases, then upgrade libtool
for your build.  Future releases probably will use a newer
libtool, so probably this bug will be resolved automatically
when libtool at the build machine is upgraded.

Ther other question: the libraries naming scheme is:
Static archive: libexpat.a
Import library: libexpat.dll.a
Shared library: (cyg)expat-0.dll

If you want to link against the static archive please use
the -static ld switch with your link command, ld takes care
about it and uses the static archive to build executables
independant of the shared library.

Hth,
Gerrit

----------------------------------------------------------------------

Comment By: Karl Waclawek (kwaclaw)
Date: 03/29/05 18:41

Message:
Logged In: YES 
user_id=290026

Assigned to our Cygwin expert - maybe he can help.

----------------------------------------------------------------------

Comment By: heromyth (heromyth)
Date: 03/29/05 16:15

Message:
Logged In: YES 
user_id=1190746

There is a another question about the expat's libraries. In 
msys 1.0, I get libexpat.dll.a , libexpat.a and expat-0.dll. I link 
my applications like this:
-Ld:/some/dir/ -lexpat
It always use  libexpat.dll.a but not libexpat.a. So I have test 
it. When I rename libexpat.dll.a to libexpat-0.dll.a, now the 
linker use libexpat.a. 

----------------------------------------------------------------------

You can respond by visiting: 
https://test.sf.net/tracker/?func=detail&atid=110127&aid=1171906&group_id=10127