unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pier-Hugues Pellerin <ph@heykimo.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Problem when packaging Avizo
Date: Tue, 8 Mar 2022 11:53:00 -0500	[thread overview]
Message-ID: <CA+RyfLm1r0vS9y2pPOug4G+206oUjLZWf7dac3QFA1GcdAxNMA@mail.gmail.com> (raw)
In-Reply-To: <87pmmw67k9.fsf@gnu.org>

Hello Ludo,

It does happen every time, I've added the parameters '--max-jobs=1
--no-offload'
and I get the same results with the same stack trace. Anything else I could
give you, should
I open a bug report?

Thanks
ph


On Tue, Mar 8, 2022 at 5:51 AM Ludovic Courtès <ludo@gnu.org> wrote:

> Hi Pier-Hugues,
>
> Pier-Hugues Pellerin <ph@heykimo.com> skribis:
>
> > In guix/status.scm:
> >    645:15  4 (_ (build-log 4365 "[1/11] Generating avizo-resource…") #)
> >    179:23  3 (update-build #<<build-status> building: () downloadin…> …)
> > In ice-9/boot-9.scm:
> >   1685:16  2 (raise-exception _ #:continuable? _)
> >   1685:16  1 (raise-exception _ #:continuable? _)
> >   1685:16  0 (raise-exception _ #:continuable? _)
> >
> > ice-9/boot-9.scm:1685:16: In procedure raise-exception:
> > In procedure struct-vtable: Wrong type argument in position 1 (expecting
> > struct): #f
>
> It looks like you hit a genuine bug, similar to
> <https://issues.guix.gnu.org/43518>.
>
> Does it happen every time you try to build this package?
>
> Does it happen when you build with ‘--max-jobs=1 --no-offload’?
>
> Thanks in advance,
> Ludo’.
>


-- 
ph,
http://heykimo.com

  reply	other threads:[~2022-03-08 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03  2:45 Problem when packaging Avizo Pier-Hugues Pellerin
2022-03-08 10:51 ` Ludovic Courtès
2022-03-08 16:53   ` Pier-Hugues Pellerin [this message]
2022-03-16 14:52     ` Maxim Cournoyer
2022-03-25 19:26       ` Pier-Hugues Pellerin

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=CA+RyfLm1r0vS9y2pPOug4G+206oUjLZWf7dac3QFA1GcdAxNMA@mail.gmail.com \
    --to=ph@heykimo.com \
    --cc=help-guix@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.
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).