Summary: | problem with generated dll in MS C# environment | ||
---|---|---|---|
Product: | binutils | Reporter: | Helmut Dipper <helmut.dipper> |
Component: | ld | Assignee: | unassigned |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | bug-binutils |
Priority: | P2 | ||
Version: | 2.15 | ||
Target Milestone: | --- | ||
Host: | Target: | i686-pc-cygwin | |
Build: | i686-pc-cygwin-gnu | Last reconfirmed: |
Description
Helmut Dipper
2005-07-07 13:31:58 UTC
(In reply to comment #0) > My program written in MS C# (for example "nant" from sourceforge) uses a > function written in pure C and compiled and linked to a dll with cygwin-gcc: if > linked with option "-mno-cygwin" function is executed as expected. if linked > without the option "-mno-cygwin" program finishes execution after return from > function without any message. This much is expected. It is not possible to use a Cygwin-native DLL without the rest of the Cygwin runtime support present and correctly initialised, in particular cygwin1.dll. > Linking a gcc-created *.o with MSVC-linker to a > dll is not possible, because the MSVC-linker cannot read the used dll's out of > the cygwin-environment. This statement is unclear and confusing: is the MS linker trying to link a cygwin DLL or a gcc-created .o? Either way, it's impossible to tell from a rough description whether this is just a manifestation of the same problem above. Compatibility with the MS tools has been much improved since this report was filed, but if a problem can be demonstrated on up-to-date binutils we can re-open this bug. cheers, DaveK |