Thanks to some persistent effort on the part of Brett Estrade, not only
can we verify that the patch works and the ticket may be closed, but we
get our first smoke reports on Dragonfly BSD as well:
http://tinyurl.com/yp2fqk
On Mon, 12 Nov 2007, chromatic via RT wrote:
> On Monday 12 November 2007 12:33:41 Andy Dougherty wrote:
> > It may well be there's an issue with gcc's optimizer, since the problem
> > goes away without optimization, but I think it's also fair to say that
> > the definition of FLOAT_IS_ZERO in in
Klaas-Jan Stol via RT wrote:
Is there any reason not to close this ticket?
Do it.
Allison
On Thu Nov 08 12:14:15 2007, kjs wrote:
> On Sat Jul 15 23:35:50 2006, mdiep wrote:
> > When IMCC encounters an unexpected identifier, it throws an error,
> > but it doesn't say what the unexpected identifier was. This is
> > painful for debugging compilers and should be fixed.
> >
> >mini
On Thu Nov 08 12:23:50 2007, kjs wrote:
> To my knowledge, the :init flag is implemented and there are no problems
> with it.
>
> Is there any reason not to close this ticket?
>
> kjs
forgot to cc the list. See my previous comment.
kjs
On Thu Nov 08 12:04:02 2007, kjs wrote:
> On Sat Dec 16 19:06:42 2006, [EMAIL PROTECTED] wrote:
> > This is still valid, but I think it hides a bigger problem with -E. The
> > attached patch avoids the segfault by passing the correct arguments to
> > yylex(), but then it runs into an infinite loop
The PARROT_ASSERT was replaced back by assert's by ptc++.
kjs
On Mon, Nov 12, 2007 at 12:33:41PM -0800, Andy Dougherty wrote:
> It may well be there's an issue with gcc's optimizer, since the problem
> goes away without optimization, but I think it's also fair to say that
> the definition of FLOAT_IS_ZERO in include/parrot/misc.h is
> perhaps not optimal he
On Sun Jun 12 06:09:47 2005, coke wrote:
> Neither are p6i archives a good place to keep TODO items. =-)
>
> Chip said that Leo said:
> >> A note WRT exception handlers
> >> Leo posted a quick discussion of the correct use of exception
> handlers
> >> in Parrot. Essentially, the rule is,
On Wed Sep 05 12:58:32 2007, bernhard wrote:
>
> > thanks for the quick turnaround. this test is perfect for the
> > 'executed from pir test case', and will be applied shortly.
> The test case has been added in r21092.
>
> > but as
> > patrick later provided an example of executing a .pbc file, w
On Tue, Nov 13, 2007 at 01:10:11PM -0800, Klaas-Jan Stol via RT wrote:
> On Wed Sep 05 12:58:32 2007, bernhard wrote:
> >
> > > thanks for the quick turnaround. this test is perfect for the
> > > 'executed from pir test case', and will be applied shortly.
> > The test case has been added in r21092
Earlier today during #parrotsketch I reported a problem with
installing Test::TAP::HTMLMatrix, needed in order to run the
'make smoke' target.
perlfan++ on #parrot has found the likely culprit -- the
Test::TAP::Model module needs to have Test::Harness::Results
available, and it's apparently not li
Andy,
Could you supply the output of perl -V for the system where you are
encountering these problems?
Also it would be good to have the output of prove -v for each of the
failing t/configure/*.t tests.
Thank you very much.
kid51
On Sun Nov 11 22:29:21 2007, ptc wrote:
>
> My next guess now is that the -std=c89 gcc compiler option doesn't
> play nicely with your system headers. I've removed the compiler flag
> in r22809, see how you go.
>
> Paul
>
It did. Now Darwin is back to failing just one non-coding-standards
t
# New Ticket Created by James Keenan
# Please include the string: [perl #47425]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=47425 >
Failed twice for me on Linux tonight. Here's the output of 'prove -v':
t/dynpmc/dynlex
Patches applied to trunk in r22826.
16 matches
Mail list logo
