[Buildroot] Trying to configure the kernel

[Buildroot] Trying to configure the kernel

[Ormund Williams]

Hi everyone,

I downloaded the latest stable release, 2013.02, then ran 'make
menuconfig' then 'make' and it built without errors, then I wanted to
build the kernel so did 'make menuconfig' again and turned on the kernel
but neither of the choices 'defconfig' or 'custom config file' works
when I try to run 'make linux-menuconfig' I get one of the 2 errors
bellow:
  linux/linux.mk:321: *** No kernel defconfig name specified, check your BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.
or
  linux/linux.mk:327: *** No kernel configuration file specified, check your BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE setting.  Stop.

I feel like I've missed a step. Have I?

-- 
Ormund

[Buildroot] Trying to configure the kernel

[Thomas Petazzoni]

Dear Ormund Williams,

On Fri, 05 Apr 2013 16:06:06 -0400, Ormund Williams wrote:

> I downloaded the latest stable release, 2013.02, then ran 'make
> menuconfig' then 'make' and it built without errors, then I wanted to
> build the kernel so did 'make menuconfig' again and turned on the kernel
> but neither of the choices 'defconfig' or 'custom config file' works
> when I try to run 'make linux-menuconfig' I get one of the 2 errors
> bellow:
>   linux/linux.mk:321: *** No kernel defconfig name specified, check your BR2_LINUX_KERNEL_DEFCONFIG setting.  Stop.
> or
>   linux/linux.mk:327: *** No kernel configuration file specified, check your BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE setting.  Stop.
> 
> I feel like I've missed a step. Have I?

Well, I thought the messages were clear enough, but it seems they are
not.

 * If you chose to use a defconfig, then you must give the name of a
   defconfig file, using the BR2_LINUX_KERNEL_DEFCONFIG option.

 * If you chose to use a kernel configuration file, then you must give
   the path to this file in BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE.

In short, there is no way to just "start the kernel configuration", you
must first give it an initial existing configuration. Maybe we should
add an option "Just run the kernel configuration with whatever defaults
for the current architecture", so that you don't have to give an
existing defconfig or an existing kernel configuration file.

What architecture and hardware are you targeting? If you're targeting
x86, then you can set BR2_LINUX_KERNEL_DEFCONFIG to 'i386', if you're
targeting x86-64, then you can set BR2_LINUX_KERNEL_DEFCONFIG to
'x86_64'. If you're targeting ARM, then you should look in the kernel
sources which defconfig in arch/arm/configs/ matches your hardware.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] Trying to configure the kernel

[Ormund Williams]

On Sat, 2013-04-06 at 15:26 +0200, Thomas Petazzoni wrote:
> Well, I thought the messages were clear enough, but it seems they are
> not.
> 
>  * If you chose to use a defconfig, then you must give the name of a
>    defconfig file, using the BR2_LINUX_KERNEL_DEFCONFIG option.
> 
>  * If you chose to use a kernel configuration file, then you must give
>    the path to this file in BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE.
> 
> In short, there is no way to just "start the kernel configuration", you
> must first give it an initial existing configuration. Maybe we should
> add an option "Just run the kernel configuration with whatever defaults
> for the current architecture", so that you don't have to give an
> existing defconfig or an existing kernel configuration file.
> 
A default would be great but just adding the above paragraph to section
3.3.4 of the manual would be helpful.

> What architecture and hardware are you targeting? If you're targeting
> x86, then you can set BR2_LINUX_KERNEL_DEFCONFIG to 'i386', if you're
> targeting x86-64, then you can set BR2_LINUX_KERNEL_DEFCONFIG to
> 'x86_64'. If you're targeting ARM, then you should look in the kernel
> sources which defconfig in arch/arm/configs/ matches your hardware.
> 
An ARM board that I'm currently designing.  I wanted to explore a
complete system and the make files used to build it.

Regards,


-- 
Ormund

[Buildroot] Trying to configure the kernel

[Arnout Vandecappelle]

On 06/04/13 15:26, Thomas Petazzoni wrote:
> In short, there is no way to just "start the kernel configuration", you
> must first give it an initial existing configuration. Maybe we should
> add an option "Just run the kernel configuration with whatever defaults
> for the current architecture", so that you don't have to give an
> existing defconfig or an existing kernel configuration file.

  I posted a patch to do exactly that a long time ago. Don't have 
internet access at the moment so can't look up the patchwork reference.

  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

[Buildroot] Trying to configure the kernel

[Thomas Petazzoni]

Dear Arnout Vandecappelle,

On Tue, 09 Apr 2013 07:46:38 +0200, Arnout Vandecappelle wrote:
> On 06/04/13 15:26, Thomas Petazzoni wrote:
> > In short, there is no way to just "start the kernel configuration",
> > you must first give it an initial existing configuration. Maybe we
> > should add an option "Just run the kernel configuration with
> > whatever defaults for the current architecture", so that you don't
> > have to give an existing defconfig or an existing kernel
> > configuration file.
> 
>   I posted a patch to do exactly that a long time ago. Don't have 
> internet access at the moment so can't look up the patchwork
> reference.

I think this is something we should commit, probably as part of a
rework of how linux-menuconfig/barebox-menuconfig and al. work, as per
our discussions at the FOSDEM Buildroot Developers meeting.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com