Hi Masahiro,
On Wed, 5 Dec 2018 at 22:51, Masahiro Yamada yamada.masahiro@socionext.com wrote:
On Sat, Nov 24, 2018 at 1:43 PM Simon Glass sjg@chromium.org wrote:
Even if U-Boot does not use this, some libraries do. Add back this header file so that the build does not fall back to using the host version, which may include stdint.h and break the build due to conflicts with uint64_t, etc.
The root cause of the problem might be, those libraries mix up <linux/types.h> from U-Boot and <inttypes.h> from the compiler.
Linux kernel has a different <linux/types.h> for user-space tools in tools/include/linux/types.h
Right, but how does it enforce those tools using that file? It is non-standard.
I agree that U-Boot has been screwed up here to a hopeless level.
The problem is not U-Boot. If a library that links against U-Boot includes stdint.h, it expects it to work.
Regards, Simon