From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Handle the hossttools directory when restoring from the sstate cache
Date: Sat, 29 Apr 2017 09:52:54 +0100 [thread overview]
Message-ID: <1493455974.19076.167.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1493391620.git.pkj@axis.com>
On Fri, 2017-04-28 at 17:01 +0200, Peter Kjellerstedt wrote:
> After the introduction of copying host tools to the build directory
> and cleaning out $PATH, we got a problem with one of our tools. It
> turned out that its configure.ac uses AC_PATH_PROG(PERL, perl) to
> locate the perl interpreter, and uses that on the shebang line of the
> installed tool. Previously it found /usr/bin/perl and used that, but
> now it will find ${TMPDIR}/hosttools/perl and use that instead, which
> means that if the tool is restored from the sstate cache in another
> build directory than where it originated from, the path will be
> wrong.
>
> These two patches adds a new variable (HOSTTOOLS_DIR) for the
> ${TMPDIR}/hosttools directory, and then makes sure it is handled by
> the staging code so that any references to its value are properly
> corrected when restoring from the sstate cache.
I did mention on irc that I didn't really want to do this, I only
wanted to fix this issue on a case by case basis.
The reason is that we currently have pretty clean sstate files in this
regard, we haven't needed to do this. If we add this, we'll become
reliant on the fixups. The fixups are slow and ideally we want to pass
in correct paths in the first place if/as/where we can.
So is there a way we can only do this if/as/where needed instead of
universally?
The performance overhead of fixups verses no fixups is significant.
Cheers,
Richard
next prev parent reply other threads:[~2017-04-29 8:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 15:01 [PATCH 0/2] Handle the hossttools directory when restoring from the sstate cache Peter Kjellerstedt
2017-04-28 15:01 ` [PATCH 1/2] bitbake.conf: Add HOSTTOOLS_DIR for ${TMPDIR}/hosttools Peter Kjellerstedt
2017-04-28 15:01 ` [PATCH 2/2] sstate.bbclass, staging.bbclass: Handle HOSTTOOLS_DIR when restoring state Peter Kjellerstedt
2017-04-28 15:06 ` Burton, Ross
2017-04-28 20:24 ` Peter Kjellerstedt
2017-04-29 8:52 ` Richard Purdie [this message]
2017-04-29 18:07 ` [PATCH 0/2] Handle the hossttools directory when restoring from the sstate cache Peter Kjellerstedt
2017-05-01 8:14 ` Richard Purdie
2017-05-03 21:12 ` Peter Kjellerstedt
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=1493455974.19076.167.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=peter.kjellerstedt@axis.com \
/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