From: Alex Kost <alezost@gmail.com>
To: Quilro Ordonez <quiliro@riseup.net>
Cc: lxo@fsfla.org, 23409@debbugs.gnu.org
Subject: bug#23409: unable to load free firmware
Date: Thu, 05 May 2016 00:33:09 +0300 [thread overview]
Message-ID: <87r3dhv78q.fsf@gmail.com> (raw)
In-Reply-To: <c1f9add0862382112ed11b91baa8a1ab@riseup.net> (Quilro Ordonez's message of "Wed, 04 May 2016 13:30:23 -0500")
Quilro Ordonez (2016-05-04 21:30 +0300) wrote:
> Thank you very much for your help Alex. Below is my report.
>
> El 2016-05-04 04:10, Alex Kost escribió:
>> you can create
>> "/any/directory/you/want/my-guix-packages.scm" file
>
> Downloaded the file and saved it on directory
> /home/quiliro/guix/packages
>
>> After that the following command should build the package:
>>
>> $ GUIX_PACKAGE_PATH=/any/directory/you/want guix build
>> openfwwf-firmware
>
> This is the output:
>
> $ GUIX_PACKAGE_PATH=/home/quiliro/guix/packages guix build
> openfwwf-firmware
> /gnu/store/xcxhd2r2h3iz0721vn6c5wfqkd0r4xc0-openfwwf-firmware-5.2
> $
Great, so as "guix build openfwwf-firmware" succeeds now, you can return
to answering Ludovic's message about modifying
"/sys/module/firmware_class/parameters/path".
>> Also if you add this directory to GUILE_LOAD_PATH, you could use
>> (my-guix-packages) module in any guile code, particularly in your
>> system
>> config
>
> Downloaded quiliro-os.scm and placed it in /home/quiliro/guix
>
>> So add the following to your ~/.bash_profile:
>>
>> export GUIX_PACKAGE_PATH=/any/directory/you/want
>> export GUILE_LOAD_PATH=/any/directory/you/want
>
> Did that.
>
> This is the output of reconfiguring the whole system:
>
> # guix system reconfigure /home/quiliro/guix/quiliro-os.scm
> guix system: error: failed to load 'quilro-os.scm':
> ice-9/boot-9.scm:2867:6: In procedure resolve-interface:
> ice-9/boot-9.scm:2867:6: no code for module (my-guix-packages)
Ahem, did you try "echo $GUILE_LOAD_PATH" before this? I bet it will be
empty, because you export this variable as user, but run "guix system"
command as root.
--
Alex
next prev parent reply other threads:[~2016-05-04 21:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 21:06 bug#23409: unable to load free firmware Quilro Ordonez
2016-04-30 22:43 ` Leo Famulari
2016-05-01 13:19 ` Ludovic Courtès
2016-05-02 13:55 ` Eric Bavier
2016-05-03 8:01 ` Ludovic Courtès
2016-05-03 20:10 ` Quilro Ordonez
2016-05-03 20:45 ` Ludovic Courtès
2016-05-03 21:17 ` Quilro Ordonez
2016-05-03 21:21 ` Quilro Ordonez
2016-05-04 9:10 ` Alex Kost
2016-05-04 18:30 ` Quilro Ordonez
2016-05-04 21:33 ` Alex Kost [this message]
2016-05-04 23:08 ` Quilro Ordonez
2016-05-04 23:13 ` Quilro Ordonez
2016-05-05 8:42 ` Alex Kost
2016-05-11 19:01 ` Quilro Ordonez
[not found] ` <87oa8bzjqg.fsf@gmail.com>
2016-05-12 16:11 ` Quilro Ordonez
2016-05-13 13:25 ` Ludovic Courtès
2016-05-13 21:15 ` Quilro Ordonez
2016-05-14 16:17 ` Alex Kost
2016-11-02 22:19 ` Ludovic Courtès
2017-01-11 22:29 ` Ludovic Courtès
2016-11-04 0:43 ` Quiliro Ordonez
2016-11-04 0:46 ` Quiliro Ordonez
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=87r3dhv78q.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=23409@debbugs.gnu.org \
--cc=lxo@fsfla.org \
--cc=quiliro@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).