From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Tim Bird <tim.bird@am.sony.com>,
lasse.collin@tukaani.org, glp@openwrt.org,
linux-embedded@vger.kernel.org
Subject: Re: LZMA inclusion
Date: Wed, 3 Dec 2008 22:28:12 +0100 [thread overview]
Message-ID: <20081203212812.GG8563@mx.loc> (raw)
In-Reply-To: <20081203211617.GB7255@uranus.ravnborg.org>
On Wed, Dec 03, 2008 at 10:16:17PM +0100, Sam Ravnborg wrote:
>>
>> PS: Not sure if you, Sam, are the right person who cares for it, but
>> i think that the help-text and actual accepted arguments of
>> scripts/kconfig/lxdialog/check-lxdialog.sh are out of sync.
>I queued up the following:
Thanks alot.
>
>> PPS: I did not verify if this is still the case, but I have this
>> comment as a reminder for a small issue with "archprepare" versus
>> headers_install, fwiw. It would be very handy if i could fuse those
>> two into a simple "make ... archprepare headers_install":
>
>Which architectures needs this archprepare?
At least cris tripped this IIRC, at least before or around the time
when cris's subarch handling was fixed (the asm-cris/arch-v10 vs.
arch-v32 linking issue).
>It would be good to get rid of the dependency.
nod
>PS. I consider archprepare an internal target.
>If some preparation is needed the recommended target is 'prepare'.
>The day no targets has any special things they need to do archprepare will die.
The proper solution would perhaps be to do have prepare or archprepare
as a prerequisite of headers_install as long as those are needed, i guess.
I as a user don't want to be bothered with this mere implementation detail
in the first place, yes.
next prev parent reply other threads:[~2008-12-03 21:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 7:06 LZMA inclusion Gregers Petersen
2008-12-03 19:36 ` Tim Bird
2008-12-03 19:50 ` Florian Fainelli
2008-12-03 19:58 ` Bernhard Reutner-Fischer
2008-12-03 20:20 ` Sam Ravnborg
2008-12-03 20:45 ` Bernhard Reutner-Fischer
2008-12-03 21:16 ` Sam Ravnborg
2008-12-03 21:28 ` Bernhard Reutner-Fischer [this message]
2008-12-03 21:43 ` Sam Ravnborg
2008-12-03 21:48 ` Lasse Collin
2008-12-04 21:46 ` Jean-Christophe PLAGNIOL-VILLARD
2008-12-05 8:31 ` Geert Uytterhoeven
2008-12-06 21:56 ` Lasse Collin
2008-12-07 16:01 ` Jörn Engel
2008-12-07 23:32 ` Phillip Lougher
2008-12-08 13:46 ` Jamie Lokier
2008-12-08 18:23 ` Lasse Collin
2008-12-08 19:00 ` Phillip Lougher
2008-12-09 10:20 ` Lasse Collin
2008-12-09 10:37 ` Geert Uytterhoeven
2008-12-16 8:55 ` Lasse Collin
2008-12-08 20:17 ` Jörn Engel
2008-12-08 21:47 ` Phillip Lougher
2008-12-08 22:15 ` Jörn Engel
2008-12-03 20:09 ` Gregers Petersen
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=20081203212812.GG8563@mx.loc \
--to=rep.dot.nop@gmail.com \
--cc=glp@openwrt.org \
--cc=lasse.collin@tukaani.org \
--cc=linux-embedded@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tim.bird@am.sony.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 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.