[Buildroot] kernel build name

[Buildroot] kernel build name

[kakuschky at elbe-net.de]

Hi, I'm just starting to explorer buildroot. Just one question. Where are the parts of the build name coming from?

If I use make menuconfig my target is named "arm-unknown-linux-uclibcgnueabi" 

- arm is releated to the target platform
- linux o.k. it's a linux kernel I want to build
- eabi is the interface for embedded systems

The two I don't know are

- uclib is because I'm linking against GNU uclibc?
- unknown

Can somebody explain me where to set the part which is named "unknown" ?

Thanks & best regards Michael

[Buildroot] kernel build name

[kakuschky at elbe-net.de]

Hi, I'm just starting to explorer buildroot. Just one question. Where are the parts of the build name coming from?

If I use make menuconfig my target is named "arm-unknown-linux-uclibcgnueabi"

- arm is releated to the target platform
- linux o.k. it's a linux kernel I want to build
- eabi is the interface for embedded systems

The two I don't know are

- uclib is because I'm linking against GNU uclibc?
- unknown

Can somebody explain me where to set the part which is named "unknown" ?

Thanks & best regards Michael

[Buildroot] kernel build name

[Thomas Petazzoni]

Le Fri, 18 Nov 2011 20:01:35 +0100 (CET),
kakuschky at elbe-net.de a ?crit :

> If I use make menuconfig my target is named
> "arm-unknown-linux-uclibcgnueabi"

See http://sourceware.org/autobook/autobook/autobook_17.html for a
description of what this is.

This is *not* the "kernel build name" as the topic of your e-mail
suggests.

> - arm is releated to the target platform
> - linux o.k. it's a linux kernel I want to build
> - eabi is the interface for embedded systems

No, EABI on ARM is not really related to whether it's embedded or not.
Originally Linux on ARM systems have been using a Linux-specific ABI,
since ARM did not standardize any ABI. Since ABI is now called OABI
(probably for Old ABI or Original ABI or something alike). Later on,
ARM standardized an ABI, called EABI, which Linux now uses.

> - uclib is because I'm linking against GNU uclibc?

Yes.

> - unknown
> 
> Can somebody explain me where to set the part which is named
> "unknown" ?

That's the vendor/manufacturer part of the host tuple. You can put
whatever you want here, and Buildroot simply puts "unknown". We could
have put "br" or "buildroot", it would have worked just as fine.

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