Aldo Calpini wrote:
Allison Randal ha scritto:
We do. Unfortunately we can't rely on Perl 5 for the configure system.
It may seem like an easy way to gain cross-compilation in the short
term, but in the long term it will hurt us.
Miniparrot is the right way to go. It certainly needs work,
Allison Randal ha scritto:
We do. Unfortunately we can't rely on Perl 5 for the configure system.
It may seem like an easy way to gain cross-compilation in the short
term, but in the long term it will hurt us.
Miniparrot is the right way to go. It certainly needs work, though. As
you're
jerry gay ha scritto:
On 2/20/07, Aldo Calpini [EMAIL PROTECTED] wrote:
1) does anybody have objections to patching the current build system for
cross-compilation (even yes, but not now because... objections)?
no objection here! this is a long-desired feature, and is currently
unavailable.
Joshua Isom ha scritto:
Using perl 5's configure probes also somewhat limits us to how the
vendor distributed perl. It should also be considered that we can't
rely on perl5 being available, especially since we intend to replace
it eventually, so rewriting all the perl to support cross
Aldo Calpini wrote:
1) does anybody have objections to patching the current build system for
cross-compilation (even yes, but not now because... objections)?
Not at all. Cross-compilation is definitely a core goal for Parrot.
2) does anybody already have a .plan or something in mind about
back in 2004, Dan Sugalski wrote:
http://www.nntp.perl.org/group/perl.perl6.internals/2004/09/msg25521.html
nowadays my effort of porting Parrot to the PocketPC platform, as you
may have suspected, force me to reopen the question.
there is, I know, a lot of work to be done. and this will
On 2/20/07, Aldo Calpini [EMAIL PROTECTED] wrote:
back in 2004, Dan Sugalski wrote:
http://www.nntp.perl.org/group/perl.perl6.internals/2004/09/msg25521.html
nowadays my effort of porting Parrot to the PocketPC platform, as you
may have suspected, force me to reopen the question.
there is, I
On Feb 20, 2007, at 8:44 AM, jerry gay wrote:
On 2/20/07, Aldo Calpini [EMAIL PROTECTED] wrote:
no objection here! this is a long-desired feature, and is currently
unavailable. although i don't have a pocketpc to test on, i'll do my
best to help. for years, the dependence on perl 5's configure
On Tuesday 20 February 2007 03:55, Aldo Calpini wrote:
2) does anybody already have a .plan or something in mind about it (so
that I may either learn from what others have thought, or avoiding
reinventing some wheel)?
It would be nice, though I don't know how feasable it is, to be able to
On Oct-17, Dan Sugalski wrote:
At 9:49 AM -0400 10/17/04, Jacques Mony wrote:
Hello,
I'm trying to port parrot to the unununium operating system, which
uses a modified version of 'diet lib c'. Can anyone tell me if this
is actually possible to force the use of this library using the
Hello,
I'm trying to port parrot to the unununium operating system, which uses a
modified version of 'diet lib c'. Can anyone tell me if this is actually
possible to force the use of this library using the current Configure.pl
script or if I will need to change it a lot... or even replace it
At 9:49 AM -0400 10/17/04, Jacques Mony wrote:
Hello,
I'm trying to port parrot to the unununium operating system, which
uses a modified version of 'diet lib c'. Can anyone tell me if this
is actually possible to force the use of this library using the
current Configure.pl script or if I will
Hi,
Did anybody try to crosscompile parrot? It doesn't seem to work. I tried
it with parrot_2004-08-26_23 by setting
--cc=arm-softfloat-linux-gnu-gcc
--ld=arm-softfloat-linux-gnu-gcc
on configure, but that fails with:
--8--
[EMAIL PROTECTED]:~/tmp/parrot
At 7:32 PM +0200 9/1/04, Robert Schwebel wrote:
Hi,
Did anybody try to crosscompile parrot? It doesn't seem to work.
That doesn't surprise me. We still pull information out of the local
perl install (which'll be wrong, of course, in a cross-compilation
environment) and I'm pretty sure we don't
14 matches
Mail list logo
