From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/6] patch.bbclass: do_patch: unset TMPDIR from environment
Date: Fri, 14 Mar 2014 18:17:04 +0800 [thread overview]
Message-ID: <5322D720.8080309@windriver.com> (raw)
In-Reply-To: <CAJTo0LZXYBmSy4bme8Y3MaYCZ=X2VRabbXOeSNVX7TEubVOKPg@mail.gmail.com>
On 03/14/2014 12:54 AM, Burton, Ross wrote:
> On 13 March 2014 16:46, Burton, Ross <ross.burton@intel.com> wrote:
>> On 11 March 2014 17:08, Robert Yang <liezhi.yang@windriver.com> wrote:
>>> We need unset it after we use it, otherwise it would affect the env
>>> after we run "bb.build.exec_func('do_patch', d)", and will cause
>>> unexpected errors.
>>
>> This assignment has been there since October 2012, so what are the
>> problems that this causes?
>
> So what bothers me about this (and the original patch) is that TMPDIR
> has special meaning to bitbake and the conflict with patch's temporary
> directory is unfortunate. Maybe a better solution is to change
> meta/lib/oe/patch.py to set TMPDIR when invoking patch so the changed
> TMPDIR is constrained to the patch process and nothing else.
>
Hi Ross,
The problem is that:
1) do_patch set "TMPDIR" in env, it would remove the directory but didn't
unset the "TMPDIR".
2) autoconf will use the "TMPDIR" from the env:
autoconf/Autom4te/General.pm: my $TMPDIR = $ENV{'TMPDIR'} || '/tmp';
And if the dir doesn't exist, there would be errors.
I had met this problem because I used the do_patch and do_configure
in one task:
bb.build.exec_func('do_patch', d)
bb.build.exec_func('do_configure', d)
I had split them into 2 tasks, so the "TMPDIR" doesn't affact the
archiver.bbclass any more.
I've tried to set the TMPDIR in meta/lib/oe/patch.py, but met more
problems, the PATCHTOOL = "patch" doesn't work (Seems only on
OpenSuse 12.2), I've filed a bug for it:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5968
I think that we can fix it in another thread since it doesn't affect
the archiver.bbclass, as we have talked, we may drop the
PATCHTOOL = "patch"
// Robert
> Ross
>
>
next prev parent reply other threads:[~2014-03-14 10:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 17:08 [PATCH 0/6 V3] refactor the archiver*.bbclass Robert Yang
2014-03-11 17:08 ` [PATCH 1/6] classes/archive*.bbclass: remove archive-*-source.bbclass Robert Yang
2014-03-11 17:08 ` [PATCH 2/6] archiver.bbclass: refactor it Robert Yang
2014-03-19 12:12 ` Paul Eggleton
2014-03-20 1:22 ` Robert Yang
2014-03-20 7:38 ` Robert Yang
2014-03-11 17:08 ` [PATCH 3/6] package_rpm.bbclass: archive the source to srpm package Robert Yang
2014-03-13 17:39 ` Burton, Ross
2014-03-14 2:14 ` Robert Yang
2014-03-14 10:59 ` Burton, Ross
2014-03-11 17:08 ` [PATCH 4/6] archiver.bbclass: move a few code to copyleft_compliance.bbclass Robert Yang
2014-03-19 12:09 ` Paul Eggleton
2014-03-20 1:18 ` Robert Yang
2014-03-11 17:08 ` [PATCH 5/6] local.conf.sample.extended: update for the archiver Robert Yang
2014-03-11 17:08 ` [PATCH 6/6] patch.bbclass: do_patch: unset TMPDIR from environment Robert Yang
2014-03-13 16:46 ` Burton, Ross
2014-03-13 16:54 ` Burton, Ross
2014-03-13 18:11 ` Chris Larson
2014-03-14 10:17 ` Robert Yang [this message]
2014-03-13 17:45 ` [PATCH 0/6 V3] refactor the archiver*.bbclass Burton, Ross
2014-03-14 15:03 ` Robert Yang
2014-03-21 17:03 ` Richard Purdie
2014-03-19 12:14 ` Paul Eggleton
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=5322D720.8080309@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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