unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Théo Tyburn" <theo.tyburn@posteo.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Help Packaging Incudine (Common Lisp)
Date: Sat, 30 Sep 2023 13:31:25 +0000	[thread overview]
Message-ID: <87o7hjg505.fsf@posteo.net> (raw)
In-Reply-To: <75c9147df571ce872f2c0a2c89afce5037d6b9f9.camel@gmail.com>


Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Donnerstag, dem 28.09.2023 um 12:23 +0000 schrieb Théo Tyburn:
>> Oh, it seems I took the WARNING message for an ERROR message.
>> 
>> The error message seems to just be:
>> > Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR in thread #<SB-
>> > THREAD:THREAD tid=21 "main thread" RUNNING
>> >                                                         
>> > {100AFE8113}>:
>> >  COMPILE-FILE-ERROR while
>> >  compiling #<CL-SOURCE-FILE "cl-sndfile" "cffi-sndfile">
>> 
>> No sure what can be done with this.
> Note that this error doesn't tell you where CL would have written the
> compiled file to.
>
> Am Donnerstag, dem 28.09.2023 um 14:21 +0000 schrieb Théo Tyburn:
>> Not sure in what retrying a compilation on the interactive debugger
>> is different from compiling normally. But I need to understand why
>> the retrying of compilation does in order to replicate it without the
>> need of an interactive session.
> I'd hazard a guess that your $HOME is writable in the interactive case
> and not so much during guix build :)
> Well, that still doesn't explain why the compilation fails normally in
> the interactive case, does it?  I think for that you'd have to look up
> uiop/lisp-build:compile-file and see when it raises errors.  Enter
> rubber ducky.

Yes, that's probably the right place to look for hints. Need to find out
where and how compiled files are written.

Thanks


  reply	other threads:[~2023-09-30 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 20:31 Help Packaging Incudine (Common Lisp) Théo Tyburn
2023-09-28 12:23 ` Théo Tyburn
2023-09-29  4:29   ` Liliana Marie Prikler
2023-09-30 13:31     ` Théo Tyburn [this message]
2023-10-22 12:07       ` Guillaume Le Vaillant
2023-10-22 14:15         ` Théo Tyburn
2023-10-23  8:44           ` Guillaume Le Vaillant
2023-10-24 20:25             ` Théo Tyburn
2023-09-28 14:20 ` Théo Tyburn

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=87o7hjg505.fsf@posteo.net \
    --to=theo.tyburn@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=liliana.prikler@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.
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).