Re: problem w/ mingw32/egcs/msvcrt and file reads (fwd)

[Mumit Khan <khan@xraylith.wisc.edu>]

On Mon, 10 May 1999, Earnie Boyd wrote:

> gcc -v -o cpsh.exe cpsh.o -specs=msvcrt-specs
> Reading specs from c:\root\usr\lib\gcc-lib\i386-mingw32\egcs-2.91.66\specs
> Reading specs from
> c:\root\usr\lib\gcc-lib\i386-mingw32\egcs-2.91.66\msvcrt-specs
> gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)
>  ld -o cpsh.exe c:\root\usr\lib\crt2.o
> -Lc:\root\usr\lib\gcc-lib\i386-mingw32\egcs-2.91.66 -Lc:\root\usr\lib\gcc-lib
> -Lc:\root\usr\lib
> -Lc:\root\usr\lib\gcc-lib\i386-mingw32\egcs-2.91.66\..\..\..\..\i386-mingw32\lib
> -Lc:\root\usr\lib\gcc-lib\i386-mingw32\egcs-2.91.66\..\..\.. cpsh.o -lmingw32
> -lgcc -lmoldname -lmsvcrt -lkernel32 -ladvapi32 -lshell32 -lmingw32 -lgcc
> -lmoldname -lmsvcrt
> 
> cygcheck cpsh.exe
>   C:\WINNT\System32\kernel32.dll
>     C:\WINNT\System32\ntdll.dll
>   C:\WINNT\System32\crtdll.dll
>   C:\WINNT\System32\msvcrt.dll
> 

Thanks Earnie. 

The culprit is one of the import libraries, and the only possible culprit 
here is libmoldname.a. The problem I believe is in your setup, and not in 
the msvcrt add-on.

You need to make sure that the correct version of libmoldname.a is being
picked up. You'll see that I distribute a slightly different libmoldname.a
in the msvcrt add-on from what's in the egcs-1.1.2 standard/crtdll
distrib.

When using different specs that point to different libraries, espcially
with the same name, the best way to deal with it is via the -B flag, and
not necessarily via -specs flag. That's why my msvcrt add-on package 
simply overwrites the crtdll setup so that I can avoid answering the 
usual questions.

Regards,
Mumit



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com