On 1/20/19 3:36 PM, Chet Ramey wrote:
On 1/19/19 10:27 PM, Dennis Clarke wrote:
No, there's a file named "config.log" that contains all the compiler and
other output from configure. It will tell you what happened when the
script tried to find stdbool.h.
Oh that thing. All 3900+ lines of it.
Well, it doesn't look like the Oracle compiler likes stdbool.h unless under
specific circumstances:
configure:4965: checking stdbool.h usability
configure:4965: /opt/developerstudio12.6/bin/cc -c -m64 -xarch=sparc -g -Xa
-errfmt=error -erroff=%none -errshort=full -xstrconst -xildoff
-xmemalign=8s -xnolibmil -xcode=pic32 -xregs=no%appl -xlibmieee -mc
-ftrap=%none -xbuiltin=%none -xunroll=1 -xs -xdebugformat=dwarf
-I/usr/local/include -D_POSIX_PTHREAD_SEMANTICS -D_LARGEFILE64_SOURCE
-D_TS_ERRNO conftest.c >&5
"/usr/include/stdbool.h", line 42: #error: "Use of <stdbool.h> is valid
only in a c99 compilation environment."
That seems...limiting.
Welcome to the world of Solaris and Oracle where nothing really works
the way you think it should.
I could go back and try again with c99 and strict CFLAGS but my
motivation is quite low ;-)
Dennis
_______________________________________________
Bug-readline mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-readline
