From: rm@fabula.de
Subject: Autoconf-like #defines in distributed header file
Date: Sat, 27 Jul 2002 18:52:58 +0200 [thread overview]
Message-ID: <20020727165258.GA27310@www> (raw)
Hello list/maintainers,
working on the autoconf-ing of mod_guile i
just realized that the guile build process
(via autogen.sh) uses 'atoheader' to produce
libguile/scmconfig.h.in which is later processed
by configure to generate libguile/scmconfig.h.
I think this use of autoheader to produce a header
file that gets distributed might create problems in
situations where libguile is used by other autoconf-
enabled software. If suchsoftware uses its own version
of 'config.h' (which is _not_ supposed to get installed)
like in the following example:
|
| #include "config.h"
| ...
| #include <libguile.h>
|
|
... '#define's from the build phase of libguile leak into the
software's build. '#define PACKAGE_VERSION ""' from scmconfig.h
will override the softwares own version of the value and possibly
introduce errant behaviour if the software uses this value for
its own version testing.
Fix: probably create scmconfig.h.in maually, avoiding the general
'#define's (or moving them to config.h.in or any similar file that
doesn't get installed).
Ralf Mattes
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-07-27 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 16:52 rm [this message]
2002-08-05 11:54 ` Autoconf-like #defines in distributed header file Han-Wen Nienhuys
2002-08-05 16:30 ` Rob Browning
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020727165258.GA27310@www \
--to=rm@fabula.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).