On Mon, 30 Jun 2008, chromatic wrote:
> > On Mon, Jun 30, 2008 at 3:55 PM, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> > > Given a regular x86 (GNU/Linux) box, using GCC 4.2.3, should the
> > > following produce a working Parrot, using 64-bit ints?
> > >
> > > perl Configure.pl --intval="long long
chromatic wrote:
On Monday 30 June 2008 13:00:37 Will Coleda wrote:
# New Ticket Created by Will Coleda
# Please include the string: [perl #56484]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56484 >
Any time we can pro
On Monday 30 June 2008 13:00:37 Will Coleda wrote:
> # New Ticket Created by Will Coleda
> # Please include the string: [perl #56484]
> # in the subject line of all future correspondence about this issue.
> # http://rt.perl.org/rt3/Ticket/Display.html?id=56484 >
>
>
> Any time we can produce a s
Any time we can produce a segfault, that's bad. CC'ing rt to get a ticket.
On Mon, Jun 30, 2008 at 3:55 PM, Ron Blaschke <[EMAIL PROTECTED]> wrote:
> Given a regular x86 (GNU/Linux) box, using GCC 4.2.3, should the following
> produce a working Parrot, using 64-bit ints?
>
> perl Configure.pl --
# New Ticket Created by Will Coleda
# Please include the string: [perl #56484]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=56484 >
Any time we can produce a segfault, that's bad. CC'ing rt to get a ticket.
On Mon, Jun
Given a regular x86 (GNU/Linux) box, using GCC 4.2.3, should the
following produce a working Parrot, using 64-bit ints?
perl Configure.pl --intval="long long int" --opcode="long long int"
If fails for me on C while building PGE.
../../parrot -o PGE.pbc --output-pbc PGE.pir
../../parrot .
