From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: Richard Purdie
<public-richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@plane.gmane.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf/gcc: Add clean masks for stamp files
Date: Fri, 21 Sep 2012 14:22:56 +0100 [thread overview]
Message-ID: <1348233776.10108.75.camel@ted> (raw)
In-Reply-To: <1348220197.10108.34.camel@ted>
On Fri, 2012-09-21 at 10:36 +0100, Richard Purdie wrote:
> On Thu, 2012-09-20 at 20:03 +0200, Enrico Scholz wrote:
> >
> > Richard Purdie
> > <richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
> > writes:
> >
> > > +STAMPCLEAN = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}-*-*"
> >
> > Is it intended that this pattern can match unrelated packages? E.g. for
> > PN='gcc-cross', the mask will apply to stampfiles for 'gcc-cross-initial'
> > too.
>
> No, this is a problem :(
>
> I saw this last night and have been giving it some thought. We might
> have to put a separator into the stamp file format to make this easier
> to deal with. The downside is that is a TMPDIR layout change :/.
>
> The thing is the bug this solves is serious even if people only rarely
> hit it and I can't think of a better solution...
I've given this some more thought and there is an easier way out if we
assume PV starts with something numeric. Since the current situation is
rather problematic (I didn't see it locally due to another patch I
have), I've pushed a fix:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=3c101af5e33b21f53171c66de0c2c3e797d95247
I'm going to post some RFCs on other ideas related to this.
Cheers,
Richard
next prev parent reply other threads:[~2012-09-21 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 10:32 [PATCH] bitbake.conf/gcc: Add clean masks for stamp files Richard Purdie
2012-09-20 18:03 ` Enrico Scholz
2012-09-21 9:36 ` Richard Purdie
2012-09-21 13:22 ` Richard Purdie [this message]
2012-09-23 17:36 ` Khem Raj
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=1348233776.10108.75.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=public-richard.purdie-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@plane.gmane.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