public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: imx_v6_v7_defconfig needs lzop
Date: Thu, 5 Feb 2015 11:59:51 +0100	[thread overview]
Message-ID: <20150205105951.GU10842@pengutronix.de> (raw)
In-Reply-To: <CAMuHMdXJCh32e-+7rqNzCdbYX4AH3qfBQ3uZ_t9kC_8+1P1jJQ@mail.gmail.com>

Hello,

On Wed, Feb 04, 2015 at 03:41:45PM +0100, Geert Uytterhoeven wrote:
> On Wed, Feb 4, 2015 at 3:32 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > On Wed, Feb 4, 2015 at 12:21 PM, Geert Uytterhoeven
> > <geert@linux-m68k.org> wrote:
> >> http://kisskb.ellerman.id.au/kisskb/buildresult/12358024/
> >>
> >> /bin/sh: 1: lzop: not found
> >> cat: write error: Broken pipe
> >> make[3]: *** [arch/arm/boot/compressed/piggy.lzo] Error 1
> >
> > Isn't this error happening due to the lack of 'lzop' package installed
> > on the host machine?
> 
> Indeed.
I guess you don't want to ask for help or report a build breakage, but
question if it's sensible to let a defconfig depend on a host tool that
isn't commonly installed, right?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-02-05 10:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 14:21 imx_v6_v7_defconfig needs lzop Geert Uytterhoeven
2015-02-04 14:32 ` Fabio Estevam
2015-02-04 14:41   ` Geert Uytterhoeven
2015-02-05 10:59     ` Uwe Kleine-König [this message]
2015-02-05 11:12       ` Geert Uytterhoeven
2015-02-12  6:58         ` Stephen Rothwell
2015-02-12 18:52           ` Geert Uytterhoeven
2015-02-05 21:28   ` Stefan Agner

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=20150205105951.GU10842@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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