configure script in jungerl
Matthew D Swank
Wed Sep 7 21:01:35 CEST 2005
Ulf Wiger wrote:
> When trying to build the jungerl code on my Libranet (Debian) distro,
> I encountered some autoheader errors.
> After some reading and hacking around, I made it work by changing
> all AC_DEFINEs to an alternative syntax. This made autoheader stop
> complaining about missing templates.
> For example, in config/aclocal.m4:
> was changed to:
> AC_DEFINE([HAVE_MSGHDR_MSG_CONTROL], , [Description])
> and ditto for all AC_DEFINE(...) and AC_DEFINE_UNQUOTED(...)
> in configure.in.
> I don't feel comfortable enough mucking around in this stuff
> to commit my changes to sourceforge. Perhaps someone else can
> judge whether this is something that should be done?
> Also, should it really be [Description] literally, or should
> something descriptive be written in there instead?
according to the info file:
`autoheader' scans `configure.ac' and figures out which C
preprocessor symbols it might define. It knows how to generate
templates for symbols defined by `AC_CHECK_HEADERS', `AC_CHECK_FUNCS'
etc., but if you `AC_DEFINE' any additional symbol, you must define a
template for it. If there are missing templates, `autoheader' fails
with an error message.
The simplest way to create a template for a SYMBOL is to supply the
DESCRIPTION argument to an `AC_DEFINE(SYMBOL)'
So a reasonable replacement would be
AC_DEFINE_UNQUOTED(CPU_VENDOR_OS, "$target", CPU_VENDOR_OS)
Though cutting and pasting from the error message works correctly also.
More information about the erlang-questions