All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 2/2] linux: Add support for specifying a custom directory
Date: Mon, 30 Oct 2017 23:32:46 +0100	[thread overview]
Message-ID: <20171030223246.GC3150@scaer> (raw)
In-Reply-To: <d7e6d392-b7d1-7bdc-5048-d88fc6f0ab79@gmail.com>

Florian, All,

On 2017-10-29 20:27 -0700, Florian Fainelli spake thusly:
> Le 10/29/17 ? 11:12, Yann E. MORIN a ?crit?:
> > On 2017-10-29 10:26 -0700, Florian Fainelli spake thusly:
> >> package/linux-headers/linux-headers.mk:134: *** LINUX_HEADERS_SITE
> >> cannot be empty when LINUX_HEADERS_SOURCE is not.  Stop.
> >> Makefile:79: recipe for target '_all' failed
> >> make: *** [_all] Error 2
> >> zsh: exit 2     make
> > 
> > Hmm... Even when you keep the kernel version to its default value?
> 
> That was also because I had set the "custom kernel version" to an empty
> string, which could have indicated "don't care" but was still needed.
> This is also probably fine to set to anything once you set your kernel
> headers to a particular version.
> 
> It seems like we should not prompted any kernel version in case since we
> use a local kernel directory, or, the version should be derived directly
> from the kernel  directory so it does not have to be manually specified
> at all but that's a tad more complicated.

But in truth, the override-srcdir mechanism is just that: an _override_
of the configured values, to be used only for development.

So, the premise is that you start off from a "known" configuration, and
override just that one or two packages you are working on.

> Thanks for your help, it's been pretty interesting to use another build
> system thus far :)

I was rather surprised (in a good sense!) to see you here, yes. Trying
the Dark Side of the Force, are we? ;-]

See ya!

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2017-10-30 22:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-29  2:06 [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory Florian Fainelli
2017-10-29  2:06 ` [Buildroot] [RFC 1/2] pkg-generic: Don't check for trailing slashes for local method Florian Fainelli
2017-10-29  2:06 ` [Buildroot] [RFC 2/2] linux: Add support for specifying a custom directory Florian Fainelli
2017-10-29  7:26   ` Yann E. MORIN
2017-10-29  9:12     ` Thomas Petazzoni
2017-10-29 17:26       ` Florian Fainelli
2017-10-29 18:12         ` Yann E. MORIN
2017-10-30  3:27           ` Florian Fainelli
2017-10-30 22:32             ` Yann E. MORIN [this message]
2017-11-03  5:03               ` Florian Fainelli
2017-11-03  7:04                 ` Yann E. MORIN
2017-11-03  9:23                 ` Thomas Petazzoni
2017-10-29  7:33 ` [Buildroot] [RFC 0/2] Add support for specifying a custom kernel directory Yann E. MORIN
2017-10-29 17:10   ` Florian Fainelli

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=20171030223246.GC3150@scaer \
    --to=yann.morin.1998@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.