unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Reza Housseini <reza.housseini@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Strange error when adding module gnu/packages/engineering
Date: Sat, 08 Apr 2023 15:29:12 -0400	[thread overview]
Message-ID: <87r0surx4n.fsf@gmail.com> (raw)
In-Reply-To: <8a28046e-196c-d68f-6408-cd5adce3b7f8@gmail.com> (Reza Housseini's message of "Wed, 22 Mar 2023 21:36:27 +0100")

Hi Reza,

Reza Housseini <reza.housseini@gmail.com> writes:

>> Thinking more about it, since this a new module, there shouldn't be any
>> recursive dependency problem.
>> Probably you are missing some #:use-module at the top of your new
>> module.  I'd start minimal and see what works, and evaluate the package
>> at the REPL for more accurate messages perhaps.
>
> I could boil it down a bit: when commenting out `#:use-module (gnu
> packages commencement)` in gnu/packages/engineering.scm the error
> vanishes but the freehdl package in module engineering does not build
> anymore (due to gcc-toolchain missing).
> Is there a cycle inside module commencement? Seems really strange to me?

That's a tell sign of a Guile module top-level circular dependency.  I
think the usual way to work around that is usually to resort to use (@
(gnu packages toolchain) gcc-toolchain) in place of the input, so that
importing it at the top level is not necessary (the evaluation of inputs
is delayed, eliminating the cycle).

I hope that helps,

-- 
Thanks,
Maxim


  reply	other threads:[~2023-04-08 19:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 14:38 Strange error when adding module gnu/packages/engineering Reza Housseini
2023-01-05  2:34 ` Csepp
2023-01-06 12:13   ` Reza Housseini
2023-01-05 16:02 ` Maxim Cournoyer
2023-01-06 12:14   ` Reza Housseini
2023-01-06 17:42     ` Maxim Cournoyer
2023-01-07  9:05       ` reza.housseini
2023-01-08 20:20       ` Reza Housseini
2023-03-22 20:36       ` Reza Housseini
2023-04-08 19:29         ` Maxim Cournoyer [this message]
2023-01-05 16:52 ` Julien Lepiller
2023-01-06 12:15   ` Reza Housseini

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=87r0surx4n.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=reza.housseini@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).