bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: errors building m4 on interix/sfu/sua


From: Eric Blake
Subject: Re: errors building m4 on interix/sfu/sua
Date: Tue, 16 Jun 2009 13:01:35 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[please don't top-post on technical lists]

According to address@hidden on 6/16/2009 8:08 AM:
> Isn't just ifdef estale around use of it sufficient? Or is there some
> chance of const int or such?

That misses the whole point of the gnulib errno module, which exists to
guarantee that user code can assume that ESTALE is always defined, and to
a useful value.  In other words, the proper fix is to the gnulib errno
module to work around Interix's buggy lack of ESTALE, and not in the rest
of m4 code by #ifdef away the use of ESTALE.

> Given that const int cannot be switched on
> in C, they must    all be defines and simple ifdef suffices and is fully
> portable no need for configury? Right?

Huh?  There's no restriction against switching on const int in C.

> I don't/won'tlikely have the paperwork,

And that's the very reason why gnulib support for Interix is so lacking -
no one seems to be serious enough about the platform to offer maintenance
support.  Even being willing to run regression tests and post autobuild
results on a regular basis, which does not require copyright assignment,
would go a long way to helping us track whether gnulib changes are still
portable to Interix.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAko37A8ACgkQ84KuGfSFAYDfZQCeM3ehCwQXqKHcBVUzShCXqrYG
qsQAn1tmNOQrrdmGKRj7vHuxAzWgfcIQ
=65Dk
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]