Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 75564 - Why does linux-info.eclass require a built kernel source location for emerge'ing modules?
Summary: Why does linux-info.eclass require a built kernel source location for emerge'...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-24 10:21 UTC by Andy Wang
Modified: 2005-01-06 10:00 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Wang 2004-12-24 10:21:28 UTC
The linux-info.eclass has a check_kernel_built() function that checks for the existence of System.map.  linux-mod ebuilds use this function and bombs out if a fully built linux source tree exists.  Why is this required?  I always do a make clean of my linux source tree after building a kernel because it cleans up alot of disk space.

From my understanding, kernel modules just need a properly prepared kernel tree, not a fully built kernel tree with the System.map file.  Am I wrong?

Up until recently, I've never needed a fully built kernel tree to build modules.
Comment 1 Andy Wang 2004-12-24 10:22:58 UTC
FYI, here's a comment from the kernel Makefile regarding make clean:

# make clean     Delete most generated files
#                Leave enough to build external modules
Comment 2 John Mylchreest (RETIRED) gentoo-dev 2004-12-29 03:12:37 UTC
in many cases your right.
the system.map check is a little crude and needs checking.
CC'ing me in.
Comment 3 John Mylchreest (RETIRED) gentoo-dev 2005-01-06 10:00:11 UTC
mostly fixed in cvs. should now work for you.