From: Thomas Lundquist <lists@zelow.no>
To: buildroot@busybox.net
Subject: [Buildroot] LZMA in Buldroot.
Date: Thu, 5 Oct 2006 09:29:07 +0200 [thread overview]
Message-ID: <20061005072907.GA17753@zelow.no> (raw)
In-Reply-To: <20061004192606.GO17455@aon.at>
On Wed, Oct 04, 2006 at 09:26:07PM +0200, Bernhard Fischer wrote:
> >
> >as snipped out from the original lzma.mk, it's commented out which is
>
> Yes, i left it commented out. I had (and still have) trouble with c++
> due to an alleged bug with libtool on my ubuntu devel host.
I don't think you're the only one.
BTW; we should have uClibc++ available in buildroot. maybe I'll look at
it. (I haven't seen it, maybe I'm just blind?)
> Yes, i do and will add it too when i have verified and applied your
> diff. No timeframe on checking it, though.
>
> If you find the time to add the rule for the header(s), then i'll
> blindly apply your take 3 patch see if i need any additional changes.
> I don't know if anybody except me does currently use lzma via buildroot
> on their targets, so i do not feel obligued to be exceptionally stable
> at that end..
I use LZMA on my target (ARM9 but also floppyfw, which is intel and buld
using a devkit build by buildroot...), so you're not the only one :=)
BTW, I had lzma in buildroot some time ago but I've been using the SDK
directly and not the lzma-utils, which are a derivative. I have to admit
I am a bit unsure if lzma-utils is the right thing altho it's more
compatible option wise. (which could be fixed by a wrapper script).
but now we use lzma-utils and I am digressing alot.
You can, if you want to, wait with applying the patch and I'll verify it
myself (have to admit I havent after moving it from toolchain to package.)
and also add the lzma-headers back in.
Thomas.
next prev parent reply other threads:[~2006-10-05 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 17:30 [Buildroot] LZMA in Buldroot Thomas Lundquist
[not found] ` <20061004084732.GA15165@aon.at>
2006-10-04 14:40 ` Thomas Lundquist
2006-10-04 16:20 ` Bernhard Fischer
2006-10-04 16:37 ` Thomas Lundquist
2006-10-04 19:26 ` Bernhard Fischer
2006-10-05 7:29 ` Thomas Lundquist [this message]
2006-10-05 8:18 ` Bernhard Fischer
[not found] ` <20061006061248.GA2458@zelow.no>
[not found] ` <20061006081808.GA5591@aon.at>
[not found] ` <20061006105147.GA7047@zelow.no>
2006-11-04 19:21 ` Bernhard Fischer
2006-10-05 17:40 ` Rob Landley
2006-10-05 17:50 ` Bernhard Fischer
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=20061005072907.GA17753@zelow.no \
--to=lists@zelow.no \
--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.