Bug 573

Summary:	BR2_DEFAULT_KERNEL_HEADERS is undefined with external toolchain
Product:	buildroot	Reporter:	Phil <n0-1>
Component:	Other	Assignee:	unassigned
Status:	RESOLVED INVALID
Severity:	normal	CC:	buildroot
Priority:	P5
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	Linux
Host:		Target:
Build:
Attachments:	Log of the make-output when compiling The buildroot config triggering the described behaviour.

Description Phil 2009-08-19 13:30:39 UTC

Hi,

I'm trying to compile using an external binary toolchain (installed via crossdev in Gentoo), but when BR2_TOOLCHAIN_EXTERNAL is active, toolchain/kernel-headers/Config.in is not being included. The later leads to an undefined BR2_DEFAULT_KERNEL_HEADERS, which again makes buildroot try to download http://www.kernel.org/pub//linux/kernel/v2.6/linux-..tar.bz2.

Greetings, Phil

Comment 1 Phil 2009-08-19 13:46:26 UTC

This happens with the git tree from git://repo.or.cz/buildroot.git, btw.

Comment 2 Thomas Petazzoni 2009-08-19 21:24:14 UTC

At what step does it fail ? Could you post your build log and Buildroot configuration file ?

Comment 3 Thomas Petazzoni 2009-08-19 21:32:09 UTC

BTW, this bugzilla is for the official Buildroot version, that you can find at http://www.buildroot.org, or in its Git repo at http://git.buildroot.org.

But anyway, I think that the issue you're having might be present in the official Buildroot version as well.

Comment 4 Phil 2009-08-20 09:22:20 UTC

Created attachment 607 [details]
Log of the make-output when compiling

Comment 5 Phil 2009-08-20 09:23:53 UTC

Created attachment 609 [details]
The buildroot config triggering the described behaviour.

Comment 6 Peter Korsgaard 2009-08-26 20:58:14 UTC

This shouldn't happend with the official BR tree, as we don't display the BR2_KERNEL_LINUX option when an external toolchain is used.

Is there any specific reason why you are using Bernhard's tree instead of the official one?

Comment 7 Phil 2009-08-26 22:11:59 UTC

(In reply to comment #6)
> This shouldn't happend with the official BR tree, as we don't display the
> BR2_KERNEL_LINUX option when an external toolchain is used.

Indeed. The official tree simply skips kernel compilation or, when BR2_KERNEL_LINUX_ADVANCED
has been specified, allows specification of the desired linux version, too.

> Is there any specific reason why you are using Bernhard's tree instead of the
> official one?

I was searching for glibc-based toolchain support, which sadly occurs to be not complete in Bernhard's
tree, too. I didn't know of the external toolchain support option in busybox, so I just tried that on
occasion.

Filing this report to the wrong site was just because of me having forgotten that I didn't use the official
sources. So, thanks for your patience and sorry for the inconvenience.

Comment 8 Bernhard Reutner-Fischer 2009-08-27 13:44:47 UTC

(In reply to comment #7)
> (In reply to comment #6)
> > This shouldn't happend with the official BR tree, as we don't display the
> > BR2_KERNEL_LINUX option when an external toolchain is used.
> 
> Indeed. The official tree simply skips kernel compilation or, when
> BR2_KERNEL_LINUX_ADVANCED
> has been specified, allows specification of the desired linux version, too.

My tree does not support external toolchains, just FYI.
> 
> > Is there any specific reason why you are using Bernhard's tree instead of the
> > official one?
> 
> I was searching for glibc-based toolchain support, which sadly occurs to be not
> complete in Bernhard's

I only added stub-functionality for the buildroot parts to show people how
i would implement it cleanly.

Let me note that if you want glibc and an external toolchain then i personally would use gentoo or some such.