Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Race condition or something when fetching local	files?
Date: Thu, 20 Oct 2011 20:47:21 -0400	[thread overview]
Message-ID: <20111021004721.GW26170@denix.org> (raw)
In-Reply-To: <20111018201708.GC556@jama.jama.net>

On Tue, Oct 18, 2011 at 10:17:08PM +0200, Martin Jansa wrote:
> On Tue, Oct 18, 2011 at 01:09:43PM -0700, Khem Raj wrote:
> > On Tue, Oct 18, 2011 at 11:35 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > > I have noticed that even local patches are stored in downloads dir,
> > > but today I've noticed that wrong file was used later in do_patch.
> > > I have latest oe-core/meta-oe + latest bitbake.
> > >
> > > Pulseaudio was building here for first time
> > >
> > > downloads/buildfix.patch is from previous build of xf86-video-intel-2.16.0
> > > $ head downloads/buildfix.patch
> > 
> > looking in bitbake lib/bb/fetch2/local.py it seems it searches DL_DIR
> > before other
> 
> Which would be wrong for sure if I have
> foo_1.0.bb with SRC_URI = "file://bar.patch"
> 
> foo-1.0/om-gta02/bar.patch
> foo-1.0/nokia900/bar.patch
> 
> Then I don't want to use bar.patch from downloads/bar.patch where it's
> from om-gta02 build when I'm building nokia900 now.

Was there any resolution on this one?

-- 
Denys



  reply	other threads:[~2011-10-21  1:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 18:35 Race condition or something when fetching local files? Martin Jansa
2011-10-18 20:09 ` Khem Raj
2011-10-18 20:17   ` Martin Jansa
2011-10-21  0:47     ` Denys Dmytriyenko [this message]
2011-11-01  9:30       ` Martin Jansa
2011-11-01 20:44     ` Martin Jansa

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=20111021004721.GW26170@denix.org \
    --to=denis@denix.org \
    --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