Re: FYI: removing HAVE_FCNTL_H tests

2005-08-09 Thread Derek Price
Jim Meyering wrote:

>Bruno Haible <[EMAIL PROTECTED]> wrote:
>  
>
>
>>One platform still does not have : It's Woe32 with the MSVC
>>compiler. It's unfortunately a major platform, and still alive.
>>
>>
>
>Perhaps it's not a popular enough build environment for packages using
>gnulib.  Several existing modules include  unconditionally:
>
>  lib/argp-parse.c
>  lib/chdir-long.c
>  lib/fts.c
>  lib/getpass.c
>  lib/openat.c
>  lib/poll.c
>  lib/utime.c
>
>and yet I haven't heard any complaints.
>  
>

We dealt with it on CVS by putting the unistd.h prototypes we needed in
a unistd.h file that only gets included on WOE32.  I believe we also had
to implement a few missing POSIX functions.

Regards,

Derek

-- 
Derek R. Price
CVS Solutions Architect
Ximbiot 
v: +1 717.579.6168
f: +1 717.234.3125





___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib


Re: FYI: removing HAVE_FCNTL_H tests

2005-07-14 Thread Jim Meyering
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> > I've just removed all tests for HAVE_FCNTL_H from coreutils.
>> > It's been gone in at least one place since coreutils-5.0 (2004-04-02)

[actually, that should have been 2003-04-02, not 2004]

>> The same applies to HAVE_UNISTD_H and unistd.h
>
> One platform still does not have : It's Woe32 with the MSVC
> compiler. It's unfortunately a major platform, and still alive.

Perhaps it's not a popular enough build environment for packages using
gnulib.  Several existing modules include  unconditionally:

  lib/argp-parse.c
  lib/chdir-long.c
  lib/fts.c
  lib/getpass.c
  lib/openat.c
  lib/poll.c
  lib/utime.c

and yet I haven't heard any complaints.

> Also,  is less dependable for GNU programs than ,
> because someone creates a brand new operating system different in style
> from Unix, he will typically implement the ISO C headers but not POSIX
> . (Some recent operating systems like BeOS or MacOS X have
> a Unix underneath, but others don't.)

IMHO, a new OS that does not provide a POSIX header like 
does not deserve our consideration -- and isn't likely to get much
from any other development community, either.

> So for the sake of ease of porting to new OSes, I would leave HAVE_UNISTD_H
> in place.

Thanks for the info.
I've made a note to wait a year.
If there have still been no complaints,
I'll remove them then.


___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib


Re: FYI: removing HAVE_FCNTL_H tests

2005-07-11 Thread Bruno Haible
Jim Meyering wrote:
> > I've just removed all tests for HAVE_FCNTL_H from coreutils.
> > It's been gone in at least one place since coreutils-5.0 (2004-04-02)
>
> The same applies to HAVE_UNISTD_H and unistd.h

One platform still does not have : It's Woe32 with the MSVC
compiler. It's unfortunately a major platform, and still alive.

Also,  is less dependable for GNU programs than ,
because someone creates a brand new operating system different in style
from Unix, he will typically implement the ISO C headers but not POSIX
. (Some recent operating systems like BeOS or MacOS X have
a Unix underneath, but others don't.)

So for the sake of ease of porting to new OSes, I would leave HAVE_UNISTD_H
in place.

Bruno



___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib


Re: FYI: removing HAVE_FCNTL_H tests

2005-07-02 Thread Jim Meyering
I wrote:
> I've just removed all tests for HAVE_FCNTL_H from coreutils.
> It's been gone in at least one place since coreutils-5.0 (2003-04-02)
> and no one has complained, so I think it's safe to say every system
> we care about has fcntl.h, now.
>
> If you know of a system (reasonable portability target)
> that lacks fcntl.h, speak now.
>
> Tomorrow I plan to remove all #if HAVE_FCNTL_H tests,
> retaining only the `if' branch.  Likewise, there is no
> need to check for fcntl.h in .m4 macros.

I've just done the same for gnulib:

[lib]
2005-07-01  Jim Meyering  <[EMAIL PROTECTED]>

* chown.c, cloexec.c, dup-safer.c, dup2.c, fsusage.c, getcwd.c:
* getloadavg.c, mountlist.c, openat.h, pagealign_alloc.c:
* save-cwd.c, tempname.c:
Assume HAVE_FCNTL_H (i.e., include  unconditionally,
and don't include ).

[m4]
2005-07-02  Jim Meyering  <[EMAIL PROTECTED]>

* chown.m4, cloexec.m4, dup2.m4, fsusage.m4:
* getcwd-path-max.m4, getcwd.m4, mkstemp.m4, mountlist.m4:
* pagealign_alloc.m4, save-cwd.m4, unistd-safer.m4:
Don't check for fcntl.h, and don't test for HAVE_FCNTL_H.


___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib


Re: FYI: removing HAVE_FCNTL_H tests

2005-07-01 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote:
> I've just removed all tests for HAVE_FCNTL_H from coreutils.
> It's been gone in at least one place since coreutils-5.0 (2004-04-02)
> and no one has complained, so I think it's safe to say every system
> we care about has fcntl.h, now.

FYI, that date should have been (2003-04-02).


___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib


Re: FYI: removing HAVE_FCNTL_H tests

2005-07-01 Thread Jim Meyering
Jim Meyering <[EMAIL PROTECTED]> wrote:
> I've just removed all tests for HAVE_FCNTL_H from coreutils.
> It's been gone in at least one place since coreutils-5.0 (2004-04-02)

The same applies to HAVE_UNISTD_H and unistd.h,
but I haven't yet made the change in coreutils.
I'll do it over the weekend, too.

> and no one has complained, so I think it's safe to say every system
> we care about has fcntl.h, now.
>
> If you know of a system (reasonable portability target)
> that lacks fcntl.h, speak now.


___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib


FYI: removing HAVE_FCNTL_H tests

2005-07-01 Thread Jim Meyering
I've just removed all tests for HAVE_FCNTL_H from coreutils.
It's been gone in at least one place since coreutils-5.0 (2004-04-02)
and no one has complained, so I think it's safe to say every system
we care about has fcntl.h, now.

If you know of a system (reasonable portability target)
that lacks fcntl.h, speak now.

Tomorrow I plan to remove all #if HAVE_FCNTL_H tests,
retaining only the `if' branch.  Likewise, there is no
need to check for fcntl.h in .m4 macros.


___
bug-gnulib mailing list
bug-gnulib@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnulib