Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream

[Svante Signell <svante.signell@telia.com>]

On Wed, 2012-10-17 at 11:07 +0200, Samuel Thibault wrote:
> Svante Signell, le Wed 17 Oct 2012 11:00:38 +0200, a écrit :
> > On Wed, 2012-10-17 at 09:27 +0200, Svante Signell wrote:
> > For symmetry reasons the text below
> > >   AC_MSG_WARN([getcwd(NULL,0)... cannot run test program while cross
> > > compiling])
> > should be changed to
> >   AC_MSG_WARN([checking for getcwd(NULL,0)... cannot run test program
> > while cross compiling])
> 
> Actually "checking for getcwd(NULL,0)..." printing should be factorized
> into an AC_MSG_CHECKING call before the actual test.

Final version?

AC_CHECK_FUNCS([getcwd])
AC_RUN_IFELSE([
AC_LANG_PROGRAM([
#ifdef HAVE_GETCWD
#include <unistd.h>
#endif
],[
char *result = getcwd(NULL,0);
if (result == NULL)
  return 1;
])],[
  AC_MSG_RESULT([checking for getcwd(NULL, 0)... yes])
  AC_DEFINE([HAVE_GETCWD_GLIBC], 1, [Define to 1 if you have support for
`getcwd(NULL,0)`])
],[
  AC_MSG_RESULT([checking for getcwd(NULL, 0)... no])
],[
  AC_MSG_CHECKING([getcwd(NULL,0)])
  AC_MSG_WARN([cannot run test program while cross compiling])
])