Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] Added linux drivers backports project
Date: Sun, 19 Apr 2015 23:19:41 +0200	[thread overview]
Message-ID: <20150419211940.GD12734@t61> (raw)
In-Reply-To: <20150419190321.19200e70@free-electrons.com>

Thank you Thomas for testing, thanks a lot to all of you for the comments.
Sorry that I didn't test it well, I didn't expect to be able to use 'make menuconfig'
without calling make or 'make linux-backports' before.

I send v5 where I integrated Thomass' changes. So is it blind alley (if you don't want to
tweak custom requirements), and I should try to add it as linux extension using
integration strategy?

Petr
> Dear Yann E. MORIN,

> On Sun, 19 Apr 2015 18:28:39 +0200, Yann E. MORIN wrote:

> > Well, I would not be very happy with that, since that would make the
> > following use-case a real pain:

> >     $ make foo_defconfig
> >     $ make linux-menuconfig

> > Currently, all it needs is the linux kernel to be extracted and patched,
> > and none of its depedencies to be built. Otherwise, it would require the
> > toolchain to be built, plus a sh.tload of other stuff (lzo, for one, and
> > all its own dependencies).

> We could remove the mandatory host-lzo dependency from the linux
> package, by adding an option for that. Remember the recent patches also
> adding host-xz to the dependencies of linux, which I rejected?

> This would leave host-kmod as the only dependency of the linux package
> I believe. But well host-kmod as AUTORECONF = YES, so it pulls a whole
> bunch of crap.

> I agree that being able to do "make <foo>-menuconfig" without waiting
> too long is really a great feature.

> Thomas

  reply	other threads:[~2015-04-19 21:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 23:01 [Buildroot] [PATCH v4 1/1] Added linux drivers backports project Petr Vorel
2015-04-19  9:03 ` Thomas Petazzoni
2015-04-19 13:15   ` Yann E. MORIN
2015-04-19 16:20   ` Arnout Vandecappelle
2015-04-19 16:28     ` Yann E. MORIN
2015-04-19 17:03       ` Thomas Petazzoni
2015-04-19 21:19         ` Petr Vorel [this message]
2015-04-19 21:28           ` Yann E. MORIN
2015-04-20 20:42         ` Arnout Vandecappelle
2015-04-20 20:56           ` Thomas Petazzoni
2015-04-20 21:08             ` Arnout Vandecappelle
2015-04-20 21:00           ` Yann E. MORIN

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=20150419211940.GD12734@t61 \
    --to=petr.vorel@gmail.com \
    --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