unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>, help-guix@gnu.org
Subject: Re: Problems with McCLIM (Common Lisp)
Date: Sun, 06 Sep 2020 09:07:03 +0200	[thread overview]
Message-ID: <87eenfidt4.fsf@ambrevar.xyz> (raw)
In-Reply-To: <dbc8cf60-3a74-a55c-c372-13791f645a56@fastmail.net>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Konrad Hinsen <konrad.hinsen@fastmail.net> writes:

> That sounds good, as does getting rid of ADSF bundles. I have more or 
> less given up on numcl, for example, which fails to compile to a bundle 
> in recent versions but seems to work find via fasls (at least it works 
> fine with quicklisp).

It seems that the Common Lisp community is mostly relying on Quicklisp
and thus rarely, if ever, uses asdf:compile-bundle-op.
The latter has been a source of oddities to me: several times a piece of
code would behave differently between compile-bundle-op and compile-op.
Upstream is almost always relying on compile-op and thus not aware of
the compile-bundle-op issues.

Cheers!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-09-06  7:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13  2:43 Problems with McCLIM (Common Lisp) Ricardo Wurmus
2020-08-13  7:16 ` Pierre Neidhardt
2020-08-13  9:08   ` Guillaume Le Vaillant
2020-09-04 16:37     ` Ricardo Wurmus
2020-09-05  6:57       ` Pierre Neidhardt
2020-09-05  7:20         ` Ricardo Wurmus
2020-09-05  9:49           ` Guillaume Le Vaillant
2020-09-05 17:52         ` Konrad Hinsen
2020-09-06  7:07           ` Pierre Neidhardt [this message]
2020-09-11 14:19             ` Katherine Cox-Buday
2020-09-11 14:40               ` 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=87eenfidt4.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=help-guix@gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    /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).