chromatic wrote:
On Sunday 01 April 2007 07:15, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
needs a "make cle
Steve Peters wrote:
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote:
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
n
Eric Hanchrow wrote:
"Ron" == Ron Blaschke <[EMAIL PROTECTED]> writes:
Ron> If you see this error
...
Ron> the file has Windows line endings
Dare I suggest that parrot not be so fussy about line endings?
I second that. ;) Actually, both things are supposed only as
workarounds until
On Sunday 01 April 2007 07:15, Ron Blaschke wrote:
> As recently discussed it is currently necessary to include the absolute
> path to F in the environment variable PATH. This should be
> done before trying to built parrot, otherwise one gets a broken
> F and F. One
> needs a "make clean" or rem
On Sun, Apr 01, 2007 at 04:15:24PM +0200, Ron Blaschke wrote:
> Hi,
>
> As recently discussed it is currently necessary to include the absolute
> path to F in the environment variable PATH. This should be
> done before trying to built parrot, otherwise one gets a broken
> F and F. One
> need
> "Ron" == Ron Blaschke <[EMAIL PROTECTED]> writes:
Ron> If you see this error
...
Ron> the file has Windows line endings
Dare I suggest that parrot not be so fussy about line endings?
--
If you're trying to choose between two theories and one gives
you an excuse for being lazy, the
Hi,
As recently discussed it is currently necessary to include the absolute
path to F in the environment variable PATH. This should be
done before trying to built parrot, otherwise one gets a broken
F and F. One
needs a "make clean" or remove *both* files before trying again. Make
sure to
