From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] kernel module dir following move to git
Date: Thu, 28 May 2009 13:18:56 +0200 [thread overview]
Message-ID: <871vq98ogv.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4A1E5F5F.1040600@carallon.com> (Will Wagner's message of "Thu\, 28 May 2009 10\:54\:39 +0100")
>>>>> "Will" == Will Wagner <will_wagner@carallon.com> writes:
Hi,
Will> Think I have worked this out now. It is because I have
Will> CONFIG_LOCALVERSION_AUTO=y set in my kernel config file. Still seems
Will> odd that it is finding buildroot git rather than a kernel git but
Will> think I can fix it now.
Well, it's because the kernel's scripts/setlocalversion checks if your
kernel is in a git repo (which it technically is if you build in the
tree and have buildroot from git).
Another workaround is to simply build out of tree (make O=<somewhere>)
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-05-28 11:18 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
2009-05-28 11:18 ` 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=871vq98ogv.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