Mail Archives: cygwin/2000/08/31/14:13:39
On Thu, Aug 31, 2000 at 08:44:17PM +0400, Egor Duda wrote:
>Hi!
>
>Thursday, 31 August, 2000 Chris Faylor cgf AT cygnus DOT com wrote:
>
>>>(This argument is based on the supposition that dll's with the same
>>>name will always conflict. If I'm wrong about that supposition,
>>>please correct me...as I stated above, I'm a bit confused as to when
>>>dll's will conflict and when they will not)
>
>CF> Can someone write a simple test to verify Windows behavior? It's pointless
>CF> to argue about what Windows does with DLLs if we don't know for sure.
>
>with ease. all you need is two different builds of cygwin1.dll, sh.exe
>and strace.exe i've used my yesterday's build and current one.
>1. create 2 directories -- say c:\test\1 and c:\test\2
>2. copy first cygwin1.dll to c:\test\1 and other build to c:\test\2
>3. copy sh.exe and strace.exe into both c:\test\1 and c:\test\2
>4. start cmd.exe, cd c:\test\1, strace -o sh.log sh
>5. start cmd.exe, cd c:\test\2, strace -o sh.log sh
>6. look at the string containing "DLL build" in c:\test\1\sh.log and
>c:\test\2\sh.log
>
>voila
Duh. Of course I know that it is possible to load conflicting versions of
the Cygwin DLL. I guess that means that Windows doesn't just blindly use
DLLs of the same name (unless specially instructed to do so).
That means that the (so far hypothetical) DLL problems should be
solvable by keeping the DLLs in the same directory as the executables.
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -