I've been staring at this ticket for more than a year. One of my
earlier patches got us part of the way there. Applying Reini's or
something like that would get us closer.
But the more I look at this problem in light of
https://trac.parrot.org/parrot/ticket/586,
https://trac.parrot.org/parrot/ti
Can you assign it to me?
2008/12/30 Reini Urban :
> 2008/12/30 James Keenan via RT:
>> On Tue May 06 17:56:23 2008, jk...@verizon.net wrote:
>>> No. I only figured out how to keep track of files generated during
>>> configuration, not during build. We need some of what, IIRC, particle
>>> termed
2008/12/30 James Keenan via RT:
> On Tue May 06 17:56:23 2008, jk...@verizon.net wrote:
>> No. I only figured out how to keep track of files generated during
>> configuration, not during build. We need some of what, IIRC, particle
>> termed "makefile trickery" to keep track of files generated by
James Keenan via RT schrieb:
On Tue May 06 17:15:39 2008, coke wrote:
If the patch is applied, can we close this ticket?
No. I only figured out how to keep track of files generated during
configuration, not during build. We need some of what, IIRC, particle
termed "makefile trickery" to keep
On Tue May 06 17:15:39 2008, coke wrote:
>
> If the patch is applied, can we close this ticket?
>
No. I only figured out how to keep track of files generated during
configuration, not during build. We need some of what, IIRC, particle
termed "makefile trickery" to keep track of files generat
Alright, take 3: Store the fact that this is real configuration in the
Parrot::Configure object just before calling runsteps().
Index: lib/Parrot/Configure/Compiler.pm
===
--- lib/Parrot/Configure/Compiler.pm(revision 26526)
+++ l
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 Nov 11 12:04:20 2006, particle wrote:
> we need ... some config hackery to do it during
> configure-time.
>
> this would replace the MANIFEST.generated file which is created ex
> post facto with a file that is created at build-time.
>
Herewith some configure-time hackery. This patch prov
# New Ticket Created by Jerry Gay
# Please include the string: [perl #40817]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40817 >
arguably the best way to track which files are generated during
parrot's configure/build pr
12 matches
Mail list logo
