Now that we have a sys_select module, I'd like to propose the patch from
my previous mail again (make the nanosleep module use the sys_select
module). This would allow to use nanosleep on MinGW.
Martin
On Wed, 07. Jun 2006, 14:31:34 +0200, Simon Josefsson wrote:
> > Is there any interest in this module?
>
> Yes. I think it looks good. Unless someone objects soonish, I think
> we should install it.
I integrated the lates changes to the sys_socket module.
I also filled in Simon as the maintaine
Martin Lambers <[EMAIL PROTECTED]> writes:
> On Tue, 23. May 2006, 22:18:23 +0200, Martin Lambers wrote:
>> On Tue, 23. May 2006, 00:25:11 -0700, Paul Eggert wrote:
>> > In that case, it may be best for gnulib to generate a substitute
>> > file that does the right thing under Microsoft Windows
>>
On Tue, 23. May 2006, 22:18:23 +0200, Martin Lambers wrote:
> On Tue, 23. May 2006, 00:25:11 -0700, Paul Eggert wrote:
> > In that case, it may be best for gnulib to generate a substitute
> > file that does the right thing under Microsoft Windows
> > (or indeed, any platform that lacks ). That wa
On Tue, 23. May 2006, 22:21:15 +0200, Martin Lambers wrote:
> With the new sys_select module and the attached changes to the nanosleep
> module, my project compiles and links fine when crosscompiled using the
> mingw package.
I forgot to add the new file nanosleep.h to AC_LIBSOURCES. Here is an
up
With the new sys_select module and the attached changes to the nanosleep
module, my project compiles and links fine when crosscompiled using the
mingw package.
Martin
diff -uNr gnulib/lib/nanosleep.c gnulib-sys_select_h/lib/nanosleep.c
--- gnulib/lib/nanosleep.c 2006-05-20 21:22:15.
On Tue, 23. May 2006, 00:25:11 -0700, Paul Eggert wrote:
> In that case, it may be best for gnulib to generate a substitute
> file that does the right thing under Microsoft Windows
> (or indeed, any platform that lacks ). That way, gnulib
> modules like nanosleep can simply "#include "
> uncondit
In that case, it may be best for gnulib to generate a substitute
file that does the right thing under Microsoft Windows
(or indeed, any platform that lacks ). That way, gnulib
modules like nanosleep can simply "#include "
unconditionally and use 'select'.
Is that something you could write?
On Sun, 21. May 2006, 21:27:15 -0700, Paul Eggert wrote:
> > No, unfortunately it does not, because the target system does not have a
> > nanosleep function.
>
> OK. Do the other parts of the patch (e.g., the HAVE_SYS_SELECT_H,
> TIME_WITH_SYS_TIME, etc.) address the problem? If not, what proble
Martin Lambers <[EMAIL PROTECTED]> writes:
> No, unfortunately it does not, because the target system does not have a
> nanosleep function.
OK. Do the other parts of the patch (e.g., the HAVE_SYS_SELECT_H,
TIME_WITH_SYS_TIME, etc.) address the problem? If not, what problems
do you encounter wit
On Fri, 19. May 2006, 11:01:49 -0700, Paul Eggert wrote:
> There's one other thing about this particular problem that may save us
> here, though. The current code tests that nanosleep works at runtime,
> not merely whether it links. I suspect this is overkill, at least
> nowadays. And, since the
Jim Meyering <[EMAIL PROTECTED]> writes:
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
> ...
>> Wouldn't this be a good situation to have nanosleep depend on the
>> unistd module, and make the replacement unistd.h include winsock2.h on
>> mingw32 platforms? After all, nanosleep.c include unistd.h,
Bruno Haible <[EMAIL PROTECTED]> writes:
> Since gnulib's policy is to let the programs write code in POSIX
> syntax, I vote for a module that creates a file in
> the build directory.
Yes, that would make sense, to properly declare 'select'. For
nanosleep I suppose we'd also need a substitute t
Simon Josefsson wrote:
> Wouldn't this be a good situation to have nanosleep depend on the
> unistd module, and make the replacement unistd.h include winsock2.h on
> mingw32 platforms? After all, nanosleep.c include unistd.h, and
> unistd.h define select on some platforms.
But is not supposed to
Simon Josefsson <[EMAIL PROTECTED]> wrote:
...
> Wouldn't this be a good situation to have nanosleep depend on the
> unistd module, and make the replacement unistd.h include winsock2.h on
> mingw32 platforms? After all, nanosleep.c include unistd.h, and
> unistd.h define select on some platforms.
On Thu, May 18, 2006 at 10:23:49PM +0200, Bruno Haible wrote:
> > +#ifdef _WIN32
>
> The conditional for Woe32 platforms, excluding Cygwin (which has normal Unix
> API),
> is
>#if (defined _WIN32 || defined __WIN32__) && !defined __CYGWIN__
Sorry, I somehow missed your mail about Cygwin defi
Martin Lambers <[EMAIL PROTECTED]> writes:
> Hi,
>
> I get the following error when using the nanosleep module and
> crosscompiling to W32 with the Debian mingw32 package and
> ./configure --host=i586-mingw32msvc :
>
> ../gnulib/libgnu.a(nanosleep.o):nanosleep.c:(.text+0x64): undefined reference
Hello,
> I get the following error when using the nanosleep module and
> crosscompiling to W32 with the Debian mingw32 package and
> ./configure --host=i586-mingw32msvc :
>
> ../gnulib/libgnu.a(nanosleep.o):nanosleep.c:(.text+0x64): undefined
> reference to `_select'
>
> The attached patch fixes t
Hi,
I get the following error when using the nanosleep module and
crosscompiling to W32 with the Debian mingw32 package and
./configure --host=i586-mingw32msvc :
../gnulib/libgnu.a(nanosleep.o):nanosleep.c:(.text+0x64): undefined reference
to `_select'
The attached patch fixes this for me.
Re
19 matches
Mail list logo