On Fri, 26 May 2006, Joshua Gatcomb wrote:
> On 5/26/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
> >
> > I don't know anything about either msys or mingw, so I don't really know
> > what to recommend.
> >
> > I'm afraid I don't understand what a patch would actually try to do.
> > From your pr
On 5/26/06, Andy Dougherty <[EMAIL PROTECTED]> wrote:
I don't know anything about either msys or mingw, so I don't really know
what to recommend.
I'm afraid I don't understand what a patch would actually try to do.
From your previous message, it looks like sh.exe is changing the path
delimiters
On Fri, 26 May 2006, Joshua Gatcomb wrote:
> All:
> In tracking down why building parrot with mingw was failing, I discovered
> that the culprit was having msys in my PATH even if I wasn't intentionally
> trying to use it.
>
> There are 3 interesting things to note:
> 1. It does not matter what
All:
In tracking down why building parrot with mingw was failing, I discovered
that the culprit was having msys in my PATH even if I wasn't intentionally
trying to use it.
There are 3 interesting things to note:
1. It does not matter what msys is actually called - renaming the directory
to foo h
Jens Rieks <[EMAIL PROTECTED]> wrote:
> Status: MinGW should work, but I ran out of time.
Thanks for investigating. We'll include it in the next release.
> jens
leo
... compiles now, but "-lws2_32" is not yet automatically appended to the
linker options.
I can not run the tests because the ICU version bundled with parrot does not
support MinGW and my system ICU is currently not working due to an experiment
conducted earlier today.
Status: MinGW should wor
