Closed GoogleCodeExporter closed 8 years ago
I'm able to install it without any issues on my computer. I'm running XP Pro,
SP3. I
had multiple versions of Python installed. I also tried removing all versions of
Python and reinstalling Python 2.6 and gmpy.
Do you get the error message when you launch the gmpy installer?
casevh
Original comment by casevh
on 15 Oct 2008 at 3:27
> Do you get the error message when you launch the gmpy installer?
Yes.
Original comment by fredrik....@gmail.com
on 15 Oct 2008 at 8:46
I tried installing Python 2.6 and gmpy on an old Windows 2000 laptop without
any
issues. I wonder if you have a corrupted file. Could you try downloading it
again?
Could you also try the Core2 specific version? (It won't run, but should
install
just fine.)
Original comment by casevh
on 15 Oct 2008 at 8:53
The SHA1 hash is correct, a6477c0357befe91332339e8db097bfb043edf95.
The Core2 installer has the same problem.
Both the 2.4 and the 2.5 installers work.
Original comment by fredrik....@gmail.com
on 15 Oct 2008 at 9:29
This is getting strange. You may have a different set of DLLs on your machine
than I
do on mine. Can you run dependancy walker against the gmpy executable and see
if it
generates any errors?
http://www.dependencywalker.com/
Download and unzip. Start depends.exe. Then File | Open and select the gmpy
installer.
Original comment by casevh
on 16 Oct 2008 at 12:02
I almost suspected this from the start: installing .NET made it work.
I'm not sure if this is because the compiler has linked to some .NET modules,
or if
the existing modules on my computer were just outdated and the .NET installer
updated
them, or if there is some other reason.
Although it now installs, Dependency Walker does give errors.
"Warning: At least one module has an unresolved import due to a missing export
function in a delay-load dependent module."
The modules ADVAPI32.DLL, SHLWAPI.DLL, USER32.DLL, MPR.DLL are marked red. I
don't
know if any other information that it displays is relevant.
Original comment by fredrik....@gmail.com
on 16 Oct 2008 at 7:38
Interesting. I'll try to build the next releases on a machine that has never
had .NET
installed on it.
Original comment by casevh
on 19 Oct 2008 at 12:44
Original issue reported on code.google.com by
fredrik....@gmail.com
on 14 Oct 2008 at 7:56