From: "Steve Sakoman" <steve@sakoman.com>
To: Matthias Klein <matthias.klein@optimeas.de>
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Bug in dunfell branch because of commit "sdk: fix relocate symlink failed"?
Date: Thu, 2 Sep 2021 04:09:16 -1000 [thread overview]
Message-ID: <CAOSpxdYp6h9AAjMngMQvpwk+JegjS=RxHPGup7Rb5OaVX8HX1A@mail.gmail.com> (raw)
In-Reply-To: <AM0PR10MB3107CEBBE29A9972AAD796D799CE9@AM0PR10MB3107.EURPRD10.PROD.OUTLOOK.COM>
On Thu, Sep 2, 2021 at 2:55 AM Matthias Klein
<matthias.klein@optimeas.de> wrote:
>
> Hello,
>
> the following commit needs the variable SDK_BUILD_PATH which doesn't seem to exist in the dunfell branch: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/files/toolchain-shar-relocate.sh?h=dunfell&id=d6f40be29bf56a835f5825692a22365f04aeb6c3
> This leads to countless messages being displayed during the installation:
>
> sed: -e expression #1, char 0: no previous regular expression
It appears that dunfell also should have:
https://git.openembedded.org/openembedded-core/commit/?id=bc4ee5453560dcefc4a4ecc5657df5cc1666e153
Could you see if this resolves the issue?
Steve
> Shouldn't the process be aborted with an error message at the first problem?
>
> Many greetings,
> Matthias
>
>
>
>
next prev parent reply other threads:[~2021-09-02 14:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 12:54 Bug in dunfell branch because of commit "sdk: fix relocate symlink failed"? Matthias Klein
2021-09-02 14:09 ` Steve Sakoman [this message]
2021-09-02 14:35 ` [yocto] " Matthias Klein
2021-09-03 5:48 ` Matthias Klein
2021-09-03 20:06 ` Steve Sakoman
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='CAOSpxdYp6h9AAjMngMQvpwk+JegjS=RxHPGup7Rb5OaVX8HX1A@mail.gmail.com' \
--to=steve@sakoman.com \
--cc=matthias.klein@optimeas.de \
--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 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.