d? (This seems ugly, since I'd need to define an
`AH_TEMPLATE` as well and all that.) Just turn on all extensions that I
may or may not use, unconditionally at the top of the file? Something
completely different?
Thanks for reading!
--
Fredrik Tolf
__
On Wed, 26 Feb 2014, Eric Blake wrote:
On 02/26/2014 07:16 PM, Fredrik Tolf wrote:
On glibc, I need to define `_GNU_SOURCE' in order to gain access to
fopencookie() and cookie_io_functions_t. Autoconf neatly supports
turning this on with `AC_USE_SYSTEM_EXTENSIONS(_GNU_SOURCE)', b
perhaps arguably sloppy, nature
of systems development leaves things a bit unclear. But if that is so,
isn't it still ugly to have to use AC_USE_SYSTEM_EXTENSIONS always, on all
systems, rather than being left the option of using whatever the system
On Mon, 3 Mar 2014, Eric Blake wrote:
On 03/01/2014 08:32 PM, Fredrik Tolf wrote:
I read what you write kind of as if systems shouldn't expose anything
non-POSIX as long as it isn't used, but this is clearly not the case;
not only with funopen() on *BSD, but also with e.g. epoll() on
it to CPPFLAGS? Please
tell me.
Fredrik Tolf
Peter Eisentraut writes:
> Fredrik Tolf writes:
>
> > How do I get the sysconfdir into a cpp macro if I use automake as
> > well? Should I do it through a config header, or should I do it via
> > some automake contraption? Should I just add it to CPPFLAGS? Please
Guido Draheim writes:
>
>
> Peter Eisentraut wrote:
> > Fredrik Tolf writes:
> >
> >
> >>How do I get the sysconfdir into a cpp macro if I use automake as
> >>well? Should I do it through a config header, or should I do it via
> >
