John Brown wrote:
>
> On Mon, 14 Mar 2011 08:21:09 -0400, Earnie wrote:
>
>>
>> Maybe the base address is the same for both libraries and therefore has
>> memory collision? As I understand Windows workings, if the dll is in
>> the same directory as the binary then that dll would be used. But if
>
On Mon, 14 Mar 2011 08:21:09 -0400, Earnie wrote:
>
> Maybe the base address is the same for both libraries and therefore has
> memory collision? As I understand Windows workings, if the dll is in
> the same directory as the binary then that dll would be used. But if
> both dll have the same entr
On 3/14/2011 8:21 AM, Earnie wrote:
>>> An ugly workaround to the real problem is to put program A in a
>>> directory with its libstdc++-6.dll and put program B in another
>>> directory with its libstdc++-6.dll and then add the directories to PATH.
>>
>> This doesn't work, although I don't yet unde
Paul Leder wrote:
> On 11/03/2011 13:17, Earnie wrote:
>
>> An ugly workaround to the real problem is to put program A in a
>> directory with its libstdc++-6.dll and put program B in another
>> directory with its libstdc++-6.dll and then add the directories to PATH.
>
> This doesn't work, althoug
On 11/03/2011 13:17, Earnie wrote:
> An ugly workaround to the real problem is to put program A in a
> directory with its libstdc++-6.dll and put program B in another
> directory with its libstdc++-6.dll and then add the directories to PATH.
This doesn't work, although I don't yet understand why.
