Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: jan.kratochvil@redhat.com, ktietz@redhat.com,
	gdb-patches@sourceware.org, vinschen@redhat.com,
	nickc@redhat.com
Subject: Re: [patch 1/2] mingw: update gnulib: prepare the sources
Date: Mon, 23 Mar 2015 17:37:00 -0000	[thread overview]
Message-ID: <83mw33r4y3.fsf@gnu.org> (raw)
In-Reply-To: <55104C7B.9060405@redhat.com>

> Date: Mon, 23 Mar 2015 17:25:15 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: Kai Tietz <ktietz@redhat.com>, gdb-patches@sourceware.org,        Corinna Vinschen <vinschen@redhat.com>,        Nicholas Clifton <nickc@redhat.com>
> 
> > With this header file used for GDB's sources aren't gnulib's .c files compiled
> > with incompatible ABI?
> 
> Other than rpl_gettimeofday (the gettimeofday replacement):
> 
>   gettimeofday.o:0000005a T _rpl_gettimeofday
> 
> AFAICS, there's no other use of "struct timeval" or gettimeofday in gnulib's
> sources.

We should watch out for Gnulib's 'select' and friends, if we ever want
to import that.  Also 'utimens'.


  parent reply	other threads:[~2015-03-23 17:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 22:12 Jan Kratochvil
2014-12-23 11:54 ` Kai Tietz
2014-12-24 22:20   ` Jan Kratochvil
2015-03-23 16:51     ` Pedro Alves
2015-03-23 17:08       ` Jan Kratochvil
2015-03-23 17:25         ` Pedro Alves
2015-03-23 17:32           ` Jan Kratochvil
2015-03-23 17:37           ` Eli Zaretskii [this message]
2015-03-23 17:57             ` Pedro Alves
2015-08-24 18:09               ` Pedro Alves
2015-03-23 19:17       ` Corinna Vinschen
2015-03-23 19:28         ` Pedro Alves
2015-03-23 19:47           ` Corinna Vinschen

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=83mw33r4y3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=ktietz@redhat.com \
    --cc=nickc@redhat.com \
    --cc=palves@redhat.com \
    --cc=vinschen@redhat.com \
    /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