Fix the definitions around printf: either we use system printf in which

* configure.in: Fix the definitions around printf: either we use
	system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
	HAVE_UNIX98_PRINTF have already been determined by earlier tests,
	or we use the included printf, in which case we know that these
	three can be defined as 1.  (#99826)
This commit is contained in:
Matthias Clasen 2002-11-28 18:50:41 +00:00
parent a69dc4b65d
commit 7c2ae36588
8 changed files with 43 additions and 0 deletions

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -1,5 +1,11 @@
2002-11-28 Matthias Clasen <maclas@gmx.de>
* configure.in: Fix the definitions around printf: either we use
system printf in which case HAVE_VASPRINTF, HAVE_C99_VSNPRINTF and
HAVE_UNIX98_PRINTF have already been determined by earlier tests,
or we use the included printf, in which case we know that these
three can be defined as 1. (#99826)
* glib/gutf8.c (g_utf8_strreverse):
* glib/gstrfuncs.c (g_str_has_suffix):
(g_str_has_prefix):

View File

@ -732,6 +732,7 @@ fi
AM_CONDITIONAL(HAVE_GOOD_PRINTF, test "$enable_trio" != "yes")
if test "$enable_trio" != "yes" ; then
AC_DEFINE(HAVE_GOOD_PRINTF,1,[define to use system printf])
else
AC_DEFINE(HAVE_VASPRINTF,1)
AC_DEFINE(HAVE_C99_VSNPRINTF,1)
AC_DEFINE(HAVE_UNIX98_PRINTF,1)