Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Randy MacLeod" <randy.macleod@windriver.com>
To: Joris Offouga <offougajoris@gmail.com>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #sdk #toolchain
Date: Thu, 27 Feb 2020 16:11:14 -0500	[thread overview]
Message-ID: <16596991-2bd3-e3eb-8a73-e39ed76bb574@windriver.com> (raw)
In-Reply-To: <IXoN.1582833408442429277.1EYp@lists.yoctoproject.org>

On 2/27/20 2:56 PM, Joris Offouga wrote:
> Hi all,
> 
> I am developing a custom distribution based on poky and I am creating an 
> extensible sdk from my image, but when I install this extensible sdk, I 
> find an error in python3 and an error in relocate.py. For my extensible 
> sdk to work I have to install the sdk generated by populate_sdk in its 
> default location. Do you have an idea to solve my problem?
> 
> You can see raw log :
> 
> SDK environment now set up; additionally you may now run devtool to 
> perform development tasks.
> Run devtool --help for further details.
> /home/jun/poky-evbb_sdk/sysroots/x86_64-pokysdk-linux/usr/bin/python3: 
> line 5: 
> /home/jun/poky-evbb_sdk/sysroots/x86_64-pokysdk-linux/usr/bin/python3.7.real: 
> No such file or directory
> post-relocate command 
> "/home/jun/poky-evbb_sdk/sysroots/x86_64-pokysdk-linux/post-relocate-setup.d/meson-setup.py 
> /home/jun/poky-evbb_sdk" failed with status 127
> SDK has been successfully set up and is ready to be used.
> Each time you wish to use the SDK in a new shell session, you need to 
> source the environment setup script e.g.
>   $ . 
> /home/jun/poky-evbb_sdk/environment-setup-armv7vet2hf-neon-evbox-linux-gnueabi 

Hi Joris,

Thanks for reporting the issue.

I can't test this right now.  Can you reproduce the problem
with just oe-core and a core-image that is similar to yours?

If you can, then please either debug this issue and submit a patch:
   https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

or open a defect describing:

  - your build host,
  - local.conf file
  - exact versions yocto software used and
  - the steps needed to reproduce the issue:
    https://bugzilla.yoctoproject.org/

Sorry, I can't help more right now.

../Randy
> 
> 
> Best regards,
> 
> Joris Offouga
> 
> 
> 


-- 
# Randy MacLeod
# Wind River Linux

      reply	other threads:[~2020-02-27 21:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27 19:56 #sdk #toolchain Joris Offouga
2020-02-27 21:11 ` Randy MacLeod [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=16596991-2bd3-e3eb-8a73-e39ed76bb574@windriver.com \
    --to=randy.macleod@windriver.com \
    --cc=offougajoris@gmail.com \
    --cc=yocto@lists.yoctoproject.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