public inbox for src-cvs@sourceware.org
help / color / mirror / Atom feed
From: tromey@sourceware.org
To: src-cvs@sourceware.org
Subject: gdb and binutils branch master updated. 99c1d4518bf2ff230eaa6ee54c08e85f2d6c008e
Date: Mon, 11 Nov 2013 14:42:00 -0000	[thread overview]
Message-ID: <20131111144203.4604.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".

The branch, master has been updated
       via  99c1d4518bf2ff230eaa6ee54c08e85f2d6c008e (commit)
      from  8ca5801b3a05240125a79cd5ba090c98dcc584f8 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=99c1d4518bf2ff230eaa6ee54c08e85f2d6c008e

commit 99c1d4518bf2ff230eaa6ee54c08e85f2d6c008e
Author: Tom Tromey <tromey@redhat.com>
Date:   Mon Nov 11 07:35:57 2013 -0700

    fix "tkill" check
    
    An earlier patch removed the check for "syscall" since the results
    were not used in the C code.  However, the result was used, via the
    cache variable, elsewhere in configure.
    
    This patch fixes the problem by checking for "syscall" at the point at
    which HAVE_TKILL_SYSCALL is defined.
    
    2013-11-11  Tom Tromey  <tromey@redhat.com>
    
    	* config.in, configure: Rebuild.
    	* configure.ac (HAVE_TKILL_SYSCALL): Check for "syscall".

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog    |    5 +++++
 gdb/configure    |    7 ++++++-
 gdb/configure.ac |    6 ++++--
 3 files changed, 15 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
gdb and binutils


                 reply	other threads:[~2013-11-11 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20131111144203.4604.qmail@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=src-cvs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).