Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Missing sleep function for mingw hosts
Date: Tue, 29 Mar 2011 14:23:00 -0000	[thread overview]
Message-ID: <003001cbee11$49bb0880$dd311980$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <E1Q4Y9z-0004UD-1Y@fencepost.gnu.org>

  Hi Eli,
thanks for your comments.

> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : mardi 29 mars 2011 14:37
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Missing sleep function for mingw hosts
> 
> > From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> > Date: Tue, 29 Mar 2011 09:36:46 +0200
> >
> > mingw does not have a sleep function in its library.
> > This prevents currently successful compilation of
> > mingw64 with --enable-targets=all option.
> 
> You say "mingw64" -- does that mean it does compile with mingw32?  If
> so, how come it fails with the 64-bit build?
  No, it's just the configuration that I used,
but this failure also appears for mingw32.
../../../archer/gdb/remote-mips.c: In function `mips_enter_debug':
../../../archer/gdb/remote-mips.c:1353: warning: implicit declaration of
functio
n `sleep'
make: *** [remote-mips.o] Error 1 

> > I found that there is a substitute for sleep in gnulib:
> >
>
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/sleep.c;hb=d60
> > f3b0c6b0f93a601acd1cfd3923f94ca05abb0
> >
> >   What is the rule to add new parts into gnulib subdirectory?
> > Would inclusion of gnulib sleep.c source code
> > be possible to fix the above problem?
> 
> I'd rather we had a replacement in win32-nat.c, instead of importing
> gobs of gnulib stuff needed to provide such a trivial replacement.
> gnulib is GPL, so we can simply copy the code into our sources.

  This is not really the right place:
the problem triggers due to some other target,
(remote-mips.c line 1353)
so the code should be also available if only that target is selected
(i.e. without windows-nat.c ).
  The best place in my opinion would be mingw-hdep.c,
the only thing is that this would mean adding a mingw-hdep.h header
and inserting that header into remote-mips.c source...
  The big difference with using gnulib code is that the same failure
would not appear again the next time someone adds a call to sleep
somewhere else inside the GDB sources.

Pierre


  reply	other threads:[~2011-03-29 13:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29  8:11 Pierre Muller
2011-03-29 13:10 ` Eli Zaretskii
2011-03-29 14:23   ` Pierre Muller [this message]
2011-03-29 15:40     ` Pedro Alves
2011-03-29 15:41       ` Kai Tietz
2011-03-29 15:43       ` [RFA] use gdb_usleep instead of sleep in remote-mips.c (was Missing sleep function for mingw hosts) Pierre Muller
2011-03-29 15:53         ` Joel Brobecker
2011-03-29 16:54           ` Pierre Muller
2011-03-29 22:05       ` [RFC] Missing sleep function for mingw hosts Eli Zaretskii
2011-03-30  0:06         ` Matt Rice
2011-03-30  4:12           ` Eli Zaretskii
2011-03-30  6:25             ` Matt Rice
2011-03-30  9:25               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003001cbee11$49bb0880$dd311980$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox