From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Problems building for Olimex A13. A new user enquires ...
Date: Mon, 19 May 2014 08:43:02 +0200 [thread overview]
Message-ID: <20140519084302.1a0259f3@free-electrons.com> (raw)
In-Reply-To: <09d801cf72fa$f6cc2c40$e46484c0$@novadsp.com>
Hello,
On Mon, 19 May 2014 01:40:42 +0100, g4 at novadsp.com wrote:
> --------------------------snip------------------------------
> make[1]: Leaving directory `/home/jevans/olimex/buildroot'
> >>> uboot Downloading
There is no U-Boot version specified. I'd say your Buildroot
configuration might be wrong.
> Doing shallow clone
> Cloning into 'uboot-'...
> warning: Could not find remote branch --bare to clone.
> fatal: Remote branch --bare not found in upstream origin
> Unexpected end of command stream
> Doing full clone
> Cloning into bare repository 'uboot-'...
> remote: Reusing existing pack: 261244, done.
> remote: Counting objects: 52, done.
> remote: Compressing objects: 100% (52/52), done.
> remote: Total 261296 (delta 29), reused 2 (delta 0)
> Receiving objects: 100% (261296/261296), 72.68 MiB | 228.00 KiB/s, done.
> Resolving deltas: 100% (205455/205455), done.
> Checking connectivity... done.
> usage: git archive [options] <tree-ish> [<path>...]
Which /might/ explain why git archive is failing (but not sure).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-19 6:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 0:40 [Buildroot] Problems building for Olimex A13. A new user enquires g4 at novadsp.com
2014-05-19 2:56 ` Baruch Siach
2014-05-19 9:52 ` g4 at novadsp.com
2014-05-19 10:08 ` Maxime Ripard
2014-05-19 12:52 ` g4 at novadsp.com
2014-05-19 6:43 ` Thomas Petazzoni [this message]
2014-05-20 19:52 ` Arnout Vandecappelle
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=20140519084302.1a0259f3@free-electrons.com \
--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.