in reply to nmake, CPAN and Modules not listed in PPM
Are there any examples of computer output/errors that you can post along with the particular module being built and the make utility used?
You wouldn't happen to have tried MINGW? It has a unix-ish Make.exe and a gcc that creates native win32 binaries.
If a module is not in the Activestate PPM (or is it PPD) repository it may be in someone elses that you can have ppm.bat search through.
--blm--
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: nmake, CPAN and Modules not listed in PPM
by Flame (Deacon) on Oct 15, 2002 at 04:09 UTC | |
I aborted it, and got:
I tried again using XML::SAX, which I heard was 'Pure Perl' to see if it makes a difference, I grabbed output where I could:
Then
And
Unfortunately, I have no idea what just over half of that really means as I rarely work with CPAN (obviously, because it doesn't work...) I hope this helps... My code doesn't have bugs, it just develops random features. | [reply] [d/l] [select] |
by blm (Hermit) on Oct 15, 2002 at 05:29 UTC | |
Thanks this does help In the output from building Bundle::CPAN the build of Digest::MD5 failed because it could not find cl.exe the linking program that comes with Visual Studio. It may also come with what was MASM. MASM seems to have been renamed to Build environment and might need Visual Studio to install it anyway. Relevant line:
With XML::Sax it seemed to fail as a dependancy was unsatisfied. It seems to need XML::NamespaceSupport which you attempted to build next. (Good!). Unfortunately the build failed with the following output indicating a syntax error in the makefile. Possibily the module assumes a GNU or UNIX-like Make binary. This banner indicates nmake.exe is being used. If I remember correctly it has differences in its makefile syntax :-( IMHO there is no simple answer to these problems. The Bundle::CPAN found you were running windows and adjusted accordingly but needed a cl.exe linker to link binary objects. Can you get Visual Studio or do you already have it? I am not sure what is best to fix the other problem. You have tried various make utilities. I will try installing these on my development machine and see what I can do: make some helpful instructions or a binary package. All of this may come down to the fact that on windows one doesn't get the compiler included with the OS. This is why I try to use linux or something similar _where possible_ Updated: Reread root node. You do have Visual Studio 6! Cool! Make sure that the dos environment variables are registered so it can find the cl.exe etal in the path and the .lib files. There would have been an option to register these variables at installation of VS 6. If this was not done there may be a batch file you can run to do this. --blm-- | [reply] [d/l] [select] |
by strat (Canon) on Oct 15, 2002 at 11:27 UTC | |
This tells you that the program cl.exe is not found in PATH. cl.exe is somewhere in the paths of VisualC++. If you add the path where you find it to your PATH-Environmentvariable, this error will probably not occur any more... Write something like the following at the end of your autoexec.bat (and then reboot):
Best regards, | [reply] [d/l] [select] |
by Flame (Deacon) on Oct 16, 2002 at 03:07 UTC | |
Edit: I fixed the missing DLL problem, but now I try install Bundle::CPAN and it switches to a text prompt (blank line, I just type and see text, does'nt seem to do anything with the text)
My code doesn't have bugs, it just develops random features. | [reply] [d/l] |
by grantm (Parson) on Oct 15, 2002 at 20:12 UTC | |
I have just tried installing XML::SAX using the CPAN shell and it worked for me. I don't have a C compiler installed, and wonder if the fact that you do might be your problem. Here's the version information from my copy of nmake:
If your version is newer, that may be contributing to the makefile syntax error message you're getting. I got my older version via the link in the Perl-XML FAQ (above). | [reply] [d/l] |