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, tho
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 think
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
we can't realistically get a
miniparrot, maybe it should be considered if building a miniparrot for
configuration is a good idea. Instead of rewriting everything now in
perl5 to support cross compiling, maybe we should dive in and try to
see if we can get it rewritten in pir. After all, we
however that discussion merits
one or more separate message threads.
yuck. shortly after I sent my message I stumbled upon
http://rt.perl.org/rt3/Public/Bug/Display.html?id=31136. and my first
thought was "oh, no".
having the build system done by a miniparrot isn't going to be
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 p
on perl5 being available, especially since we intend to replace it
eventually, so rewriting all the perl to support cross compiling would
likely not be the best thing.
2) does anybody already have a .plan or something in mind about it (so
that I may either learn from what others have thought
y work. for example, everything that is pulled out from Perl's
%Config will need to be pulled out from somewhere else if, and _only
if_, we are currently cross-compiling. (well, this is the plan. I can't
exclude that something somewhere may break for some obscure reason, so
please be
from Perl's
%Config will need to be pulled out from somewhere else if, and _only
if_, we are currently cross-compiling. (well, this is the plan. I can't
exclude that something somewhere may break for some obscure reason, so
please bear with me in advance :-).
before I start dirting my
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
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 ne
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 wit
ficiently.
Some assumptions could be made, and autoconf's knowledge could be
distilled a bit and then extracted into the [cross-]compiling database
that would be needed by Parrot.
--
â 781-324-3772
â [EMAIL PROTECTED]
â http://www.ajs.com/~ajs
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 pa
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>
On Tue, 2 Jan 2001, Jeff Okamoto wrote:
> I know this isn't necessarily a topic for -internals, but if someone
> could direct me to the right ML to think about how to make Perl easier
> to cross-compile, I'll take the discussion there.
[EMAIL PROTECTED] would be the right list, but Jarkko and I
> An OS problem and a build environment (cross-compilation, yuk)
> problem. I once managed to compile miniperl (5.005) for Chorus.
> I'm about to unearth the cross-compilation changes I had to make to
> get that working. (You thought Configure was hairy enough already?
> Think again: the test ex
17 matches
Mail list logo
