From: Christopher Friedt <cfriedt@visible-assets.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Cross compiling libperl
Date: Wed, 14 Nov 2007 09:01:35 +0100 [thread overview]
Message-ID: <473AAB5F.5030404@visible-assets.com> (raw)
In-Reply-To: <47388443.4020403@hiramoto.org>
Alternatively, what I've done in the past, was actually natively compile
badly behaved packages using Qemu/ARM.
This is naturally slightly slower.
Chris
Karl Hiramoto wrote:
> Petric Frank wrote:
>> Hello,
>>
>> i've read the mail from Corey <corey@...> (dd. 2006-11-20 03:13:19 GMT).
>>
>> The problem is that the build process compiles a test program for the
>> destination platform and afterwards it tries to execute it.
>> This will never work when cross compiling.
>>
>> Are there any workarounds available (patches for the ebuild, etc.) ?
>>
>> regards
>> Petric
>>
>
> There are a lot of packages like this that come this way from upstream
>
> Options that have worked for me
> 1. modify the configure script and/or makefiles to not run the test program
>
> 2. In a few cases i complied gcc for my ARM platform, then compiled
> natively.. I think perl was one of these.. It took hours to compile..
>
> --
> Karl.
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2007-11-14 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 17:07 [gentoo-embedded] Cross compiling libperl Petric Frank
2007-11-12 16:50 ` Karl Hiramoto
2007-11-14 8:01 ` Christopher Friedt [this message]
2007-11-19 4:08 ` Mike Frysinger
2007-11-19 4:08 ` Mike Frysinger
2007-11-19 17:59 ` Petric Frank
2007-11-20 5:26 ` Mike Frysinger
2007-11-20 18:34 ` Petric Frank
2007-11-21 17:40 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2006-11-20 3:13 [gentoo-embedded] cross " Corey
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=473AAB5F.5030404@visible-assets.com \
--to=cfriedt@visible-assets.com \
--cc=gentoo-embedded@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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