Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb@sourceware.org>
Subject: Re: Fwd: Your commit 'Sync Makefile.tpl with GCC' broke GDB
Date: Wed, 15 Jul 2015 18:59:00 -0000	[thread overview]
Message-ID: <87a8uxw8k8.fsf@redhat.com> (raw)
In-Reply-To: <CAMe9rOp+CbrF5HxrRwnKb5QeWAgZyFxXJRabf2KfVPQVi-K_rA@mail.gmail.com>	(H. J. Lu's message of "Tue, 14 Jul 2015 16:09:12 -0700")

On Tuesday, July 14 2015, H. J. Lu wrote:

> GDB BuildBot is broken:

This has been fixed now.  Sorry about the noise.

> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: Resource temporarily unavailable
>
>
> ---------- Forwarded message ----------
> From:  <sergiodj+buildbot@redhat.com>
> Date: Tue, Jul 14, 2015 at 4:05 PM
> Subject: Your commit 'Sync Makefile.tpl with GCC' broke GDB
> To: "H.J. Lu" <hjl.tools@gmail.com>
>
>
> Hello there,
>
> Your commit:
>
>         Sync Makefile.tpl with GCC
>         22121df01ff9247b3cb272f52632848f9631f80f
>
> broke GDB.  Please fix it, or the GDB gods will get you.
>
> You can find details of the breakage below.
>
> Cheers,
>
> Your GDB BuildBot.
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
> Buildslave:
>         fedora-x86-64-1
>
> Full Build URL:
>         <http://gdb-build.sergiodj.net/builders/Fedora-i686/builds/1445>
>
> Commit(s) tested:
>         22121df01ff9247b3cb272f52632848f9631f80f
>
> Author(s) (in the same order as the commits):
>         H.J. Lu <hjl.tools@gmail.com>
>
> Testsuite log (gdb.sum and gdb.log) URL(s):
>         <Error fetching commit ID for 22121df01ff9247b3cb272f52632848f9631f80f>
>
> *** Failed to configure GDB. ***
> ============================
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: retry: No child processes
> ../binutils-gdb/configure: fork: Resource temporarily unavailable
> ============================
>
>
>
> -- 
> H.J.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


      reply	other threads:[~2015-07-15 18:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1ZF9Gp-000060-IF@kwanyin.sergiodj.net>
2015-07-14 23:09 ` H.J. Lu
2015-07-15 18:59   ` Sergio Durigan Junior [this message]

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=87a8uxw8k8.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=hjl.tools@gmail.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