Re: Error compiling barebox on fido

[Nikolay Dimitrov <picmaster@mail.bg>]

Hi György,

On 06/22/2015 05:38 PM, György Kövesdi wrote:
> Hi Nikolay,
>
> I found something. As you suggested, i created a small test recipe.
> It was succeeded on master and fido checkouts too. I found that it
> uses gcc this way:
>
> arm-poky-linux-gnueabi-gcc  -march=armv7-a -marm  -mthumb-interwork
> -mfloat-abi=hard -mfpu=neon -mtune=cortex-a9
> --sysroot=/home/kgy/work/Yocto/MX6-master/build/tmp/sysroots/embedsky-e9
>
>
-O2 -pipe -g -feliminate-unused-debug-types  -Wl,-O1
> -Wl,--hash-style=gnu -Wl,--as-needed  x.c   -o x
>
> The first some options passed to gcc fixes my problem:
>
> -march=armv7-a -marm  -mthumb-interwork -mfloat-abi=hard -mfpu=neon
> -mtune=cortex-a9
> --sysroot=/home/kgy/work/Yocto/MX6-master/build/tmp/sysroots/embedsky-e9
>
>
>and the others are come from CFLAGS and LDFLAGS variables. If i
> could pass these to barebox compilation, then i could fix it. My
> problem is that i could not find the variable where these options
> are stored.

I would recommend you not to try to force the Yocto build system to
work-around component quirks, but to try to fix the component makefile
to work properly in a cross-compile environment. Assuming that barebox
and U-Boot have somewhat similar build scripts, it should be to see how
things work in U-Boot and do it the same way for barebox (U-Boot builds
*perfectly* in every environment I had so far, including native armhf
builds).

The other thing I could recommend is to re-evaluate your motivation to
build barebox and to try instead using U-Boot for the same purpose
(unless barebox is a hard-requirement for your project). If you feel
like learning more about Makefiles makes you happy - that's cool, but
if you're hard pressed against a wall (e.g. deadlines) you should look
at lower risk solution.

[snip]

Regards,
Nikolay