> "Ron" == Ron Blaschke <[EMAIL PROTECTED]> writes:
Ron> Sorry, I guess there was some mental PATH overloading going
Ron> on. Try adding the absolute path to F to PATH.
Ron> export PATH=/path/to/parrot/blib/lib:$PATH
Ron> And then "make."
OK, that gets me past that failu
Eric Hanchrow wrote:
I think it's relevant to note that I'm using the native Win32
subversion client, and hence most of my files are in DOS format:
carriage-return/linefeed at the end of each line. If I convert that
file's line endings to Unix format (plain line-feeds) it works.
You're right,
chromatic wrote:
On Friday 30 March 2007 07:35, Ron Blaschke wrote:
Not 100% on this, but I think one or two of the stm tests hang, too.
t/pmc/stmlog.t, test 2?
No, I think this one's fine. More like t/stm/queue.t test 2 and
t/stm/runtime.t test 4. Actually, t/stm/queue.t sometimes seems
On Friday 30 March 2007 07:35, Ron Blaschke wrote:
> Not 100% on this, but I think one or two of the stm tests hang, too.
t/pmc/stmlog.t, test 2?
-- c
Paul Cochrane wrote:
Sorry, I guess there was some mental PATH overloading going on. Try
adding the absolute path to F to PATH.
export PATH=/path/to/parrot/blib/lib:$PATH
And then "make."
I tried this (although, I appended the blib path to PATH, not sure if
that makes a difference) and
Ron Blaschke wrote:
Paul Cochrane wrote:
I don't know if it's of much help, but I too am getting the Cygwin
build barfing when miniparrot goes to build
runtime/parrot/include/config.fpmc.
I think that's actually a good sign. Try adding the absolute path to
F and try again. If this is workin
Joshua Gatcomb wrote:
On 3/28/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Joshua Gatcomb wrote:
If you could hang out on #parrot (irc.perl.org) when myself, Jonathan,
particle, etc are around - it would go a long way towards getting a
reproduceable test case that can be correctly articulated
Paul Cochrane wrote:
I don't know if it's of much help, but I too am getting the Cygwin
build barfing when miniparrot goes to build
runtime/parrot/include/config.fpmc.
I think that's actually a good sign. Try adding the absolute path to
F and try again. If this is working please see my previ
I don't know if it's of much help, but I too am getting the Cygwin
build barfing when miniparrot goes to build
runtime/parrot/include/config.fpmc.
Paul
On 3/28/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Joshua Gatcomb wrote:
> Really? No one on #parrot has been able to get parrot to work on Cygwin
> for months.
Interesting, didn't know about this.
The issue for the longest time was that miniparrot.exe would silently die
and not even gdb c
> "Joshua" == Joshua Gatcomb <[EMAIL PROTECTED]> writes:
Joshua> Really? No one on #parrot has been able to get parrot to
Joshua> work on Cygwin for months. The reason has changed since
Joshua> this specific ticket but if you have a working cygwin
Joshua> build can you please
Eric Hanchrow schrieb:
I use Cygwin and am willing to occasionally test the build on it.
Alas I have no clue how to actually -develop- for Cygwin, so I doubt
I'd be much help fixing any problems that I find. But I'd be happy to
"svn up; perl Configure.pl && make all test" and summarize or post t
Hi All!
On 28/03/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Joshua Gatcomb wrote:
> On 3/26/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
>>
>> Not sure about the details of this issue, but r17772 seems to build fine
>> on Cygwin.
>
> Really? No one on #parrot has been able to get parrot to work
I use Cygwin and am willing to occasionally test the build on it.
Alas I have no clue how to actually -develop- for Cygwin, so I doubt
I'd be much help fixing any problems that I find. But I'd be happy to
"svn up; perl Configure.pl && make all test" and summarize or post the
results.
--
I'd like
Joshua Gatcomb wrote:
On 3/26/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Not sure about the details of this issue, but r17772 seems to build fine
on Cygwin.
Really? No one on #parrot has been able to get parrot to work on Cygwin
for months.
Interesting, didn't know about this.
The reas
On 3/26/07, Ron Blaschke <[EMAIL PROTECTED]> wrote:
Not sure about the details of this issue, but r17772 seems to build fine
on Cygwin.
Really? No one on #parrot has been able to get parrot to work on Cygwin for
months. The reason has changed since this specific ticket but if you have a
wor
Not sure about the details of this issue, but r17772 seems to build fine
on Cygwin.
Here's the output of "make test" on my box.
Failed Test Stat Wstat Total Fail Failed List of Failed
---
t/codingstd/
Hi Nick,
Nick Glencross via RT wrote:
Yes, there's a problem building dynclasses on cygwin. [I think that there
are a few related calls logged]
One quick hack to complete the build is to type 'echo all: >
src/dynclasses/Makefile' after running Configure.pl.
Many thanks. I shall do that in
On 12/21/05, via RT Justin Koser <[EMAIL PROTECTED]> wrote:
> # New Ticket Created by Justin Koser
> # Please include the string: [perl #37997]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/rt3/Ticket/Display.html?id=37997 >
>
>
> Hello Parrot hac
# New Ticket Created by Justin Koser
# Please include the string: [perl #37997]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=37997 >
Hello Parrot hackers,
I'm trying to build Subversion revision 10604 of Parrot on Cygwi
20 matches
Mail list logo
