From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] target/ubifs: fix compilation
Date: Mon, 20 Jul 2009 22:41:11 +0200 [thread overview]
Message-ID: <87hbx7dr4o.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090720122227.GW13236@buzzloop.caiaq.de> (Daniel Mack's message of "Mon\, 20 Jul 2009 14\:22\:27 +0200")
>>>>> "Daniel" == Daniel Mack <daniel@caiaq.de> writes:
Hi,
>> We'll also need to remove the 'depends on BROKEN' from Config.in
Daniel> Ok, done.
Great.
>> Why the backslashes? Wget here adds them to the URL:
>>
>> --2009-07-19 15:54:50--
>> http://git.infradead.org/mtd-utils.git?a=snapshot%5C;h=HEAD%5C;sf=tgz
>>
>> Which obviously fails.
Daniel> Argh. Done, thanks.
You're welcome.
>> We have MAKE1 for this.
Daniel> Fixed.
Ok.
>> The build breaks if you don't have liblzo development headers on the
>> build host:
Daniel> Hmm. What's your propose to check that? We can't depend on a
Daniel> config flag to be set, and building that liblzo-dev package
Daniel> manually doesn't seem to be the right ay to go either.
I propose we do exactly the same as we do for mkfs.jffs2 - E.G. use
the source selection / infrastructure from package/mtd/mtd-utils.mk
and build lzo for the host.
>> I really think the proper solution is to build the ubifs tools for the
>> host in the mtd-utils package like we do for mkfs.jffs2. Now, if the
>> mtd guys would put out a 1.3 release with all the new stuff it would
>> be even better.
Daniel> Which wouldn't solve the above problem, right? When there's a new
Daniel> release, I'll have another look at it :)
It would. Please have a look at how it is done for mkfs.jffs2. It's
currently a bit messy as we support 2 mtd-utils versions, which would
get solved if they would do a proper release with ubifs support.
>> Care to fix this and resend?
Daniel> See the patch below.
Thanks. I would still like to see the logic moving to package/mtd so
we don't duplicate the download step / selection logic here.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-07-20 20:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 11:39 [Buildroot] [PATCH 1/2] target/ubifs: fix compilation Daniel Mack
2009-06-03 11:39 ` [Buildroot] [PATCH 2/2] mtd-utils.git: fix targets Daniel Mack
2009-07-19 14:12 ` Peter Korsgaard
2009-07-20 11:25 ` Daniel Mack
2009-07-20 20:35 ` Peter Korsgaard
2009-07-20 21:03 ` Daniel Mack
2009-07-21 7:20 ` Peter Korsgaard
2009-07-29 17:20 ` Daniel Mack
2009-07-29 17:21 ` [Buildroot] [PATCH 1/2] e2fsprogs: factor out libuuid support Daniel Mack
2009-07-29 17:21 ` [Buildroot] [PATCH 2/2] mtd-utils.git: fix targets Daniel Mack
2009-08-05 19:47 ` Peter Korsgaard
2009-08-06 6:36 ` Daniel Mack
2009-08-06 7:58 ` Peter Korsgaard
2009-08-06 14:18 ` Daniel Mack
2009-08-06 15:03 ` Peter Korsgaard
2009-08-03 14:36 ` [Buildroot] [PATCH 1/2] e2fsprogs: factor out libuuid support Daniel Mack
2009-08-03 14:58 ` Thomas Petazzoni
2009-08-03 15:09 ` Daniel Mack
2009-08-03 20:48 ` Peter Korsgaard
2009-08-04 8:28 ` Daniel Mack
2009-08-05 11:47 ` Peter Korsgaard
2009-08-05 11:55 ` Daniel Mack
2009-08-05 13:52 ` Peter Korsgaard
2009-06-04 18:05 ` [Buildroot] [PATCH 1/2] target/ubifs: fix compilation Daniel Mack
2009-07-09 2:36 ` Paul Archer
2009-07-08 13:36 ` Daniel Mack
2009-07-08 14:18 ` Peter Korsgaard
2009-07-19 14:06 ` Peter Korsgaard
2009-07-20 12:22 ` Daniel Mack
2009-07-20 20:41 ` Peter Korsgaard [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=87hbx7dr4o.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox