|
From: | Paul Eggert |
Subject: | bug#23261: 25.0.92; Undefined behavior in lib/stdint.h |
Date: | Mon, 11 Apr 2016 00:23:15 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
Could we maybe just remove stdint.h completely? It should always be provided by the standard C library.
Unfortunately stdint.h is not portable in practice, as many C implementations don't conform to C11 or even to C99. It sounds like your platform has a problem in this area. Emacs provides a replacement stdint.h on platforms that don't conform to the standards.
I don't observe a problem with my clang installation (clang 3.7.0 on Fedora 23 x86-64). I configured with './configure CC=clang', and on my platform the system stdint.h was fine so lib/stdint.h was not created. Perhaps you could look in your config.log near the strings "checking whether stdint.h ..." and see why your clang has problems with its stdint.h, and debug what went wrong. Another possibility is to futz with your CFLAGS to cajole clang into not issuing the bogus warning. Yet another possibility is to switch to GCC.
[Prev in Thread] | Current Thread | [Next in Thread] |