Here's a patch that does the minimal amount of work necessary to tell
ExtUtils::MakeMaker how to build Parrot::Embed from a compiled but
uninstalled Parrot. It works on Linux; my hope is that it will work much
better on Windows.
If it doesn't, it's because of one missing configuration item, so I believe we
can fix this with relative ease.
Testers welcome, especially on non-Linux platforms.
-- c
Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
cd Parrot-Embed && C:\Perl\bin\perl.exe Makefile.PL && nmake
Warning: PERL_LIB
(C:\TEMP\perl-----------------------------------------please-r
un-the-install-script----------------------------------------\lib) seems
not to
be a perl library directory
(Exporter.pm not found) at C:/Perl/lib/ExtUtils/MM_Unix.pm line
1676.
Have C:\Perl\lib\Config.pm expected
C:\TEMP\perl--------------------------------
---------please-run-the-install-script----------------------------------------\l
ib\Config.pm
Your perl and your Config.pm seem to have different ideas about the
architecture they are running on.
Perl thinks: [lib]
Config says: [MSWin32-x86-multi-thread]
This may or may not cause problems. Please check your installation of perl
if you have problems building this extension.
Note (probably harmless): No library found for libparrot0A)
Writing Makefile for Parrot::Embed
Microsoft (R) Program Maintenance Utility Version 6.00.8168.0
Copyright (C) Microsoft Corp 1988-1998. All rights reserved.
NMAKE : fatal error U1073: don't know how to make
'C:\TEMP\perl-----------------
------------------------please-run-the-install-script---------------------------
-------------\lib\Config.pm'
Stop.
But I don't think your module is to blame. PPM went and installed
ExtUtils::CBuilder in
"C:\TEMP\perl-----------------------------------------please-run-the-install-script---------------------------
-------------\lib\", which tells me that something is REALLY messed up
somewhere in my Perl installation. Why or since when, I've no idea. So I
guess I'd best try re-installing that and I'll give this another go and
let you know.
Thanks,
Jonathan