From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Anthony Green <green@redhat.com>
Cc: Anthony Green <green@moxielogic.com>,
Matthias Klose <doko@ubuntu.com>,
libffi-discuss <libffi-discuss@sourceware.org>,
Debian m68k <debian-68k@lists.debian.org>,
debian-superh@lists.debian.org
Subject: Re: libffi 3.3 release candidate 1
Date: Thu, 31 Oct 2019 22:16:00 -0000 [thread overview]
Message-ID: <bfe296c6-5e38-642c-c13a-cd481a80bb8e@physik.fu-berlin.de> (raw)
In-Reply-To: <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com>
Hi!
On 10/31/19 9:47 PM, Anthony Green wrote:
> I was using that one, but I haven't been able to connect to it
> today, so I took it out for now. I'll try again later.
The machine is up and reachable:
glaubitz@zlogin2:~> ssh gcc202.fsffrance.org
Linux gcc202 4.19.0-5-sparc64-smp #1 SMP Debian 4.19.37-6 (2019-07-18) sparc64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Oct 31 19:05:52 2019 from XXX.XXX.XXX.XXX
glaubitz@gcc202:~$
But there are certain hosts from which access doesn't work. I think Anatoly
Pugachev who set up the LDOM can probably figure out what's wrong.
> libffi doesn't see a ton of activity, so I predict a light load...
> but this an experiment and we'll see how it goes!
For m68k, qemu-system-m68k can be used these days to set up a Debian/m68k
system [1]. Adding one of my SuperH (sh4) systems to the GCC compile
farm is also on my TODO list but I just don't have the time at the moment :(.
FWIW, if you need access to a certain architecture, please let me know.
Adrian
> [1] https://wiki.debian.org/M68k/QemuSystemM68k
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2019-10-31 22:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 11:17 Anthony Green
2019-10-25 10:08 ` Matthias Klose
2019-10-25 10:29 ` John Paul Adrian Glaubitz
2019-10-25 14:41 ` Andreas Schwab
2019-10-25 14:44 ` John Paul Adrian Glaubitz
2019-10-25 18:32 ` Andreas Schwab
2019-10-25 18:37 ` John Paul Adrian Glaubitz
2019-10-25 19:04 ` Andreas Schwab
2019-10-25 19:07 ` John Paul Adrian Glaubitz
2019-10-26 11:35 ` Anthony Green
2019-10-26 12:54 ` Anthony Green
2019-10-31 19:49 ` Anthony Green
2019-10-31 20:32 ` John Paul Adrian Glaubitz
[not found] ` <CAAs=koj3HU08uxx36809NcPYe33xvEjUDsLwJc_9R8V4tbr9Zg@mail.gmail.com>
2019-10-31 22:16 ` John Paul Adrian Glaubitz [this message]
2019-11-01 8:01 ` John Paul Adrian Glaubitz
2019-11-01 22:24 ` John Paul Adrian Glaubitz
2019-11-08 9:21 ` Matthias Klose
2019-11-08 14:28 ` Anthony Green
2019-11-09 16:04 ` Matthias Klose
2019-11-09 17:46 ` Anthony Green
2019-11-10 16:22 ` Matthias Klose
2019-11-26 8:39 ` Matthias Klose
2019-11-26 23:25 ` Anthony Green
2019-11-27 7:54 ` Matthias Klose
2019-11-27 9:28 ` Anthony Green
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=bfe296c6-5e38-642c-c13a-cd481a80bb8e@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=debian-superh@lists.debian.org \
--cc=doko@ubuntu.com \
--cc=green@moxielogic.com \
--cc=green@redhat.com \
--cc=libffi-discuss@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).