From: Hongxu Jia <hongxu.jia@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Saul Wold <saul.wold@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/3] apr: fix cross compiling failed
Date: Wed, 28 May 2014 19:25:26 +0800 [thread overview]
Message-ID: <5385C7A6.4020103@windriver.com> (raw)
In-Reply-To: <CAJTo0La0d-hJs9-Lgpaw_4Zm4gJ2=Y9F47J-SPcTbwACa62mrg@mail.gmail.com>
On 05/28/2014 06:48 PM, Burton, Ross wrote:
> On 28 May 2014 10:05, Hongxu Jia <hongxu.jia@windriver.com> wrote:
>> The tools/gen_test_char was invoked at build time, and it didn't
>> work for the cross compiling, so we used the native one to instead.
> Building all of libapr natively and installing the extra binary is
> wasteful when the binary is trivially compiled natively in the target
> build.
>
> Simply add a do_compile_prepend() that uses BUILD_CC and so on to
> compile tools/gen_test_char. As it only uses standard C headers this
> is trivial and you won't need to patch the build at all (obviously
> test when MACHINE is massively incompatible with the host, ie qemuarm
> with x86 host).
Sounds reasonable, I will do that in V2.
//Hongxu
> Ross
next prev parent reply other threads:[~2014-05-28 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 9:05 [PATCH 0/3] upgrade: apr to 1.5.1 and apr-utils to 1.5.3 Hongxu Jia
2014-05-28 9:05 ` [PATCH 1/3] apr: upgrade to 1.5.1 Hongxu Jia
2014-05-28 9:05 ` [PATCH 2/3] apr: fix cross compiling failed Hongxu Jia
2014-05-28 10:48 ` Burton, Ross
2014-05-28 11:25 ` Hongxu Jia [this message]
2014-05-28 9:05 ` [PATCH 3/3] apr-util: upgrade to 1.5.3 Hongxu Jia
-- strict thread matches above, loose matches on Subject: below --
2014-05-30 3:27 [PATCH V2 0/3] upgrade: apr to 1.5.1 and apr-utils " Hongxu Jia
2014-05-30 3:27 ` [PATCH 2/3] apr: fix cross compiling failed Hongxu Jia
2014-05-30 11:22 ` Burton, Ross
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=5385C7A6.4020103@windriver.com \
--to=hongxu.jia@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
--cc=saul.wold@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.