From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Richard Purdie <richard.purdie@linuxfoundation.org>,
Khem Raj <raj.khem@gmail.com>
Subject: Re: gcc-configure-common: Use build time sysroot for target gcc
Date: Thu, 14 Jun 2012 10:14:29 -0700 [thread overview]
Message-ID: <4FDA1BF5.2000005@linux.intel.com> (raw)
In-Reply-To: <1339575975-22078-1-git-send-email-bogdan.a.marinescu@intel.com>
On 06/13/2012 01:26 AM, Bogdan Marinescu wrote:
> From: Khem Raj<raj.khem@gmail.com>
>
> Otherwise it assumes / as sysroot on build host and starts
> searching for directories in there.
>
> Signed-off-by: Khem Raj<raj.khem@gmail.com>
> ---
> diff --git a/meta/recipes-devtools/gcc/gcc-configure-target.inc b/meta/recipes-devtools/gcc/gcc-configure-target.inc
> index 1ee7504..5bca2b7 100644
> --- a/meta/recipes-devtools/gcc/gcc-configure-target.inc
> +++ b/meta/recipes-devtools/gcc/gcc-configure-target.inc
> @@ -1,4 +1,6 @@
> require gcc-configure-common.inc
>
> EXTRA_OECONF_PATHS = " \
> + --with-sysroot \
I can't seem to find the reply to this, but RP added a "=" to the
end of this and that seems to have re-introduced the problem we were
attempting to fix.
Apparently this is a bug in the configure script then also.
Sau!
> + --with-build-sysroot=${STAGING_DIR_TARGET} \
> --with-gxx-include-dir=${includedir}/c++/"
> --
> cgit v0.9.0.2-39-g756e
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-06-14 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 8:26 gcc-configure-common: Use build time sysroot for target gcc Bogdan Marinescu
2012-06-14 17:14 ` Saul Wold [this message]
2012-06-14 18:51 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2012-06-13 8:20 Bogdan Marinescu
2012-06-13 8:23 ` Marinescu, Bogdan A
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=4FDA1BF5.2000005@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.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