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: Mumit Khan <khan at xraylith dot wisc dot edu>
- Subject: Re: Mingw32-ecgs DLL cann't load, cross-compile can, same tools
- From: Douglas Steele <dsteele dot demon dot co dot uk at dsteele dot demon dot co dot uk>
- Date: Thu, 15 Oct 1998 22:36:15 +0100
- Cc: gnu-win32 at cygnus dot com
- References: <K3ZydZAUpPJ2Ew6N@dsteele.demon.co.uk><9810142006.AA11337@modi.xraylith.wisc.edu>
- Reply-To: Douglas Steele <Douglas at dsteele dot demon dot co dot uk>
Hi Mumit,
>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).
My "favourite" file (From Win95 Version A times).
>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.
Be interested to try it.
>Any other routines with such behaviour that may be causing this?
Not come across any. A couple of other observations though. I have two
versions of the exe and dll; cross-compile and direct. As above, no
problems with cross-compile, direct doesn't load. If I swap the dll's,
the error follows the direct compiled dll (direct compiled exe and
cross-compiled dll works fine). So problem after object file creation
in direct compiled dll only. (Exe files not identical though).
>From investigations with R system, problem originally reported with
Win95A. I have version B now, fault still present, so probably not
related to Win95 version.
--
Douglas
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".