unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Patterson <ajpatter@uwaterloo.ca>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Pierre Neidhardt <ambrevar@gmail.com>
Subject: Re: [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist.
Date: Mon, 27 Aug 2018 03:24:29 -0400	[thread overview]
Message-ID: <20180827032429.064d878b@uwaterloo.ca> (raw)
In-Reply-To: <87k1ofncss.fsf@gnu.org>

Hi all,

There are a few different messages in this thread that I could reply
to, but I'll do my best to address them all here.

On Fri, 24 Aug 2018 14:56:19 +0200
ludo@gnu.org (Ludovic Courtès) wrote:

> Hi Pierre,
> 
> Pierre Neidhardt <ambrevar@gmail.com> skribis:
> 
> > I have no clue what this SWANK-BACKEND is.  I can find
> > SWANK/BACKEND in the source however.  Maybe my misunderstanding of
> > Common Lisp...
> >
> > Any clue?  
> 
> I’m clueless ;-) but I’ve Cc’d one of our local CL experts.
> Any ideas, Andy?

Expert is a bit strong, but I'll try my best.  I wasn't able to dive
deep into this particular issue this weekend, but I did try to bring
myself back up to speed by rebuilding the currently upstreamed CL
packages as well as my local additions.  The good news here is that
I've finally found out why our slynk package doesn't build on sbcl, and
that might be relevant to this problem.

As for the initial error - it looks like it's because swank's system
definition file only compiles swank-loader, which I guess is because it
wants to use that loader to load the rest of the system.  As a result
the swank-backend package never gets added to the built swank package.

The PR linked in the upstream bug report looks like it addresses that
issue by adding all of the source files to the system's components.
The log listed in the report when using that PR doesn't show the full
details - but I've just found out that some warnings are being treated
as errors by sbcl.  It might be that there's some warning shown earlier
on which is causing the reported compilation failure, despite the fact
that it's reported as a benign-seeming warning.  I haven't been able
to figure out whether or not this is a guix-specific problem.

I haven't forgotten that I'd promised to deliver some build system
improvements a while back - I've gotten that all formatted into commits
now so I'll try to send that in later this week if I can find time.

> 
> Ludo’.

Hoping that helps,

--
Andy

  parent reply	other threads:[~2018-08-27  8:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-23 16:24 [Next browser] Common Lisp: mgl-pax: Package SWANK-BACKEND does not exist Pierre Neidhardt
2018-08-24 10:32 ` Pierre Neidhardt
2018-08-24 12:56 ` Ludovic Courtès
2018-08-24 13:15   ` Pierre Neidhardt
2018-08-27  7:24   ` Andy Patterson [this message]
2018-08-27  7:42     ` Pierre Neidhardt
2018-08-28  7:36       ` Andy Patterson
2018-08-28 19:18         ` Pierre Neidhardt
2018-08-29  6:18           ` Andy Patterson
2018-09-02 16:59             ` Pierre Neidhardt
2018-09-08 21:49               ` Andy Patterson
2018-09-11 21:01                 ` Pierre Neidhardt
2018-09-11 21:17                   ` Leo Famulari
2018-09-12  8:10                     ` Pierre Neidhardt

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20180827032429.064d878b@uwaterloo.ca \
    --to=ajpatter@uwaterloo.ca \
    --cc=ambrevar@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).