How to add the standard library to arm-fslc-linux-gnueabi-gcc in yocto meta-toolchain fatal error: stdio.h: No such file or directory

How to add the standard library to arm-fslc-linux-gnueabi-gcc in yocto meta-toolchain fatal error: stdio.h: No such file or directory

[Mattis Asp]

[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]

Just posted the question here
<https://stackoverflow.com/questions/49777448/how-to-add-the-standard-library-to-arm-fslc-linux-gnueabi-gcc-in-yocto-meta-tool>.
It's better formatting.

**Question**: How to add the standard library to arm-fslc-linux-gnueabi-gcc

**Background**:
I just had bitbake compile the `meta-toolchain` in the Yocto project.
I then installed the resulting SDK-toolchain

> $
> ./build/tmp/deploy/sdk/
fslc-framebuffer-glibc-x86_64-meta-toolchain-armv7at2hf-neon-toolchain-2.4.2.sh

which then installed the SDK-toolchain in /opt/fslc-framebuffer/2.4.2/

I can then easily run the executable to source the correct environment
variables.

> $
>
./opt/fslc-framebuffer/2.4.2/environment-setup-armv7at2hf-neon-fslc-linux-gnueabi
I now have access to the cross-compiler arm-fslc-linux-gnueabi-gcc
**So far so good...**

I then downloaded the barebone SDK from NXP [here
<https://community.nxp.com/servlet/JiveServlet/download/995668-1-423967/iMX6_Platform_SDK.zip>
]
It's a great piece of work, but it might be somewhat outdated. First unzip
the file, and then follow steps within the SDK readme.pdf.


Following readme.pdf i do the following: To build the SDK, use the
./tools/build_sdk command from the root folder. I get multiple error but
they are all related to the standard library such as:

    iMX6_Platform_SDK/sdk/drivers/accelerometer/src/mma8451.c:31:10: fatal
error: string.h: No such file or directory #include <string.h>
    iMX6_Platform_SDK/sdk/include/sdk.h:40:10: fatal error: stdio.h: No
such file or directory #include <stdio.h>

**So how do I solve this**? Do I cross compile the standard library or do I
get the binary some other place?


-- 
Mvh/Best regards
Mattis Spieler Asp
Tel: +47 412 44 648

[-- Attachment #2: Type: text/html, Size: 2357 bytes --]

Re: How to add the standard library to arm-fslc-linux-gnueabi-gcc in yocto meta-toolchain fatal error: stdio.h: No such file or directory

[Otavio Salvador]

On Wed, Apr 11, 2018 at 11:19 AM, Mattis Asp <mattis.asp@glucoset.com> wrote:
> Just posted the question here. It's better formatting.
>
> **Question**: How to add the standard library to arm-fslc-linux-gnueabi-gcc
>
> **Background**:
> I just had bitbake compile the `meta-toolchain` in the Yocto project.
> I then installed the resulting SDK-toolchain
>
>> $
>>
>> ./build/tmp/deploy/sdk/fslc-framebuffer-glibc-x86_64-meta-toolchain-armv7at2hf-neon-toolchain-2.4.2.sh
>
> which then installed the SDK-toolchain in /opt/fslc-framebuffer/2.4.2/
>
> I can then easily run the executable to source the correct environment
> variables.
>
>> $
>>
>> ./opt/fslc-framebuffer/2.4.2/environment-setup-armv7at2hf-neon-fslc-linux-gnueabi
> I now have access to the cross-compiler arm-fslc-linux-gnueabi-gcc
> **So far so good...**
>
> I then downloaded the barebone SDK from NXP [here]
> It's a great piece of work, but it might be somewhat outdated. First unzip
> the file, and then follow steps within the SDK readme.pdf.
>
>
> Following readme.pdf i do the following: To build the SDK, use the
> ./tools/build_sdk command from the root folder. I get multiple error but
> they are all related to the standard library such as:
>
>     iMX6_Platform_SDK/sdk/drivers/accelerometer/src/mma8451.c:31:10: fatal
> error: string.h: No such file or directory #include <string.h>
>     iMX6_Platform_SDK/sdk/include/sdk.h:40:10: fatal error: stdio.h: No such
> file or directory #include <stdio.h>
>
> **So how do I solve this**? Do I cross compile the standard library or do I
> get the binary some other place?

You are likely not passing some arguments to the build system. NXP
makefiles are confusing sometimes as they often override things ...
check the corresponding recipe inside the Yocto Project so you can see
how it is done there.
-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750