From: Martin Jansa <martin.jansa@gmail.com>
To: Ulf Magnusson <ulfalizer@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Detecting missing build dependencies
Date: Wed, 27 Jan 2016 15:59:46 +0100 [thread overview]
Message-ID: <20160127145946.GI2574@jama> (raw)
In-Reply-To: <CAFkk2KRbEnfcia1sq0keuFedUhMCNng3YWdbfCr=Osxw_qkeOQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
On Wed, Jan 27, 2016 at 03:45:30PM +0100, Ulf Magnusson wrote:
> Hello,
>
> If a recipe has a missing build dependency that the sysroot just
> happens to contain anyway from an earlier build, then the build will
> succeed only to fail later when the sysroot no longer has the build
> dependency. We want to avoid that, so we're looking for ways to
> automatically check for unspecified build dependencies.
>
> The only method I know of at the moment is to remove or rename tmp/ so
> that the build uses a fresh sysroot and then trying to rebuild the
> recipe. Is there something nicer? I think I remember reading about a
> script for testing for missing build dependencies, but I might be
> misremembering.
See openembedded-core/scripts/test-dependencies.sh but it basically
automates rebuilding recipes after removing TMPDIR, but also it detects
autodetected dependencies.
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-01-27 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 14:45 Detecting missing build dependencies Ulf Magnusson
2016-01-27 14:59 ` Martin Jansa [this message]
2016-01-27 15:02 ` Burton, Ross
2016-01-27 15:29 ` Ulf Magnusson
2016-01-27 15:48 ` Burton, Ross
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=20160127145946.GI2574@jama \
--to=martin.jansa@gmail.com \
--cc=ulfalizer@gmail.com \
--cc=yocto@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.