summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorSam Ravnborg <sam@neptun.(none)>2007-10-18 21:24:21 +0200
committerSam Ravnborg <sam@neptun.(none)>2007-10-18 23:17:06 +0200
commit50a8ec31c3a00594ceb7c5f1dcf2ecdaf6a5b847 (patch)
tree3f71eb176762d79d4ebfc751c864e77b99aec67a /scripts
parent6f67a00498abf8f0b29c2cecfce188c70be309d0 (diff)
downloadop-kernel-dev-50a8ec31c3a00594ceb7c5f1dcf2ecdaf6a5b847.zip
op-kernel-dev-50a8ec31c3a00594ceb7c5f1dcf2ecdaf6a5b847.tar.gz
kbuild: disable depmod in cross-compile kernel build
When building embedded systems in a cross-compile environment and populating a target's file system image, we don't want to run the depmod on the host as we may be building for a completely different architecture. Since there's no such thing as a cross-depmod, we just disable running depmod in the cross-compile case and we just run depmod on the target at bootup. Inspired by patches from Christian, Armin and Deepak. This solves: http://bugzilla.kernel.org/show_bug.cgi?id=3881 Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Cc: Christian Bjølevik <nafallo@magicalforest.se> Cc: Deepak Saxena <dsaxena@mvista.com> and Cc: Armin Kuster <akuster@mvista.com>,
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud