Discussion:
[Bug-apl] Why /* #undef ....*/ in config.h?
Peter Teeson
2017-08-18 20:18:16 UTC
Permalink
Hi JÃŒrgen:
I have been wandering in the GNU APL autotools byzantine(1) labyrinth(2) and am wondering why the #undefs in config.h are commented out?
See for example lines 244, 247, 250 for WANT_ANDROID, WANT_ERLANG, WANT_LIBAPL.

config.h.in shows them not commented out so I’m curious...

respect
..

Peter

(1) byzantine (of a system or situation) excessively complicated, typically involving a great deal of administrative detail:
(2) labyrinth a complicated irregular network of passages or paths in which it is difficult to find one's way; a maze
Kacper Gutowski
2017-08-18 22:45:21 UTC
Permalink
Post by Peter Teeson
I have been wandering in the GNU APL autotools byzantine(1) labyrinth(2) and am wondering why the #undefs in config.h are commented out?
See for example lines 244, 247, 250 for WANT_ANDROID, WANT_ERLANG, WANT_LIBAPL.
config.h.in shows them not commented out so I’m curious...
Note that config.h.in contains only #undef directives, there is no #define
at all. And after deciding which parts to define for given configuration,
others are commented out rather than being explicitly undefined.

Why? Inside the configure script there's an awk script that is written
Post by Peter Teeson
# Replace #undef with comments. This is necessary, for example,
# in the case of _POSIX_SOURCE, which is predefined and required
# on some systems where configure will not decide to define it.
-k

Loading...