Allow passing arbitrary build_subarch string.
svn path=/branches/kernel-image-2.6.11/; revision=3227
This commit is contained in:
parent
8107f6f1d9
commit
d9409bbd37
2
Makefile
2
Makefile
|
@ -59,7 +59,7 @@ ifdef added_patches
|
|||
kpkg_build_cmd += --added_patches $(subst @uver@,$(uver),$(added_patches))
|
||||
endif
|
||||
ifdef build_subarch
|
||||
kpkg_build_cmd += --subarch @flavour@
|
||||
kpkg_build_cmd += --subarch $(build_subarch)
|
||||
endif
|
||||
ifdef headers_subarch
|
||||
kpkg_headers_cmd += --subarch $(headers_subarch)
|
||||
|
|
12
README
12
README
|
@ -144,15 +144,13 @@ added_patches
|
|||
build_subarch
|
||||
|
||||
Setting this variable to non-empty value will cause an option
|
||||
--subarch to be added to 'build' and 'kernel-image' make-kpkg
|
||||
calls, followed by the flavour for which the kernel is built.
|
||||
In general, if you wish to add subarch support for your
|
||||
architecture, you should contact kernel-package maintainer
|
||||
--subarch $(build_subarch) added to 'build' and 'kernel-image'
|
||||
make-kpkg calls. In general, if you wish to add subarch support
|
||||
for your architecture, you should contact kernel-package maintainer
|
||||
to ensure that the flavour name correctly maps onto a kernel
|
||||
subarch name. Currently only mips and sparc are using this
|
||||
facility, and both of them should be fine. Typical usage:
|
||||
subarch name. Typical usage:
|
||||
|
||||
build_subarch := yes
|
||||
build_subarch := pmac
|
||||
|
||||
Note that the value of this variable is ignored.
|
||||
|
||||
|
|
Loading…
Reference in New Issue