From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Using Kernel git tree tries to extract non extractable file
Date: Thu, 12 Apr 2012 15:08:25 +0200 [thread overview]
Message-ID: <20120412150825.2b1d1057@skate> (raw)
In-Reply-To: <loom.20120412T112933-744@post.gmane.org>
Le Thu, 12 Apr 2012 12:33:43 +0000 (UTC),
Graham <gnewton@peavey-eu.com> a ?crit :
> I would have thought that as git provides a source tree "as is" there
> is no need to uncompress.
When you specify the source of a package as a git tree, what Buildroot
keeps inside the dl/ directory is a tarball of the sources, as
generated by 'git archive'. For the corresponding code, see the
DOWNLOAD_GIT macro in package/Makefile.package.in.
> Output :
> linux 2.6.34 Downloading
> Initialized empty Git repository
> in /home/gnewton/buildroot-2012.02/dl/linux- 2.6.34/
> remote: Counting objects: 1901116, done.
> remote: Compressing objects: 100% (315962/315962), done.
> remote: Total 1901116 (delta 1568013), reused 1900830 (delta 1567732)
> Receiving objects: 100% (1901116/1901116), 443.51 MiB | 19.29 MiB/s,
> done. Resolving deltas: 100% (1568013/1568013), done.
> fatal: Not a valid object name
Hint: this is the problem. The
BR2_LINUX_KERNEL_CUSTOM_GIT_VERSION="2.6.34" you're passing is not a
valid version name: it should be a commit hash, or the name of a tag,
or the name of a branch. This is where your problem is.
However, it is not normal that Buildroot does not abort here on such
error, this should be fixed.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-04-12 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 12:33 [Buildroot] Using Kernel git tree tries to extract non extractable file Graham
2012-04-12 13:08 ` Thomas Petazzoni [this message]
2012-04-12 13:51 ` Graham Newton
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=20120412150825.2b1d1057@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.