unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Reza Housseini <reza.housseini@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: Strange error when adding module gnu/packages/engineering
Date: Fri, 6 Jan 2023 13:13:18 +0100	[thread overview]
Message-ID: <b91c306d-17f3-8cf4-bcdb-23f44d14d5c0@gmail.com> (raw)
In-Reply-To: <865ydlvh2j.fsf@riseup.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 717 bytes --]

> Just to rule out the obvious things:
> did you perform a clean rebuild?
> ie.: make clean, or git clean -fxd, the bootstrap, configure, make
> 
> Also could you send the patch containing your additions?
> 
> My guess is that the Guix feature that auto-suggests what module to
> import when there is an unbound variable error is matching the list
> caught from the exception but its patterns don't cover it.  Maybe it has
> an extra element or something?
> 
> Also, getting the commit from git that yours builds on might be helpful.

Thanks for the advice, will try it out!

-- 
Reza Housseini

This message is signed with my GnuPG key:

     C0F3 0812 9AF2 80F4 0830 C2C1 C375 C6AF 0512 5C52


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 15557 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-01-06 12:14 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 [this message]
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
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=b91c306d-17f3-8cf4-bcdb-23f44d14d5c0@gmail.com \
    --to=reza.housseini@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=raingloom@riseup.net \
    /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).