----- Original Message -----
From: "Sisyphus"
And 4.7.0 won't work nicely with the perl that 4.6.0 built - and that
won't do. (About to have a closer look at this.)
Btw, the statement "4.7.0 won't work nicely with the perl that 4.6.0 built"
translates to something like "I can't use 4.7.0 to build perl extensions (ie
perl modules that need some C compilation) with my 4.6.0-built perl".
Turns out it's just that the perl import library built by 4.6.0 has the
wrong global symbols prefix for 4.7.0 - so no perl symbols get found. (The
thing of note here is that msys, yasm and mpir are not involved - yet
there's still that global symbols prefix issue.)
Two possible fixes:
1) Hack perl so that linking is done directly to the perl dll (instead of
the perl import library);
2) Use gendef.exe and 4.7.0's dlltool to build an appropriate import
library.
(Both approaches work, btw.)
Amazingly, my 4.7.0 works nicely with the perl built by Microsoft Platform
SDK for Windows Server 2003 R2, as also does my 4.6.0.
Well ... not so amazing, when I think about it. Those SDK-built perls have
already been hacked so that mingw64 links directly to the perl dll.
In any case, for various reasons (pertaining mainly to practicality), I'd
like to keep using 4.6.0. Looks like there'll need to be an awful lot of
rebuilding if I switch to 4.7.0.
I finally got to thinking (which is a dangerous thing for me to be doing)
... I could build a dynamic (assembler) build of mpir using 4.7.0, then use
gendef and 4.6.0's dlltool to create a 4.6.0-compliant import lib from the
4.7.0-built dll. That way, I end up with a dynamic assembler build of mpir
that I can use with 4.6.0. And, sure enough, that works !!
It then occurred to me that the dll I built didn't have to be built using
4.7.0 - I could have used 4.6.0 to build it.
So many hacks .... and not one of them right (hacker's heaven ;-)
Only drawback (from my pov) is that I've ended up with a dynamic library -
better if I could get a static lib that I could use with 4.6.0.
Cheers,
Rob
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en.
