On Tue, Nov 18, 2003 at 09:57:02AM -0500, Dan Sugalski wrote:
> FWIW, with these changes rather than using the literal "perl" use $^X
> instead. That picks up the perl being used rather than whatever comes
> first in the search path, which may not be the perl being used for
> configure.
There was
On 02 Dec 2003 18:37:15 +0100, Juergen Boemmels
<[EMAIL PROTECTED]> wrote:
>Pete Lomax <[EMAIL PROTECTED]> writes:
>
>> Command line used was:
>> $ perl -e "open STDERR,'>&STDOUT'; exec qq{$^X Configure.pl --cc=gcc
>> --cgoto=0 --jitcapable=0 --verbose}" > conf.out
>>
>> Output file is attached
>
On 19 Nov 2003 16:03:59 +0100, Juergen Boemmels
<[EMAIL PROTECTED]> wrote:
> Could you try out the attached patch.
>
diff -u -r1.16 mswin32.pl
--- config/init/hints/mswin32.pl15 Oct 2003 12:06:24 - 1.16
+++ config/init/hints/mswin32.pl19 Nov 2003 14:30:26 -
@@ -95,6
On 19 Nov 2003 16:00:00 +0100, Juergen Boemmels
<[EMAIL PROTECTED]> wrote:
>Are there any people out there building parrot on MinGW?
>config/init/hints/mswin32.pl is far from complete.
I'm quite happy to be the first/only testing this
>
>Could you try out the attached patch.
Sorry, no can do thi
? $_
? languages/befunge/befunge.pbc
? t/src/headers.t
Index: config/init/hints/mswin32.pl
===
RCS file: /cvs/public/parrot/config/init/hints/mswin32.pl,v
retrieving revision 1.16
diff -u -r1.16 mswin32.pl
--- config/init/hints/mswin32
Pete Lomax <[EMAIL PROTECTED]> writes:
> On 18 Nov 2003 18:37:57 +0100, Juergen Boemmels
> <[EMAIL PROTECTED]> wrote:
>
> >I assume he runs it with perl Configure.pl --ask
> Yes
>
> >The problem is that --ask option of has not the knowledge to change
> >the options according to the compiler. I d
On 18 Nov 2003 18:37:57 +0100, Juergen Boemmels
<[EMAIL PROTECTED]> wrote:
>I assume he runs it with perl Configure.pl --ask
Yes
>The problem is that --ask option of has not the knowledge to change
>the options according to the compiler. I don't know a simple fix for
>this.
>
>A workaround soluti
"Jonathan Worthington" <[EMAIL PROTECTED]> writes:
> Pete sent me some further info off list, here's what happens when he runs
> Configure:-
I assume he runs it with
perl Configure.pl --ask
> Parrot Version 0.0.13 Configure 2.0
> Copyright (C) 2001-2003 The Perl Foundation. All Rights Reserved.
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 =
> On Tue, 18 Nov 2003, Juergen Boemmels 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/
boemmels at physik.uni-kl dot de wrote:
> Pete Lomax writes:
>
> > 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 chan
On Tue, 18 Nov 2003, Juergen Boemmels 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
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 = "p
- Original Message -
From: "Pete Lomax" <[EMAIL PROTECTED]>
To: "Pete Lomax" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, November 17, 2003 10:20 PM
Subject: Re: configure on windows
> On Mon, 17 Nov 2003 20:46:32 +, Pete Loma
On Mon, 17 Nov 2003 20:46:32 +, Pete Lomax
<[EMAIL PROTECTED]> wrote:
>I got 'bad command or file name' because line 12 of
>config\init\hints.pl is:
> my $hints = "config/init/hints/" . lc($^O) . ".pl";
PS: that was the dos error, shouldn't there be an and/or die thing
somewhere near it?
Pete
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
16 matches
Mail list logo
