Poky Project Discussions
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Can't build mtd-utils-native
Date: Sun, 06 Feb 2011 10:49:23 -0700	[thread overview]
Message-ID: <4D4EDF23.1010508@mlbassoc.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Using latest master 50387575ecdb05712958ea3c5caf023d6eb753ba
The recipe for mtd-utils-native fails to build, log attached.

Any ideas how to fix this?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

[-- Attachment #2: log.do_unpack --]
[-- Type: text/plain, Size: 4942 bytes --]

Cloning into /tmp/test_poky/tmp/work/i686-linux/mtd-utils-native-1.4.1-r1/git...
 done.
 fatal: Not a valid object name v1.4.1
 Error executing a python function in /tmp/poky-amltd/meta/recipes-devtools/mtd/mtd-utils_1.4.1.bb:
FetchError: Fetch command export HOME="/home/gthomas"; export GIT_CONFIG="/tmp/test_poky/tmp/sysroots/i686-linux/usr/etc/gitconfig"; export PATH="/tmp/test_poky/tmp/sysroots/i686-linux/usr/bin/i686-linux:/tmp/test_poky/tmp/sysroots/i686-linux/usr/bin:/tmp/test_poky/tmp/sysroots/i686-linux/usr/sbin:/tmp/test_poky/tmp/sysroots/i686-linux/usr/bin:/tmp/test_poky/tmp/sysroots/i686-linux/sbin:/tmp/test_poky/tmp/sysroots/i686-linux//bin:/home/local/poky-amltd/scripts:/home/local/poky-amltd/bitbake/bin/:/opt/amltd/bin:/usr/java/jdk1.6.0_10/bin:/home/gthomas/Android/android-sdk-linux_x86-1.1_r1/tools:/home/gthomas/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/tmp/poky-amltd/scripts"; git read-tree v1.4.1 failed with signal 128, output:
fatal: Not a valid object name v1.4.1


ERROR: Error executing a python function in /tmp/poky-amltd/meta/recipes-devtools/mtd/mtd-utils_1.4.1.bb:
FetchError: Fetch command export HOME="/home/gthomas"; export GIT_CONFIG="/tmp/test_poky/tmp/sysroots/i686-linux/usr/etc/gitconfig"; export PATH="/tmp/test_poky/tmp/sysroots/i686-linux/usr/bin/i686-linux:/tmp/test_poky/tmp/sysroots/i686-linux/usr/bin:/tmp/test_poky/tmp/sysroots/i686-linux/usr/sbin:/tmp/test_poky/tmp/sysroots/i686-linux/usr/bin:/tmp/test_poky/tmp/sysroots/i686-linux/sbin:/tmp/test_poky/tmp/sysroots/i686-linux//bin:/home/local/poky-amltd/scripts:/home/local/poky-amltd/bitbake/bin/:/opt/amltd/bin:/usr/java/jdk1.6.0_10/bin:/home/gthomas/Android/android-sdk-linux_x86-1.1_r1/tools:/home/gthomas/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/tmp/poky-amltd/scripts"; git read-tree v1.4.1 failed with signal 128, output:
fatal: Not a valid object name v1.4.1


The stack trace of python calls that resulted in this exception/failure was:
ERROR: The stack trace of python calls that resulted in this exception/failure was:
  File "base_do_unpack", line 34, in <module>
ERROR:   File "base_do_unpack", line 34, in <module>

ERROR: 
  File "base_do_unpack", line 28, in base_do_unpack
ERROR:   File "base_do_unpack", line 28, in base_do_unpack

ERROR: 
  File "/home/local/poky-amltd/bitbake/lib/bb/fetch2/git.py", line 168, in unpack
ERROR:   File "/home/local/poky-amltd/bitbake/lib/bb/fetch2/git.py", line 168, in unpack
    runfetchcmd("%s read-tree %s%s" % (ud.basecmd, ud.revisions[ud.names[0]], readpathspec), d)
ERROR:     runfetchcmd("%s read-tree %s%s" % (ud.basecmd, ud.revisions[ud.names[0]], readpathspec), d)

ERROR: 
  File "/home/local/poky-amltd/bitbake/lib/bb/fetch2/__init__.py", line 480, in runfetchcmd
ERROR:   File "/home/local/poky-amltd/bitbake/lib/bb/fetch2/__init__.py", line 480, in runfetchcmd
    raise FetchError("Fetch command %s failed with signal %s, output:\n%s" % (cmd, signal, output))
ERROR:     raise FetchError("Fetch command %s failed with signal %s, output:\n%s" % (cmd, signal, output))

ERROR: 
The code that was being executed was:
ERROR: The code that was being executed was:
     0030:		if not ret:
ERROR:      0030:		if not ret:
     0031:			raise bb.build.FuncFailed("oe_unpack_file failed with return value %s" % ret)
ERROR:      0031:			raise bb.build.FuncFailed("oe_unpack_file failed with return value %s" % ret)
     0032:
ERROR:      0032:
     0033:
ERROR:      0033:
 *** 0034:base_do_unpack(d)
ERROR:  *** 0034:base_do_unpack(d)
     0035:
ERROR:      0035:
(file: 'base_do_unpack', lineno: 34, function: <module>)
ERROR: (file: 'base_do_unpack', lineno: 34, function: <module>)
     0024:		else:
ERROR:      0024:		else:
     0025:			# use bb.fetch2 unpack API
ERROR:      0025:			# use bb.fetch2 unpack API
     0026:			ud = urldata[url]
ERROR:      0026:			ud = urldata[url]
     0027:			rootdir = bb.data.getVar('WORKDIR', localdata, True)
ERROR:      0027:			rootdir = bb.data.getVar('WORKDIR', localdata, True)
 *** 0028:			ret = ud.method.unpack(ud, rootdir, localdata)
ERROR:  *** 0028:			ret = ud.method.unpack(ud, rootdir, localdata)
     0029:		bb.utils.unlockfile(lf)
ERROR:      0029:		bb.utils.unlockfile(lf)
     0030:		if not ret:
ERROR:      0030:		if not ret:
     0031:			raise bb.build.FuncFailed("oe_unpack_file failed with return value %s" % ret)
ERROR:      0031:			raise bb.build.FuncFailed("oe_unpack_file failed with return value %s" % ret)
     0032:
ERROR:      0032:
(file: 'base_do_unpack', lineno: 28, function: base_do_unpack)
ERROR: (file: 'base_do_unpack', lineno: 28, function: base_do_unpack)
Function 'base_do_unpack' failed
ERROR: Function 'base_do_unpack' failed

             reply	other threads:[~2011-02-06 17:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 17:49 Gary Thomas [this message]
2011-02-07  7:00 ` Can't build mtd-utils-native Darren Hart
2011-02-07 13:08   ` Gary Thomas

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=4D4EDF23.1010508@mlbassoc.com \
    --to=gary@mlbassoc.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