Hi!
The sys_socket module below will create a sys/socket.h file, primarily
for mingw32, but it could be extended for other systems or missing
sys/socket.h features in the future.
This would solve the problem of accessing sys/socket.h stuff in
applications.
However, it does not solve the problem
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote on 2005-12-17:
>> The sys_socket module below will create a sys/socket.h file, primarily
>> for mingw32, but it could be extended for other systems or missing
>> sys/socket.h features in the future.
>>
>> This would solve the proble
Simon Josefsson wrote:
> >> + rmdir sys
> >
> > Remove the directory only when it exists and is empty. (Some systems
> > create files in your directories without being asked for, e.g. .DS_Store
> > on MacOS X.)
>
> How do I test for that in a portable way?
Let rmdir do the test, and ignore a poss
Bruno Haible <[EMAIL PROTECTED]> writes:
> Simon Josefsson wrote:
>> >> + rmdir sys
>> >
>> > Remove the directory only when it exists and is empty. (Some systems
>> > create files in your directories without being asked for, e.g. .DS_Store
>> > on MacOS X.)
>>
>> How do I test for that in a porta
Simon Josefsson wrote on 2005-12-17:
> The sys_socket module below will create a sys/socket.h file, primarily
> for mingw32, but it could be extended for other systems or missing
> sys/socket.h features in the future.
>
> This would solve the problem of accessing sys/socket.h stuff in
> applicatio
