Mercurial > gnulib
view doc/configmake.texi @ 40213:cc3fed3b7788
unilbrk/u*-possible-linebreaks: Fix undefined behaviour.
Reported by Jeffrey Walton <noloader@gmail.com>.
* lib/unilbrk/u8-possible-linebreaks.c (u8_possible_linebreaks): Don't
invoke memset with a zero size.
* lib/unilbrk/u16-possible-linebreaks.c (u16_possible_linebreaks):
Likewise.
* lib/unilbrk/u32-possible-linebreaks.c (u32_possible_linebreaks):
Adjust accordingly.
author | Bruno Haible <bruno@clisp.org> |
---|---|
date | Sat, 09 Mar 2019 00:27:19 +0100 |
parents | 90cf49c6fdd5 |
children |
line wrap: on
line source
@node configmake @section configmake @findex configmake @r{module} @cindex @file{configmake.h}, module for updating The @code{configmake} module builds a C include file named @file{configmake.h} containing the usual installation directory values; for example, those specified by @code{--prefix} or @code{--libdir} to configure. Each variable is given a @code{#define} with an all-uppercase macro name, such as @code{PREFIX} and @code{LIBDIR}. (Automake cannot create this file directly because the user might override directory values at @code{make} time.) Specifically, the module retrieves values of the variables through @code{configure} followed by @code{make}, not directly through @code{configure}, so that a user who sets some of these variables consistently on the @code{make} command line gets correct results. One advantage of this approach, compared to the classical approach of adding @code{-DLIBDIR=\"$(libdir)\"} etc.@: to @code{AM_CPPFLAGS}, is that it protects against the use of undefined variables. That is, if, say, @code{$(libdir)} is not set in the Makefile, @code{LIBDIR} is not defined by this module, and code using @code{LIBDIR} gives a compilation error. Another advantage is that @code{make} output is shorter. For the complete list of variables which are @code{#define}d this way, see the file @file{gnulib/modules/configmake}, or inspect your resulting gnulib Makefile.