On Sunday 23 March 2008 21:46:23 jerry gay wrote:
> On Sun, Mar 23, 2008 at 9:39 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > On Sunday 23 March 2008 20:58:24 jerry gay wrote:
> > > why not put the location of parrot's lib dir in
> > > Parrot::Config::Generated, and look it up when needed?
>
On Sun, Mar 23, 2008 at 9:39 PM, chromatic <[EMAIL PROTECTED]> wrote:
> On Sunday 23 March 2008 20:58:24 jerry gay wrote:
>
> > why not put the location of parrot's lib dir in
> > Parrot::Config::Generated, and look it up when needed?
>
> Isn't Parrot::Config::Generated *in* Parrot's lib dir?
>
On Sunday 23 March 2008 20:58:24 jerry gay wrote:
> why not put the location of parrot's lib dir in
> Parrot::Config::Generated, and look it up when needed?
Isn't Parrot::Config::Generated *in* Parrot's lib dir?
-- c
On Sun, Mar 23, 2008 at 06:21:38PM -0700, James Keenan via RT wrote:
> On Sat Mar 22 10:38:42 2008, doughera wrote:
>
> > Just be careful that 'use lib' doesn't look outside of the parrot source
> > tree. If pmc2c.pl is normally invoked from the root directory, then
> > ../lib and ../../lib are
On Sun, Mar 23, 2008 at 6:21 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> On Sat Mar 22 10:38:42 2008, doughera wrote:
>
> > Just be careful that 'use lib' doesn't look outside of the parrot source
> > tree. If pmc2c.pl is normally invoked from the root directory, then
> > ../lib and ..
On Sun, Mar 23, 2008 at 7:49 PM, James Keenan via RT
<[EMAIL PROTECTED]> wrote:
> Hmm, the more I look at this, the more I realize that even the improved
> version of my patch is not ready for prime time. While it DWIMs when
> you call 'perl Configure.pl', it doesn't when you call 'perl
> Confi
Hmm, the more I look at this, the more I realize that even the improved
version of my patch is not ready for prime time. While it DWIMs when
you call 'perl Configure.pl', it doesn't when you call 'perl
Configure.pl --test' (as I do frequently). We only want
MANIFEST.configure.generated to be open
On Sunday 23 March 2008 19:17:41 James Keenan via RT wrote:
> Index: lib/Parrot/Configure/Utils.pm
> ===
> --- lib/Parrot/Configure/Utils.pm (revision 26524)
> +++ lib/Parrot/Configure/Utils.pm (working copy)
> @@ -311,6
Here's a corrected version of the patch. It eliminates some
"uninitialized value" warnings in t/configure/034-step.t and prepends
the needed path to the *.pasm entries in MANIFEST.configure.generated.
Index: lib/Parrot/Configure/Compiler.pm
=
On Sat Mar 22 10:38:42 2008, doughera wrote:
> Just be careful that 'use lib' doesn't look outside of the parrot source
> tree. If pmc2c.pl is normally invoked from the root directory, then
> ../lib and ../../lib are looking outside of the parrot source. This is
> wrong, since there is no gua
# New Ticket Created by Matt Kraai
# Please include the string: [perl #52026]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52026 >
Howdy,
docs/project/cage_cleaners_guide.pod says that in order to use icc to
build Parrot
# New Ticket Created by Matt Kraai
# Please include the string: [perl #52028]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52028 >
Howdy,
If a macro invocation that uses CONST_STRING is split into multiple
lines, icc use
James Keenan via RT wrote:
On Sat Dec 16 21:56:15 2006, allison wrote:
Adequately covered by PDD 13. Leaving ticket to Jonathan to close when
implemented.
Your cage cleaner wants to know ... has this been implemented?
No, not yet.
Jonathan
# New Ticket Created by Matt Kraai
# Please include the string: [perl #52022]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=52022 >
Howdy,
I'm using git-svn and have made some local commits. When I run
perl Configure.p
14 matches
Mail list logo
