From: Pier-Hugues Pellerin <ph@heykimo.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Problem when packaging Avizo
Date: Fri, 25 Mar 2022 15:26:34 -0400 [thread overview]
Message-ID: <CA+RyfL=FvhBZ7RM4iB8hMrKPTN_rkgNaKV6wcjhJuDTMo3QXMg@mail.gmail.com> (raw)
In-Reply-To: <87mthqar0t.fsf@gmail.com>
Hello,
Thanks for your reply, work got in the way of fun and I didn't have time to
reply.
I've run two different machines: a laptop and a desktop, I've copied the
avizo file on the desktop
and I was able to build it without any changes or issues using the same
command and similar directory structure.
I don't know if it's related or not, but when I tried to build the package
on my laptop my desktop machine was down and I do use it as a substitute, I
believe I've seen errors or warnings but I didn't pay attention to it. I
can try later this weekend to reproduce it.
I am going to make a patch adding avizo.
Thanks everyone.
On Wed, Mar 16, 2022 at 10:52 AM Maxim Cournoyer <maxim.cournoyer@gmail.com>
wrote:
> 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
>
--
ph,
http://heykimo.com
prev parent reply other threads:[~2022-03-25 19:33 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
2022-03-25 19:26 ` Pier-Hugues Pellerin [this message]
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+RyfL=FvhBZ7RM4iB8hMrKPTN_rkgNaKV6wcjhJuDTMo3QXMg@mail.gmail.com' \
--to=ph@heykimo.com \
--cc=help-guix@gnu.org \
--cc=maxim.cournoyer@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.
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).