On 18 Nov 2003 15:09:34 +0100, Juergen Boemmels <[EMAIL PROTECTED]> wrote:
>Pete Lomax <[EMAIL PROTECTED]> writes: > >> Hi, >> I've only just installed perl. Running Configure.pl on a windows box, >> I got 'bad command or file name' because line 12 of >> config\init\hints.pl is: >> my $hints = "config/init/hints/" . lc($^O) . ".pl"; >> I had to change it to: >> my $hints = "perl config/init/hints/" . lc($^O) . ".pl"; >> >> I'll carry on editing lines by hand, just though I should mention it. > >This is very strange. Last time I tested it Configure.pl runs under >windows without any changes. My bad, it was an error with my file associations, it is a little better now, that change is unnecessary, pls disregard. > >The main question is: what do you want to get from this? A compiled version 0.0.13 of course ;-) Now that Jonathan Worthington has put a new binary up, it is just a matter of wanting to be able to do it, if I ever need to. >$hints is passed to do, which reads the file and evals it in the >current interpreter. > >Normaly this "bad command or file name" come form failing system >calls. But there is no system in hints.pl nor in hints/mswin32.pl. >When playing around with windows it has bitten me sometimes that >stdout and stderr are not really in sync. So the error could be well >one test later or earlier. > >What is your Configure line? Is cl.exe (Visual compiler is the default >on windows) in your PATH or did you pass the right --cc= flag. I used --ask and specified gcc but it doesn't seem to help. See Jonathan Worthingtons reply to me. > >Sometimes I find Configure.pl a bit brief when you debugg things like >that. It might be a good idea to add a --verbose flag, which gives >some status information on the things that get done. Yes, It might help to have a few more of those 'and die(<msg>)' things (I don't know perl). Pete
