From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Pier-Hugues Pellerin <ph@heykimo.com>
Cc: help-guix@gnu.org
Subject: Re: Problem when packaging Avizo
Date: Wed, 16 Mar 2022 10:52:34 -0400 [thread overview]
Message-ID: <87mthqar0t.fsf@gmail.com> (raw)
In-Reply-To: <CA+RyfLm1r0vS9y2pPOug4G+206oUjLZWf7dac3QFA1GcdAxNMA@mail.gmail.com> (Pier-Hugues Pellerin's message of "Tue, 8 Mar 2022 11:53:00 -0500")
Hi Pier-Hugues,
Pier-Hugues Pellerin <ph@heykimo.com> writes:
> 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?
I've tested your definition, and it seems the problem is unrelated to
the suggested bug report after all. The issue appears to be adding the
current directory (presumably of your guix checkout) to the load path
with 'L .'; this somehow interferes with Guix's own loading/discovery
mechanism and fails with:
--8<---------------cut here---------------start------------->8---
guix build: warning: failed to load '(build-aux build-self)':
no code for module (build-aux build-self)
./build-aux/build-self.scm:19:0: warning: module name (build-self) does not match file name 'build-aux/bu'
hint: File `./build-aux/build-self.scm' should probably start with:
(define-module (build-aux build-self))
--8<---------------cut here---------------end--------------->8---
One way out would be to move your package to somewhere else:
--8<---------------cut here---------------start------------->8---
mkdir -p /tmp/avizo
mv avizo.scm /tmp/avizo
$ guix build -L /tmp/avizo avizo
/gnu/store/kv6ycqqxv2xqq3kxa9lmv9aczravs5cp-avizo-1.2
--8<---------------cut here---------------end--------------->8---
Alternatively, you could return the package object at the end of your
avizo.scm file, then build it more simply with:
--8<---------------cut here---------------start------------->8---
$ guix build -f avizo.scm
/gnu/store/kv6ycqqxv2xqq3kxa9lmv9aczravs5cp-avizo-1.2
--8<---------------cut here---------------end--------------->8---
I hope that helps!
Thanks,
Maxim
next prev parent reply other threads:[~2022-03-16 15:17 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
2022-03-16 14:52 ` Maxim Cournoyer [this message]
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=87mthqar0t.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=ph@heykimo.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).