Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Fabien Proriol <Fabien.Proriol@jdsu.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] [PATCH] SDK: allow SDK path of various level
Date: Tue, 16 Oct 2012 14:42:00 +0000	[thread overview]
Message-ID: <507D71AB.6060209@jdsu.com> (raw)
In-Reply-To: <20121016142134.GC5662@denix.org>

>> In the previous version, tar extraction use the --strip-component
>> option with "4" hard coded value.
>> If we set another SDKPATH, with a different depth, the sdk installation
>> fails.
>>
>> This patch computes the level from the SDKPATH value.
> Thanks! That's part of the problem I was having lately. Although, I think this
> patch should go to OE-Core list instead...
OK, I re-sent this patch to OE-Core.

> Do you also see the problem building gcc-cross-initial/intermediate
> complaining about missing headers from sysroot (it loses -nativesdk suffix
> for some reason, when looking for the system headers), when building with the
> new SDKPATH/SDK_NAME? I believe there's some path hardcoded somewhere in the
> gcc/cross recipes, but I wasn't able to debug it yet...
>
No, I haven't seen this type of problem.
I will look if I see somethings wrong in recipe.
But now, with Yocto 1.2-RC4, I built for PowerPC, a toolchain, a target 
image with my applications, my own kernel, without any problem except 
the one this patch solved.

Fabien


      reply	other threads:[~2012-10-16 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1350394502-7745-1-git-send-email-fabien.proriol@jdsu.com>
2012-10-16 14:21 ` [oe] [PATCH] SDK: allow SDK path of various level Denys Dmytriyenko
2012-10-16 14:42   ` Fabien Proriol [this message]

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=507D71AB.6060209@jdsu.com \
    --to=fabien.proriol@jdsu.com \
    --cc=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.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