public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: David Edelsohn <dje.gcc@gmail.com>,
Sergio Durigan Junior <sergiodj@redhat.com>,
gdb-testers@sourceware.org
Subject: Re: Missing packages on GDB Buildbot hosts
Date: Thu, 21 Jan 2016 18:46:00 -0000 [thread overview]
Message-ID: <1453401980.7711.111.camel@klomp.org> (raw)
In-Reply-To: <m3zivzhslv.fsf@oc1027705133.ibm.com>
On Thu, 2016-01-21 at 16:14 +0100, Andreas Arnez wrote:
> It seems to me that guile and libcc1-0 are also missing. For guile I
> believe you need guile-2.0-dev.
guilde-2.0-dev now installed on both setups.
But I don't know what libcc1-0 is, sorry. Do you have a bit more
information about it?
Thanks,
Mark
next prev parent reply other threads:[~2016-01-21 18:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 16:27 [binutils-gdb] Fix display of RL78 MOVW instructions that use the stack pointer sergiodj+buildbot
2016-01-14 16:27 ` Failures on Debian-s390x-m64, branch master sergiodj+buildbot
2016-01-14 16:27 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-01-14 16:28 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-14 16:35 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-01-15 14:38 ` Missing packages on GDB Buildbot hosts Andreas Arnez
2016-01-15 15:33 ` David Edelsohn
2016-01-17 12:11 ` Mark Wielaard
2016-01-21 15:15 ` Andreas Arnez
2016-01-21 18:46 ` Mark Wielaard [this message]
2016-01-21 19:00 ` Andreas Arnez
2016-01-21 18:20 ` Andreas Arnez
2016-01-21 18:47 ` Mark Wielaard
2016-01-27 15:15 ` Mark Wielaard
2016-01-29 17:24 ` Andreas Arnez
2016-02-08 10:02 ` Mark Wielaard
2016-01-14 16:37 ` Failures on Fedora-i686, branch master sergiodj+buildbot
2016-01-14 16:37 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2016-01-14 16:40 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2016-01-14 16:40 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2016-01-14 16:44 ` Failures on Debian-i686, " sergiodj+buildbot
2016-01-14 16:54 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2016-01-14 16:55 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-14 17:03 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot
2016-01-14 17:04 ` Failures on AIX-POWER7-plain, " sergiodj+buildbot
2016-01-14 17:08 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2016-01-14 17:12 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-14 17:28 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot
2016-01-14 17:35 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2016-01-14 17:45 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-14 17:51 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
2016-01-15 15:15 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot
2016-01-15 16:32 ` Failures on RHEL-s390x-m64, " sergiodj+buildbot
2016-01-15 16:40 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
2016-01-15 16:48 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
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=1453401980.7711.111.camel@klomp.org \
--to=mark@klomp.org \
--cc=arnez@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gdb-testers@sourceware.org \
--cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).