From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: "U-Boot Version 2 (barebox)" <barebox@lists.infradead.org>
Subject: Re: after "git pull", building for beagle complains about missing "lzop"
Date: Fri, 16 Nov 2012 15:01:41 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.02.1211161501001.5043@oneiric> (raw)
In-Reply-To: <20121116195703.GC8327@game.jcrosoft.org>
On Fri, 16 Nov 2012, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 14:18 Fri 16 Nov , Robert P. J. Day wrote:
> >
> > after i "git pull"ed all the recent updates and tried to rebuild
> > from scratch for my beagle xm, the barebox build failed with:
> >
> > OBJCOPY barebox.bin
> > LDS arch/arm/pbl/zbarebox.lds
> > LZO arch/arm/pbl/piggy.lzo
> > /bin/sh: lzop: command not found
> > make[2]: *** [arch/arm/pbl/piggy.lzo] Error 1
> > make[1]: *** [zbarebox.bin] Error 2
> > make: *** [_all] Error 2
> > $
> >
> > i've never had "lzop" installed on this system before and never had
> > a complaint, so i'm assuming something about the default config has
> > changed that suddenly requires lzop, is that correct?
>
> yes because we now compress barebox
> as you see in the log LZO
yes, i did notice that shortly thereafter, should have perused the
log first before asking.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-11-16 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 19:18 Robert P. J. Day
2012-11-16 19:57 ` Jean-Christophe PLAGNIOL-VILLARD
2012-11-16 20:01 ` Robert P. J. Day [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=alpine.DEB.2.02.1211161501001.5043@oneiric \
--to=rpjday@crashcourse.ca \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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