Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
> On Wed, 2012-10-17 at 16:15 +0200, Guillem Jover wrote:
> AC_DEFINE([HAVE_GNU_GETCWD], [1],
> [Define to 1 if you have support for 'getcwd(NULL, 0)' GNU extension])
BTW, why calling it a GNU extension, not GLIBC or LIBC.
>From the man page: As an extension to the POSIX.1-2001 standard,
Linux (libc4, libc5, glibc) getcwd() allocates the buffer dynamically
using malloc(3) if buf is NULL.
get_current_dir_name() is a GNU extension though, again according to the
man page.
Reply to:
- References:
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
- From: Samuel Thibault <sthibault@debian.org>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
- From: Svante Signell <svante.signell@telia.com>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
- From: Pino Toscano <pino@debian.org>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
- From: Svante Signell <svante.signell@telia.com>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
- From: Guillem Jover <guillem@debian.org>
- Re: Check for getcwd(NULL, 0) Was: Re: Bug#636568: xerces-c: Updated patch, submitted upstream
- From: Svante Signell <svante.signell@telia.com>