Sign up ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

I'm using Buildroot to create a Linux system for the NXP LPC3250 microcontroller.

There are patches to the vanilla kernel to make it compatible with the LPC3250 controller:

I would like to build Kernel, but my Buildroot system always makes a 2.6.34 kernel!

I have set the GIT repository to point to enter image description here

You can see that I've specified a Defconfig for the system I'm building for: ea3250

I've edited my ea3250 defconfig as well: enter image description here

After doing a make clean all to clean everything and rebuild the system, looking inside the output kernel image shows it is still building 2.6.34: enter image description here

What am I doing wrong? Is there another menu I need to configure to get it to build

share|improve this question
What buildroot version did you install? – jippie Dec 21 '12 at 19:30
I had some unstable version, I guess. Didn't really pay attention, just pulled down a copy from CVS. I ended up getting version 2012.11 and everything builds fine! – dext0rb Dec 22 '12 at 16:33

1 Answer 1

up vote 1 down vote accepted

Not really an answer, but it doesn't fit a comment due to formatting:

What happens when you do the following:

cd /home/user/projects/buildroot
make clean
make distclean

Copy target system's /proc/config.gz to host /tmp Then take the existing kernel config and translates it to the new kernel version by answering the various question:

gunzip -c /tmp/config.gz ./.config
make oldconfig     

Do some sanity checking on version:

make menuconfig

Build the binaries


Check version of the kernel image built, don't load the kernel image in nano to search for a string, that is bad practice.

file ./buildroot/output/images/*
share|improve this answer
Thanks, your comment on version helped me, so I will just accept this. :) – dext0rb Dec 22 '12 at 16:34

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.