public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista•com>
To: XOL <xol@mail•ru>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: perl under eldk for ppc8xx
Date: Tue, 20 May 2003 11:13:00 -0500	[thread overview]
Message-ID: <3ECA540C.2030506@mvista.com> (raw)
In-Reply-To: <E19I9dj-0002cW-00.xol-mail-ru@f21.mail.ru>


If you are going to be building perl, you really need to do it "self-hosted",
unless you are prepared to do significant modification to the perl build system.
  Perl insists on being self-hosted compiled, it generates dynamic signal lists
and other structures based on the machine performing the compile, obviously that
doesn't work right in a cross compile situation.

--Mark

XOL wrote:
> Hello.
> I found out that eldk 2.1.0 whic I'm using has no perl.
> Does anybody succeded to build perl for ppc8xx?
> Can you give please some details. Probably you have binaries/rpm
> Thank you. Xol.
>
>
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-05-20 16:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-20 16:06 perl under eldk for ppc8xx XOL
2003-05-20 16:13 ` Mark Hatle [this message]
2003-05-20 16:23   ` Re[2]: " XOL
2003-05-20 16:42     ` Mark Hatle
2003-05-20 17:25     ` Kernel parameters (Sandpoint X3 with Altimus MPC755) dong in kang
2003-05-20 17:37       ` Mark A. Greer
2003-05-20 17:56         ` dong in kang
2003-05-20 18:14           ` Mark A. Greer
2003-05-20 19:26             ` dong in kang
2003-05-20 19:35               ` Wolfgang Denk
2003-05-20 22:45               ` Mark A. Greer
2003-06-10 18:22                 ` dong in kang
2003-05-20 19:23     ` Re[2]: perl under eldk for ppc8xx Wolfgang Denk
2003-05-21 17:26     ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3ECA540C.2030506@mvista.com \
    --to=fray@mvista$(echo .)com \
    --cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
    --cc=xol@mail$(echo .)ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox