stdint.h: No such file or directory

RE: stdint.h: No such file or directory

peter9477 — Wed, 27 Sep 2017 15:54:41 GMT

Thanks! In my case (Debian 9.1) it was package "libnewlib-arm-none-eabi" that did it.

RE: stdint.h: No such file or directory

Martin Kupec — Wed, 28 Dec 2016 17:18:52 GMT

In fedora it helps to install arm-none-eabi-newlib package

RE: stdint.h: No such file or directory

Javier — Fri, 23 Sep 2016 11:26:30 GMT

Hi!,

I was used Fedora 25. Today, in the same hard-disk I have installed Ubuntu 16.04 64 bits with arm-none-eabi-gcc 4.9.3

Now compile succefully!

javi@PC:~/Development/Nordic/nRF52/examples/peripheral/blinky/pca10040/blank/armgcc$ make
Makefile:204: Cannot find include folder:  ../../../config/blinky_pca10040
Makefile:204: Cannot find include folder:  ../../../config
mkdir _build
Assembling file: gcc_startup_nrf52.S
Compiling file: system_nrf52.c
Compiling file: main.c
Compiling file: app_error.c
Compiling file: app_error_weak.c
Compiling file: app_fifo.c
Compiling file: app_timer.c
Compiling file: app_util_platform.c
Compiling file: hardfault_implementation.c
Compiling file: nrf_assert.c
Compiling file: nrf_drv_clock.c
Compiling file: nrf_drv_common.c
Compiling file: nrf_nvic.c
Compiling file: nrf_soc.c
Linking target: _build/nrf52832_xxaa.out
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-atexit.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-exit.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-fini.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-impure.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-init.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-memset.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-__atexit.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail
/usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/bin/ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/../../../arm-none-eabi/lib/armv7e-m/fpu/libc_nano.a(lib_a-__call_atexit.o) uses 2-byte wchar_t yet the output is to use 4-byte wchar_t; use of wchar_t values across objects may fail

   text	   data	    bss	    dec	    hex	filename
   4776	    112	    228	   5116	   13fc	_build/nrf52832_xxaa.out

Preparing: _build/nrf52832_xxaa.hex
Preparing: _build/nrf52832_xxaa.bin

Thanks very much, Best regards

RE: stdint.h: No such file or directory

butch — Thu, 22 Sep 2016 14:05:26 GMT

Specifically, exactly which standalone GNU ARM toolchain on which platform(s) does Nordic recommend? If Nordic is recommending a "standalone" toolchain, wouldn't "--freestanding" be in their example Makefiles? I am not recommending to mess around with makefiles in the SDK to fix this problem. But you must "mess around" with the Makefile anyway, to add your source files, fix known bugs in the Makefiles, etc. Javier, ">which gcc" to make sure you have a non-cross compiling gcc installed.

RE: stdint.h: No such file or directory

RK — Thu, 22 Sep 2016 13:44:52 GMT

yeah he can fiddle around for days getting something working using whatever redhat provides and then wait for it to break again, or he can download a standalone GNU ARM toolchain which is known to work. Just trying to help him get from where he is to where he wants to be in the shortest time without having to mess around with the makefiles in the SDK.

RE: stdint.h: No such file or directory

butch — Thu, 22 Sep 2016 13:41:19 GMT

my stdint.h:

#ifndef _GCC_WRAP_STDINT_H
#if __STDC_HOSTED__
# if defined __cplusplus && __cplusplus >= 201103L
#  undef __STDC_LIMIT_MACROS
#  define __STDC_LIMIT_MACROS
#  undef __STDC_CONSTANT_MACROS
#  define __STDC_CONSTANT_MACROS
# endif
# include_next <stdint.h>
#else
# include "stdint-gcc.h"
#endif
#define _GCC_WRAP_STDINT_H
#endif

See stackoverflow.com/.../what-is-ffreestanding-option-in-gcc

So maybe Javier doesn't have a default dev environment (with non-cross compiling gcc) installed? (Which would have a stdint.h that the #include_next would find?) I could be wrong.

RE: stdint.h: No such file or directory

butch — Thu, 22 Sep 2016 13:31:51 GMT

I assume Javier thinks his gnu toolchain IS proper, since he probably installed it using the distro's methods. Javier, what platform and how did you install? The version does seem strange (on my Ubuntu 16.04, the distro's ARM gcc version is 4.9.3) so maybe Redhat is applying their own versioning? BTW, Redhat is instrumental in maintaining gcc, so you would think it would be OK. Maybe read near line 9 in stdint.h to figure out why it thinks it needs another stdint.h found further along the list of include directories?

RE: stdint.h: No such file or directory

RK — Thu, 22 Sep 2016 12:03:44 GMT

It's the include_next thing - you don't have a next one so it doesn't work. I still recommend downloading the proper supported gnu toolchain and using that.

RE: stdint.h: No such file or directory

Javier — Thu, 22 Sep 2016 10:57:06 GMT

@RK,

[javier@PC armgcc]$ make clean
Makefile:203: Cannot find include folder:  ../../../config/blinky_pca10040
Makefile:203: Cannot find include folder:  ../../../config
rm -rf _build
[javier@PC armgcc]$ make
Makefile:203: Cannot find include folder:  ../../../config/blinky_pca10040
Makefile:203: Cannot find include folder:  ../../../config
mkdir _build
Assembling file: gcc_startup_nrf52.S
Compiling file: system_nrf52.c
In file included from ../../../../../../components/toolchain/system_nrf52.c:31:0:
/usr/lib/gcc/arm-none-eabi/6.1.0/include/stdint.h:9:26: fatal error: stdint.h: No such file or directory
 # include_next <stdint.h>
                          ^
compilation terminated.
../../../../../../components/toolchain/gcc/Makefile.common:108: fallo en las instrucciones para el objetivo '_build/nrf52832_xxaa_system_nrf52.c.o'
make: *** [_build/nrf52832_xxaa_system_nrf52.c.o] Error 1

RE: stdint.h: No such file or directory

RK — Thu, 22 Sep 2016 10:34:58 GMT

does he have another stdint.h?

RE: stdint.h: No such file or directory

butch — Thu, 22 Sep 2016 10:33:27 GMT

I agree with RK about the first errors probably are harmless, since they are part of make clean. But rather than install a new GNU ARM toolchain you could try a temporary hack: the error message says the GNU ARM stdint.h, at line 9 is #next_include'ing another stdint.h further down the list of include files. Try commenting that line out. If make then works, and your app works, you might then wonder if the #include_next was really needed. But if you get error messages similar to "can't resolve symbol" for symbols which you think should be defined in stdint, then its not the right solution. RK, #include_next is Unix'y, then Gnu'y, then Linux'y. As the Gnu Make document says, #include_next is arcane and should rarely be needed, in other words, a bit of a hack itself.

RE: stdint.h: No such file or directory

RK — Thu, 22 Sep 2016 08:59:37 GMT

quick googling shows that include_next is very linux'y and requires you to have another directory in the include list after the standard one to supply stdint.h, which you don't have.

I would go with Hakon's suggestion to install the proper arm-none-eabi, I don't know where that 6.1.0 one came from.

RE: stdint.h: No such file or directory

RK — Thu, 22 Sep 2016 08:51:15 GMT

those errors are ok - annoying but ok - what happens when you make again after the make clean

RE: stdint.h: No such file or directory

Javier — Thu, 22 Sep 2016 08:24:33 GMT

Hi,

Thanks for the replies,

stdint.h exists into include folder:

[javier@PC include]$ pwd
/usr/lib/gcc/arm-none-eabi/6.1.0/include
[javier@PC include]$ ls
arm_acle.h  mmintrin.h   stdbool.h     stdint.h             unwind.h
arm_neon.h  stdalign.h   stddef.h      stdnoreturn.h        varargs.h
float.h     stdarg.h     stdfix.h      tgmath.h
iso646.h    stdatomic.h  stdint-gcc.h  unwind-arm-common.h

I think that documentation is based in this tutorial gnuarmeclipse.github.io/.../

and used this path (for Ubuntu) /usr/local/gcc-arm-none-eabi-4_9-2015q3 (I used Fedora 25)

I will try to edit the Makefile as Butch said.

Cheers

PD: @RK, Same error: make clean

Makefile:203: Cannot find include folder:  ../../../config/blinky_pca10040
Makefile:203: Cannot find include folder:  ../../../config
rm -rf _build

RE: stdint.h: No such file or directory

RK — Thu, 22 Sep 2016 07:59:49 GMT

Have you tried 'make clean' to remove all the old dependency files first？I've seen this when and old .d file references and old include.

RE: stdint.h: No such file or directory

Håkon Alseth — Thu, 22 Sep 2016 07:29:08 GMT

I've seen the same behavior with the arm-none-eabi that is supplied with other linux distro's, meaning that the behavior is quite "strange". Can you check if stdint.h is actually located in this directory?

/usr/lib/gcc/arm-none-eabi/6.1.0/include/

If it still does not work properly, I would strongly recommend using the upstream arm-none-eabi located on launchpad: launchpad.net/.../ download

Cheers, Håkon

RE: stdint.h: No such file or directory

butch — Wed, 21 Sep 2016 14:55:52 GMT

I don't have an answer but I will give my thoughts. My strategy would be to fix the first error "Cannot find...". This comes from the function ensure_exists() in the Makefile. These Makefiles are very fragile: they use "../../.." and that breaks when you don't have exactly the same directory structure as the original build system. Try installing the SDK and example exactly in the places as shown in some tutorial. Next thought: I have never seen #include_next. If you read about it, it is used for redirecting the include to some patched or other file. I can't tell whether the gcc arm include file stdint.h is doing #include_next (which would say that your gcc arm toolchain might be broken, or looking for a non-ARM toolchain stdint.h?) or whether a Nordic Makefile is doing #include_next.