All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: New fetcher failure for local files
Date: Fri, 20 May 2011 07:37:31 -0700	[thread overview]
Message-ID: <4DD67CAB.2060604@gmail.com> (raw)
In-Reply-To: <BF0FE697-3489-4B92-AB20-36DE6B63E5C0@dominion.thruhere.net>

On 5/20/2011 12:25 AM, Koen Kooi wrote:
> Hi,
>
> Since a few days the fetcher is behaving strangely:
>
> NOTE: package linux-omap-psp-2.6.32-r99b+gitr5fc29e7b2a76a64a739f857858ef0b98294aa155: task do_fetch: Started
> ERROR: Function 'Fetcher failure for URL: 'file://defconfig'. Unable to fetch URL file://defconfig from any source.' failed
>
> It is present:
>
> koen@dominion:/OE/tentacle/sources/meta-texasinstruments$ find . -name "defconfig" | grep beagle
> ./recipes-bsp/linux/linux-omap-psp-2.6.32/beagleboard/defconfig
> ./recipes-bsp/linux/linux-omap/beagleboard/defconfig
>
> The strange thing is that it will work once (e.g. bitbake console-image) but it will fail after switching TCLIBC. And once it started failing, it doesn't work for the default TCLIBC either.
>
> What's the best way to debug this? -DDD isn't giving much clues, nor does strace :(
>

one reason could be FILESPATH is missing the paths which are appended 
with overrides like MACHINE and others
check dump of bitbake -e <recipe>
> regards,
>
> Koen
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  parent reply	other threads:[~2011-05-20 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20  7:25 New fetcher failure for local files Koen Kooi
2011-05-20  8:35 ` Koen Kooi
2011-05-20 14:37 ` Khem Raj [this message]
2011-05-31 18:00 ` 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=4DD67CAB.2060604@gmail.com \
    --to=raj.khem@gmail.com \
    --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 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.