From: Cyril HAENEL <chaenel@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Problem with LZO package in ARM configuration, need help to solve the problem
Date: Mon, 04 May 2009 15:19:36 +0200 [thread overview]
Message-ID: <49FEEB68.30800@free.fr> (raw)
In-Reply-To: <87y6td59d7.fsf@macbook.be.48ers.dk>
> Hi,
>
> Cyril> In fact when we activate jffs2 filesystem output, lzo must be compiled
> Cyril> for the host, thus why does it first try to use arm-linux-g++ !? It's
> Cyril> why I am the only one to have this problem since some week, because I
> Cyril> am the only one to have a arm toolchain installed on my computer !!
>
> Cyril> There is surely a bug to fix somewhere, but I don't know where !?
>
> Hmm, are you sure this is lzo-host compilation, and not lzo for the
> target?
>
>
I think lzo is compiled in the 2 configuration, for the host and for the
target.
Because when we activate the jffs2 filesystem output, I think buildroot
need mkfs.jffs2 and I think mkfs.jffs2 needs lzo.
But because mtd-utils (and also mkfs.jffs2) is provided in the target, I
think lzo is also compiled for the target.
--
Cyril Haenel
Registered Linux User #332632
next prev parent reply other threads:[~2009-05-04 13:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 10:39 [Buildroot] Problem with LZO package in ARM configuration, need help to solve the problem Cyril HAENEL
2009-05-04 11:29 ` Peter Korsgaard
2009-05-04 12:02 ` Cyril HAENEL
2009-05-04 12:40 ` Peter Korsgaard
2009-05-04 13:19 ` Cyril HAENEL [this message]
2009-05-04 13:37 ` Peter Korsgaard
2009-05-04 13:47 ` Cyril HAENEL
2009-05-04 14:02 ` Peter Korsgaard
2009-05-04 19:23 ` Peter Korsgaard
2009-05-04 19:52 ` Cyril HAENEL
2009-05-04 20:02 ` Peter Korsgaard
2009-05-04 20:05 ` Cyril HAENEL
2009-05-04 20:56 ` Cyril HAENEL
2009-05-04 11:30 ` Peter Korsgaard
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=49FEEB68.30800@free.fr \
--to=chaenel@free.fr \
--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.