All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] kernel module dir following move to git
Date: Thu, 28 May 2009 10:54:39 +0100	[thread overview]
Message-ID: <4A1E5F5F.1040600@carallon.com> (raw)
In-Reply-To: <4A1E5E07.2000403@carallon.com>

Will Wagner wrote:
> Hello All,
> 
> Following the move to git I am seeing the kernel modules being built to 
> a different directory. The code expects modules to be built in 
> $(TARGET_DIR)/lib/modules/$(LINUX26_VERSION_PROBED)
> 
> LINUX26_VERSION_PROBED is set with
> LINUX26_VERSION_PROBED = `$(MAKE) $(LINUX26_MAKE_FLAGS) -C 
> $(LINUX26_DIR) -s kernelrelease`
> 
> Since the move to git the kernel has changed what it reports with 
> kernelrelease to $(VERSION)-g7664a62a-dirty. Presumably the kernel is 
> spotting that buildroot came from a git repository and is appending info 
> about the checkout?
> 
> Any suggestion on how to prevent this happening?
> 
> Will

Think I have worked this out now. It is because I have CONFIG_LOCALVERSION_AUTO=y set in 
my kernel config file. Still seems odd that it is finding buildroot git rather than a 
kernel git but think I can fix it now.

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2009-05-28  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  9:48 [Buildroot] kernel module dir following move to git Will Wagner
2009-05-28  9:54 ` Will Wagner [this message]
2009-05-28 11:18   ` Peter Korsgaard

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=4A1E5F5F.1040600@carallon.com \
    --to=will_wagner@carallon.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 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.