From: Mumit Khan <khan@xraylith.wisc.EDU>
To: John Garrison <jeg@visi.net>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Libraries not working
Date: Sat, 31 Jul 1999 18:34:00 -0000 [thread overview]
Message-ID: <199907062127.QAA32661@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990731183400.Vq5bzSZNdZT6rIOokUwDaRegPT-0Qfdr9rrlG6jaVog@z> (raw)
In-Reply-To: <378264FF.D064AE02@visi.net>
John Garrison <jeg@visi.net> writes:
> >
> > $ i586-cygwin32-nm libIMG.a | grep IMG_Load_RW
> >
> > (or, i386-mingw32-nm if you're using Mingw cross-compiler).
> >
> > shows what?
> >
>
> [bin]# ./i586-mingw32-nm /usr/win32/lib/libIMG.a | grep IMG_Load_RW
> ./i586-mingw32-nm: IMG.c: File format not recognized
> ./i586-mingw32-nm: IMG_tif.c: File format not recognized
> ./i586-mingw32-nm: IMG_xxx.c: File format not recognized
> ./i586-mingw32-nm: IMG_bmp.c: File format not recognized
>
> What does it mean file format not recognized? it's C code, compiled for wind
> ows
> with mingw32. I would say maybe there were some Linux object files in the
> directory that wouldn't have gotten recompiled, but that isn't likely, it wou
> ld
> be all the objects or nothing, make clean wipes out all .o files and make
> creates all .o files.
That means that libIMG.a was NOT compiled for windows32 target, but
possibly for your host (``nm libIMG.a'' then would show the symbols
instead).
libIMG.a cannot be a host library, but rather has to be a target
library. Until that is fixed, nothing else will work. Same goes for
*all* the object files and archives on the command line you're using.
Make sure you're using the cross-compiler to build the libIMG.a, and
make sure the cross-compiler is using the cross assembler, and that
you're using cross-tools (ix86-mingw32-ar, ix86-mingw32-ranlib) to
build the archive. This is fundamental to building anything in a
cross-development environment.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-07-31 18:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-06 12:01 John Garrison
1999-07-06 12:53 ` Mumit Khan
1999-07-06 13:21 ` John Garrison
1999-07-06 14:27 ` Mumit Khan [this message]
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` John Garrison
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` John Garrison
-- strict thread matches above, loose matches on Subject: below --
1999-07-06 14:31 DJ Delorie
1999-07-06 14:50 ` Mumit Khan
1999-07-06 15:04 ` John Garrison
1999-07-06 15:23 ` Mumit Khan
1999-07-06 15:47 ` John Garrison
1999-07-06 19:31 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` John Garrison
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` John Garrison
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` DJ Delorie
1999-07-05 13:21 John Garrison
1999-07-06 11:15 ` Mumit Khan
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` John Garrison
1999-07-03 22:42 John Garrison
1999-07-04 9:57 ` tjoen
1999-07-04 17:51 ` Mumit Khan
1999-07-05 11:02 ` tjoen
1999-07-31 18:34 ` tjoen
1999-07-31 18:34 ` Mumit Khan
1999-07-31 18:34 ` tjoen
1999-07-31 18:34 ` John Garrison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199907062127.QAA32661@mercury.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=jeg@visi.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).