So I had a look at the Kconfig file and realised it isn't a kernel
config. If I add
config BT
def_bool y
under the "# some hacks ..." section, I can enable BT drivers in
backports in the menuconfig. So if a kconfig depends on an external
config, there is no way to feed in a kernel config to backports? you
list external config under "# some hacks ..." section?
Jon
On 13-08-07 03:55 PM, Jonathan Bagg wrote:
Hello,
I am cross compiling backports successful using "alldefconfig". I
would like use menuconfig and have conf read in options from my kernel
instead of the default. (CONFIG_BT is not enabled in the default and
I want to enable BT drivers in backports). It looks like kconf/conf
program is loading a kernel config from the root of backports called
Kconfig. When I replace this file with my kernel config (from
2.6.35-3) I get many....
Kconfig:1967: syntax error
Kconfig:1966: unknown statement "CONFIG_CRC_ITU_T"
Kconfig:1967: unknown statement "CONFIG_CRC32"
Kconfig:1971: syntax error
Kconfig:1970: unknown statement "CONFIG_ZLIB_INFLATE"
Kconfig:1971: unknown statement "CONFIG_ZLIB_DEFLATE"
Kconfig:1972: unknown statement "CONFIG_LZO_COMPRESS"
Kconfig:1973: unknown statement "CONFIG_LZO_DECOMPRESS"
Kconfig:1974: unknown statement "CONFIG_GENERIC_ALLOCATOR"
Kconfig:1975: unknown statement "CONFIG_HAS_IOMEM"
Kconfig:1976: unknown statement "CONFIG_HAS_IOPORT"
Kconfig:1977: unknown statement "CONFIG_HAS_DMA"
Kconfig:1978: unknown statement "CONFIG_NLATTR"
make[1]: *** [menuconfig] Error 1
make: *** [menuconfig] Error 2
What is the right way to do this? I could add CONFIG_BT=y to the
default Kconfig file, but that seems hackish.
Jon
--
To unsubscribe from this list: send the line "unsubscribe backports" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
