From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jason Andryuk <jandryuk@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Mis-generation of shell script (run.do_install)?
Date: Tue, 11 Dec 2018 15:02:51 +0000 [thread overview]
Message-ID: <08a89c71b2e3e0f4380325985541c55df00b94da.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAKf6xputiV+k9m9p1dyhZG1d0wMQoWG5tCiZjpsVVu+bXp1X6A@mail.gmail.com>
On Tue, 2018-12-11 at 08:42 -0500, Jason Andryuk wrote:
> Has anyone ever seen a generated shell script missing functions?
>
> I have an OpenXT/OpenEmbedded setup where I had run many successful
> builds. I made a change and then re-ran the build - it failed in
> binutil's do_install with autotools_do_install command not found.
>
> core2-64-oe-linux/binutils/2.28-r0/temp/run.do_install.11776: line
> 124: autotools_do_install: command not found
>
> Sure enough, autotools_do_install is not in run.do_install.
>
> I had not changed binutils or any relevant variable, as far as I can
> tell. If I run with '-e' I see the full autotools_do_install
> function in the output. For some reason, the generated script wasn't
> including autotools_do_install.
>
> I tried binutils -c cleansstate, but that didn't work. I tried
> pruning the sstate-cache dir, but that didn't work. I tried deleting
> tmp-glibc and sstate-cache, but it had the same error when I rebuilt.
>
> Modifying binutils do_install by adding a comment and `true` lets it
> builds.
>
> I saw something similar one other time where the generated script was
> missing a function. I can't recall the details, but it was a
> different package and MACHINE.
>
> Any suggestions on debugging this?
It sounds like pysh in bitbake wasn't able to see a dependency on the
function in question. Creating a small/reproducible test case would be
how I'd approach it, there are tests on the pysh code in bitbake-
selftest for example.
Once I had a test case which failed, I'd then use that to debug and see
if I could figure out a fix.
Cheers,
Richard
next prev parent reply other threads:[~2018-12-11 15:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 13:42 Mis-generation of shell script (run.do_install)? Jason Andryuk
2018-12-11 15:02 ` Richard Purdie [this message]
2018-12-14 19:30 ` Jason Andryuk
2018-12-15 10:51 ` richard.purdie
2018-12-16 1:19 ` Jason Andryuk
2018-12-17 14:44 ` richard.purdie
2018-12-17 20:21 ` Andre McCurdy
2018-12-17 21:24 ` richard.purdie
2018-12-18 17:45 ` Jason Andryuk
2019-01-08 18:26 ` richard.purdie
2019-01-16 13:55 ` Jason Andryuk
2019-01-16 14:02 ` Richard Purdie
2019-01-16 20:20 ` Jason Andryuk
2019-01-16 20:28 ` Richard Purdie
2019-01-17 17:10 ` Jason Andryuk
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=08a89c71b2e3e0f4380325985541c55df00b94da.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jandryuk@gmail.com \
--cc=openembedded-core@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