On Fri, 18 Jul 2008, James Keenan via RT wrote:
> On Fri Jul 18 08:22:48 2008, doughera wrote:
>
> >
> > Oh yes -- I did remember one other. Configure.pl currently offers you
> the
> > opportunity to specify different sizes for opcode_t and INTVAL. However,
> > parrot itself assumes they are
On Fri Jul 18 08:22:48 2008, doughera wrote:
>
> Oh yes -- I did remember one other. Configure.pl currently offers you
the
> opportunity to specify different sizes for opcode_t and INTVAL. However,
> parrot itself assumes they are the same size. (See [perl #56810] for a
> little more backgr
Applied in r29499. Marking ticket resolved.
Applied in r29499. Marking ticket resolved.
On Mon, Jul 14, 2008 at 10:05 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> Tested in the 'noautopack' branch. Passed all pre- and
> post-configuration tests; built correctly; passed all tests in 'make test'.
>
> If no one objects, I'll apply this patch after tomorrow's release.
>
> Thank y
Tested in the 'noautopack' branch. Passed all pre- and
post-configuration tests; built correctly; passed all tests in 'make test'.
If no one objects, I'll apply this patch after tomorrow's release.
Thank you very much.
kid51
Index: lib/Parrot/Configure/Step/List.pm
=
On Mon Jul 14 18:44:51 2008, [EMAIL PROTECTED] wrote:
> On Mon Jul 14 17:14:09 2008, doughera wrote:
> > Yes. Look at the Config variables that are set, and then grep for
> them in
> > the source tree. You'll find they are never used.
> >
>
>
> So it would appear. I'll change the Subject
