|Do you know where your variables are?|
Re^9: Module::Install hackingby syphilis (Chancellor)
|on Sep 14, 2012 at 13:38 UTC||Need Help??|
If you know different, I defer; but that's my understanding at this point
I certainly don't claim to *know* a lot about this - but it was our (mine and aero's) experience that one of my past x64 builds of PDL wouldn't work (because of missing entry point) on x64 Strawberry unless we either:
a) Replaced Strawberry/c/bin/libgcc_s_sjlj-1.dll with my 4.7.0 version of the same file or
b) employed the current hack.
I did ask about this on the Strawberry list - and it was there that I was put on to the hack that I've used.
At the link you provided, I see:
If a DLL with the same module name is already loaded in memory, the system checks only for redirection and a manifest before resolving to the loaded DLL, no matter which directory it is in. The system does not search for the DLL.
There are no manifest files involved (afaik) ... and the quote I've just provided suggests to me that the already-loaded dll will therefore be used.
Admittedly I'm not sure what "redirection" is .... or what "resolving to the loaded DLL" exactly means. (What dictionary do they use in Redmond ?)
Thinking a bit more about it ... I guess that it could have been the case that the libgcc_s_sjlj-1.dll that I had provided from my 4.7.0 compiler was simply located in the wrong place. (But I think we checked that wasn't happening.)
I'll re-visit this tomorrow with a much simpler test case than PDL - just to be sure.