[opensuse-kernel] How do I automate setting .config entries to "n"
Hello, I get this abort message such as this example when compiling a package which involves a kernel. and the .config file. It always ends in 'aborted' at the end like this. "Texas Instruments ADS7871 A/D converter (SENSORS_ADS7871) [N/m/y/?] (NEW) aborted!" or "Compile Remote Controller keymap modules (RC_MAP) [M/n/?] (NEW) aborted!" It falls over on a diferrent line in the .config each time I submit a rebuild. This is a slow process doing one item at a time. Question. Is is possible to automatically set it so that (NEW) entries are set and stored in the .config like this CONFIG_{itemname}=n Thanks Glenn - So far its been a case of append the value to the .config eg CONFIG_RC_MAP=n - Then submit the build again, wait and encocounter the error on another .config entry. Here is a small list I struck so far. I added them in one at a time to the .config and submit another build. Its a slow process. CONFIG_CROSS_COMPILE="" CONFIG_COMPACTION=n CONFIG_ACPI_HED=n CONFIG_MFD_WM8994=n CONFIG_PCCARD_NONSTATIC=n CONFIG_ACPI_APEI=n CONFIG_INTEL_IDLE=n CONFIG_PCI_CNB20LE_QUIRK=n CONFIG_IP_MROUTE_MULTIPLE_TABLES=n CONFIG_NETFILTER_XT_TARGET_TEE=n CONFIG_NET_SCTPPROBE=n -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
I get this abort message such as this example when compiling a package which involves a kernel. and the .config file.
It always ends in 'aborted' at the end like this. "Texas Instruments ADS7871 A/D converter (SENSORS_ADS7871) [N/m/y/?] (NEW) aborted!" or "Compile Remote Controller keymap modules (RC_MAP) [M/n/?] (NEW) aborted!"
It falls over on a diferrent line in the .config each time I submit a rebuild. This is a slow process doing one item at a time.
Question. Is is possible to automatically set it so that (NEW) entries are set and stored in the .config like this CONFIG_{itemname}=n You should run scripts/run_oldconfig.sh prior to submitting kernel to Build Service to get .config updated appropriately. You can also tell the
Hello, On Fri 01-10-10 00:27:46, doiggl@velocitynet.com.au wrote: script how it should handle new config options and similar... Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Hello,
On Fri 01-10-10 00:27:46, doiggl@velocitynet.com.au wrote:
I get this abort message such as this example when compiling a package which involves a kernel. and the .config file.
It always ends in 'aborted' at the end like this.
"Texas Instruments ADS7871 A/D converter (SENSORS_ADS7871) [N/m/y/?] (NEW) aborted!"
or
"Compile Remote Controller keymap modules (RC_MAP) [M/n/?] (NEW) aborted!"
It falls over on a diferrent line in the .config each time I submit a rebuild. This is a slow process doing one item at a time.
Question. Is is possible to automatically set it so that (NEW) entries are set and stored in the .config like this CONFIG_{itemname}=n
You should run scripts/run_oldconfig.sh prior to submitting kernel to Build Service to get .config updated appropriately. You can also tell
On Thu, 30 Sep 2010 16:48:27 +0200, Jan Kara <jack@suse.cz> wrote: the
script how it should handle new config options and similar...
Honza-- Jan Kara <jack@suse.cz> SUSE Labs, CR
Thanks for the info. Have you an example on running the oldconfig in obs Or How to tell the script how it should handle new config options and answer 'n' to the questions. - The current options in $MAKE_ARGS are set to '-C /usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-2.6.35 O=/usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-obj' This is the bit of code which the problems are located on. The full listing at [1] make prepare $MAKE_ARGS + make prepare -C /usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-2.6.35 O=/usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-obj make: Entering directory `/usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-2.6.35 [1] https://build.opensuse.org/package/view_file?file=kernel-vanilla.spec&pa... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Hello,
On Fri 01-10-10 00:27:46, doiggl@velocitynet.com.au wrote:
I get this abort message such as this example when compiling a package which involves a kernel. and the .config file.
It always ends in 'aborted' at the end like this.
"Texas Instruments ADS7871 A/D converter (SENSORS_ADS7871) [N/m/y/?] (NEW) aborted!"
or
"Compile Remote Controller keymap modules (RC_MAP) [M/n/?] (NEW) aborted!"
It falls over on a diferrent line in the .config each time I submit a rebuild. This is a slow process doing one item at a time.
Question. Is is possible to automatically set it so that (NEW) entries are set and stored in the .config like this CONFIG_{itemname}=n
You should run scripts/run_oldconfig.sh prior to submitting kernel to Build Service to get .config updated appropriately. You can also tell
On Thu, 30 Sep 2010 16:48:27 +0200, Jan Kara <jack@suse.cz> wrote: the
script how it should handle new config options and similar...
Honza-- Jan Kara <jack@suse.cz> SUSE Labs, CR
Thanks for the info. Have you an example on running the oldconfig in obs No. We run it manually after we update the kernel. I guess you can do it
On Fri 01-10-10 01:39:04, doiggl@velocitynet.com.au wrote: the same way - or do you perform automatic kernel updates?
Or How to tell the script how it should handle new config options and answer 'n' to the questions. Please read the help text before you ask... It's -nco-n option.
- The current options in $MAKE_ARGS are set to '-C /usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-2.6.35 O=/usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-obj'
This is the bit of code which the problems are located on. The full listing at [1]
make prepare $MAKE_ARGS
+ make prepare -C /usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-2.6.35 O=/usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-obj make: Entering directory `/usr/src/packages/BUILD/kernel-vanilla-2.6.34.7/linux-2.6.35
[1] https://build.opensuse.org/package/view_file?file=kernel-vanilla.spec&pa... Actually, looking into the spec file, it already has a built in way to handle undefined config options - search for TOLERATE-UNKNOWN-NEW-CONFIG-OPTIONS. You'd just need to change that to use 'no' instead of 'yes'.
Honza -- Jan Kara <jack@suse.cz> SUSE Labs, CR -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Hello. Does this kernel rpm build look ok ? Its a vanilla kernel with the reiser4 patch applied. This is my first success at building a patched kernel with reiser4 patch. Its been a interesting learning experience. The project is here -> https://build.opensuse.org/package/show?package=kernel-reiser4&project=h... The built rpms are here -> https://build.opensuse.org/package/binaries?package=kernel-reiser4&proje... The log of the build is here {x86_64} as an example. [Its a long build log ] -> https://build.opensuse.org/package/rawlog?arch=x86_64&package=kernel-rei... The .spec used file is here -> https://build.opensuse.org/package/view_file?file=kernel-reiser4.spec&pa... Thanks to everyone for compilation advice. It looks like obs built the rpms. Cheers Glenn -- -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (2)
-
doiggl＠velocitynet.com.au -
Jan Kara