From: Gary Thomas <gary@mlbassoc.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Can't build mtd-utils-native
Date: Mon, 07 Feb 2011 06:08:17 -0700 [thread overview]
Message-ID: <4D4FEEC1.5080403@mlbassoc.com> (raw)
In-Reply-To: <4D4F98A1.9030408@linux.intel.com>
On 02/07/2011 12:00 AM, Darren Hart wrote:
> On 02/06/2011 09:49 AM, Gary Thomas wrote:
>> Using latest master 50387575ecdb05712958ea3c5caf023d6eb753ba
>> The recipe for mtd-utils-native fails to build, log attached.
>>
>> Any ideas how to fix this?
>>
>
> I hit this earlier... let me dig up the logs...
>
> Feb 03 14:25:35<dvhart> RP__, I'll see if I can resolve this, but mtd_utils do_unpack fails with the new fetcher patch - I reverted it and was able to move past it
> Feb 03 14:25:44<dvhart> git read-tree v1.4.1 failed with signal 128, output:
> Feb 03 14:25:44<dvhart> | fatal: Not a valid object name v1.4.1
> Feb 03 14:30:38<RP__> dvhart: Hmm, which patch did you revert to get past it?
> Feb 03 14:30:52<dvhart> dfc5faf717ac1f917af398097d5295128548a55d
> Feb 03 14:31:00<dvhart> which looking at - doesn't make a lot of sense
> Feb 03 14:31:00<-- juliefl has quit (Quit: Leaving.)
> Feb 03 14:31:22<RP__> dvhart: no :/
> Feb 03 14:32:55<dvhart> but the do_unpack log now reports success and the do_patch followed and completed
> Feb 03 14:33:11 * dvhart kills, cleans, and rebuilds mtd_utils
> ...
> Feb 03 15:01:28<dvhart> RP__, appears to have been a false alarm :/ sorry about that, can't explain it, but I'm not able to reproduce
>
> So, two things to try.
>
> 1) do a _full_ clean and try again
> $ bitbake -c cleanall mtd-utils-native
> $ rm -rf downloads/*mtd-utils* downloads/git/*mtd-utils* sstate-cache/*mtd-utils
> $ bitbake mtd-utils-native
>
> If you are still able to produce it,
>
> 2) try reverting the commit above
> $ git revert dfc5faf717ac1f917af398097d5295128548a55d
> followed by all the commands in step 1) above.
>
> Please let us know how it goes, if we have an elusive fetcher bug, we need all
> the details on it we can get.
Still fails. Log attached.
Note: you can see that this GIT tree has been in my source
cache for a long time (since late 2009) and only now does
it cause problems.
$ ls -l /work/misc/Poky/sources/git/git.infradead.org.mtd-utils.git/.git
total 92
-rw-r--r-- 1 gthomas gthomas 735 Dec 24 07:06 FETCH_HEAD
-rw-r--r-- 1 gthomas gthomas 23 Jan 7 2009 HEAD
drwxr-xr-x+ 2 gthomas gthomas 4096 Jan 7 2009 branches
-rw-r--r-- 1 gthomas gthomas 262 Jan 7 2009 config
-rw-r--r-- 1 gthomas gthomas 58 Jan 7 2009 description
drwxr-xr-x+ 2 gthomas gthomas 4096 Nov 1 2009 hooks
-rw-rw-rw- 1 gthomas gthomas 23387 Dec 24 07:06 index
drwxr-xr-x+ 2 gthomas gthomas 4096 Nov 1 2009 info
drwxr-xr-x+ 3 gthomas gthomas 4096 Nov 1 2009 logs
drwxr-xr-x+ 7 gthomas gthomas 4096 Dec 24 07:06 objects
-rw-r--r-- 1 gthomas gthomas 401 Jan 7 2009 packed-refs
drwxr-xr-x+ 5 gthomas gthomas 4096 Nov 1 2009 refs
Also, the tag in question is there.
When I removed it from my source cache, the fetch/unpack worked fine.
Interestingly, what is being cached seems to have changed (but I don't
think the recipe has). Perhaps this has something to do with the error
I was seeing.
$ ls -ltr /work/misc/Poky/sources/*mtd*
-rw-r--r-- 1 gthomas gthomas 339413 Aug 23 2008 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_b995f89a81589be8d8a41c374a6df109d0ee12b3.tar.gz
-rw-r--r-- 1 gthomas gthomas 32 Oct 12 2009 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_9845d92440bd87739c89edd000fd6e0c47fab185.tar.gz.md5
-rw-r--r-- 1 gthomas gthomas 283980 Oct 12 2009 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_9845d92440bd87739c89edd000fd6e0c47fab185.tar.gz
-rw-rw-r-- 1 gthomas gthomas 409433 Oct 13 2009 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_ea429635388f7bb53f62c41ec3d5ccf5fa207370.tar.gz
-rw-r--r-- 1 gthomas gthomas 32 Jan 5 2010 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_ea429635388f7bb53f62c41ec3d5ccf5fa207370.tar.gz.md5
-rw-r--r-- 1 gthomas gthomas 32 Jun 29 2010 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_b995f89a81589be8d8a41c374a6df109d0ee12b3.tar.gz.md5
-rw-r--r-- 1 gthomas gthomas 424036 Sep 28 18:42 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_v1.3.1.tar.gz
-rw-rw-rw- 1 gthomas gthomas 422807 Dec 24 07:06 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_v1.4.1.tar.gz
-rw-r--r-- 1 gthomas gthomas 32 Jan 17 08:04 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_v1.3.1.tar.gz.md5
-rw-rw-rw- 1 gthomas gthomas 32 Feb 2 11:03 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git_v1.4.1.tar.gz.md5
-rw-rw-rw- 1 gthomas gthomas 32 Feb 7 05:49 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git.tar.gz.md5
-rw-rw-rw- 1 gthomas gthomas 1371209 Feb 7 05:49 /work/misc/Poky/sources/git_git.infradead.org.mtd-utils.git.tar.gz
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2011-02-07 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 17:49 Can't build mtd-utils-native Gary Thomas
2011-02-07 7:00 ` Darren Hart
2011-02-07 13:08 ` Gary Thomas [this message]
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=4D4FEEC1.5080403@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=dvhart@linux.intel.com \
--cc=poky@lists.pokylinux.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