From: Sam S. <sd...@gn...> - 2002-05-29 20:28:28
|
> * In message <20020529184511.GA848@balefire.localdomain> > * On the subject of "[clisp-list] can't build CVS clisp under OpenBSD 3.0 for x86" > * Sent on Wed, 29 May 2002 13:45:11 -0500 > * Honorable William Harold Newman <wil...@ai...> writes: > > The second problem is that CLISP's stdbool.h uses #define to turn > "true" and "false" into "1" and "0", and then CLISP elsewhere > #include's the OpenBSD file "/usr/include/stdbool.h", which does > /* `_Bool' type must promote to `int' or `unsigned int'. */ > typedef enum { > false = 0, > true = 1 > } _Bool; > So then of course when this is preprocessed into > /* `_Bool' type must promote to `int' or `unsigned int'. */ > typedef enum { > 0 = 0, > 1 = 1 > } _Bool; > gcc is not happy. CLISP is not supposed to include "/usr/include/stdbool.h" - it comes with its own. --- lispbibl.d 29 May 2002 12:25:19 -0000 1.258 +++ lispbibl.d 29 May 2002 20:27:53 -0000 @@ -1145,7 +1145,11 @@ #endif # boolean values: +#ifdef HAVE_STDBOOL_H + #include <stdbool.h> +#else #include "stdbool.h" +#endif # Type for signed values, results of comparisons, tertiary enums # with values +1, 0, -1 does this help? > I ground to a halt on the second problem, so I dunno whether there's > a third problem. I am sure there is - the sources have changed a lot in the recent days. -- Sam Steingold (http://www.podval.org/~sds) running RedHat7.2 GNU/Linux <http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/> <http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html> When we write programs that "learn", it turns out we do and they don't. |