* [Buildroot] kernel module dir following move to git
@ 2009-05-28 9:48 Will Wagner
2009-05-28 9:54 ` Will Wagner
0 siblings, 1 reply; 3+ messages in thread
From: Will Wagner @ 2009-05-28 9:48 UTC (permalink / raw)
To: buildroot
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
--
------------------------------------------------------------------------
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
------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] kernel module dir following move to git
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
0 siblings, 1 reply; 3+ messages in thread
From: Will Wagner @ 2009-05-28 9:54 UTC (permalink / raw)
To: buildroot
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
------------------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Buildroot] kernel module dir following move to git
2009-05-28 9:54 ` Will Wagner
@ 2009-05-28 11:18 ` Peter Korsgaard
0 siblings, 0 replies; 3+ messages in thread
From: Peter Korsgaard @ 2009-05-28 11:18 UTC (permalink / raw)
To: buildroot
>>>>> "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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-05-28 11:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox