Thanks for replying Rob! And you are even right!!!
But then I got this error:
dmake: Error: -- Configuration file `C:\Perl\site\bin\startup\startup.mk' not f
ound
Even though I got this path in my "PATH" enviroment variable:
C:\vanilla-perl\dmake\bin\startup
So I did something ugly, I copied the vanilla-perl startup dir to the C:\Perl\site\bin\ path
Then my test script worked,puha!
But isn't there a nicer way to do this?
It seems that Perl is not checking the right path eventhough its in the enviroment variable.
I mean there must be a way you can make perl look in the right spot.
(Its okay if you dont reply. it would just be nice to know.)
PS. Wow! Running "inline.pm" after a few hours on PerlMonks. I think I'll stick around for a bit :-)
Thanks again.
| [reply] |
dmake: Error: -- Configuration file `C:\Perl\site\bin\startup\startup.mk' not f ound
Looks like someone has put a copy of dmake.exe into C:\Perl\site\bin. I would delete it from there and also delete the startup folder you placed in Perl\site\bin. Having removed them, add C:\vanilla-perl\dmake\bin to your path environment variable, and all should be fine.
There's no reason you can't have dmake and the startup folder in C:\Perl\site\bin - except for the ugliness factor (as you noted). And you already have a perfectly functional dmake set up in vanilla perl - so better to simply use it (by amending the path) instead of creating an unnecessary duplicate of dmake and its startup folder.
Cheers,
Rob
Update: Come to think of it, C:\vanilla-perl\dmake\bin is probably already in the path - in which case simply deleting the copy of dmake.exe that was in C:\Perl\site\bin would have been sufficient.
| [reply]
[d/l]
[select] |
Right again!
I just may have placed a copy of dmake in that dir yesterday in mindless frustration.
Thanks!
| [reply] |