unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: William ML Leslie <william.leslie.ttg@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>,
	"debian-hppa@lists.debian.org" <debian-hppa@lists.debian.org>
Subject: Re: Removal of hppa support
Date: Sun, 26 Jan 2020 14:34:11 +0100	[thread overview]
Message-ID: <bb945a75-c6dc-cabd-1948-0f9793d6c6d6@physik.fu-berlin.de> (raw)
In-Reply-To: <CAHgd1hFBTzTYgGXVkZ94vf5t+feBD3C7orKYWese4+ne5LxO9w@mail.gmail.com>

On 1/26/20 1:21 PM, William ML Leslie wrote:
> The only thing Wingo wrote publicly about this seems to be:
> 
>> I ported some of the existing GNU Lightning backends over to Lightening... I deleted the backends for Itanium, HPPA, Alpha, and SPARC; they have no Debian ports and there is no situation in which I can afford to do QA on them. [0]
> 
> I haven't pushed to see what conditions would need to change to make
> JIT support on these architectures desirable for the core developers.
> Thoughts, Andy? Ludo?

They have no Debian ports?

> https://cdimage.debian.org/cdimage/ports/2019-07-16/

> https://buildd.debian.org/status/package.php?p=guile-2.2&suite=sid

It would have been nice if anyone from upstream had reached out to us.

The lack of communication is rather disappointing.

>> Debian (and NetBSD) still support hppa perfectly fine so the code is actually
>> being compiled, used and test-run. And guile has been building fine on Debian/hppa.
>>
>> Access to hppa machines for testing and bug fixing is also available through Debian.
>>
>>> As an ia64 user, i'm a bit sad that we lost jit too - but i don't run any
>>> performance-sensitive guile jobs on that system.
>>
>> Are you using Debian's ia64 port? We recently resurrected it ;).
>>
> 
> Yes I am - I saw that.  Thank you for all your hard work on it!

You're welcome. We're always looking for more contributors.

> I was recently trying to figure out the issue with the vim-tiny tests
> and I broke my ssh access: I failed to realise why setting up a chroot
> was so important when you only have access to Sid.  It is quite a bit
> of work to get iLO access in my office so I've been putting it off
> until I have a couple of days clear to look into it, and I've been
> working on replacing the ancient tech needed to speak to early iLO
> cards (a java6 browser plugin and old SSL with no hostname
> verification).

Yeah. The vim testsuite issue affects multiple architectures.

> It's not my first debian-ports fun either - I ran a hurd-i386 box for
> over a decade without issue.

Nice.

Adrian

-- 
 .''`.  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



  reply	other threads:[~2020-01-26 13:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 19:32 Removal of hppa support John Paul Adrian Glaubitz
2020-01-25 19:48 ` John David Anglin
2020-01-25 21:59   ` Helge Deller
2020-01-26  5:46 ` William ML Leslie
2020-01-26  6:19   ` William ML Leslie
2020-01-27 15:46     ` Andy Wingo
2020-01-27 17:30       ` Stefan Monnier
2020-01-27 21:41         ` tomas
2020-02-04 11:02       ` John Paul Adrian Glaubitz
2020-02-04 11:23         ` Andy Wingo
2020-02-04 11:41           ` John Paul Adrian Glaubitz
2020-01-26  9:50   ` John Paul Adrian Glaubitz
2020-01-26 12:21     ` William ML Leslie
2020-01-26 13:34       ` John Paul Adrian Glaubitz [this message]
2020-01-26 15:50         ` John David Anglin

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bb945a75-c6dc-cabd-1948-0f9793d6c6d6@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=debian-hppa@lists.debian.org \
    --cc=guile-devel@gnu.org \
    --cc=william.leslie.ttg@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).