This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Mingw32-ecgs DLL cann't load, cross-compile can, same tools
- To: Douglas Steele <Douglas at dsteele dot demon dot co dot uk>
- Subject: Re: Mingw32-ecgs DLL cann't load, cross-compile can, same tools
- From: Mumit Khan <khan at xraylith dot wisc dot edu>
- Date: Wed, 14 Oct 1998 15:06:49 -0500
- Cc: gnu-win32 at cygnus dot com
Douglas Steele <dsteele.demon.co.uk@dsteele.demon.co.uk> writes:
>
> I have a small standard test dll program (from ftp://sirio.stat.unipd.it
> /pub/dltest ). The cross-compiled version works perfectly. The
> directly compiled version (using identical tools) is unable to load.
>
> The dll failure to load on the small test program illustrates a dll
> failure to load problem with the R statistical system reported by a
> number of other users on Win95.
>
> The dll version which fails to load has large blocks of junk string data
> which are set to \0 in the cross-compiled version. (This is the most
> noticeable difference on an od -c then diff). Note though that the
> object files are identical, so that the discrepancies are occurring
> after object file creation.
[ ... ]
These are quite possibly due to bugs ("features" in MS parlance ;-) in
W95 CRTDLL runtime routines; fseek on W95 for example doesn't zero out
the storage when you seek past the end of file, while it does do the
right/expected thing on WinNT (and of course when built cross on a unix
box).
As soon as I get a chance, I want to build version of binutils using a
replacement fseek and see if that's what's happening.
Any other routines with such behaviour that may be causing this?
Regards,
Mumit
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".