Re: qutebrowser has no sound
The `qutebrowser' executable is wrapped indeed. Not sure what to do with it. Can anyone else reproduce? -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature
Re: building emacs from tarball inside guix env
1) I would guess that guix environment emacs, looks in the package definition to discover emacs' dependencies. 2) Are you trying to create a custom emacs package? If so, then you might like my jmacs package: https://notabug.org/jbranso/guix-packages/src/master/packages/jmacs.scm 3) I would guess "guix build ". You could have a custom channel that is local to your machine. Any packages in it, take precedent over packages in guix proper. That is to say, that your custom emacs package named "emacs" and is available locally, would be built instead of the "emacs" package in guix. You could also define I personally do this in my ~/.bash_profile #+BEGIN_SRC sh export GUIX_PACKAGE_PATH=/home/joshua/prog/gnu/guix/guix-packages/ #+END_SRC -- Joshua Branson Sent from Emacs and Gnus
Re: Use of `load' in declarative module
I've been having the same issues too. :( I haven't been able to get shepherd user services to work. I hope we can get it fixed. :) -- Joshua Branson Sent from Emacs and Gnus
Cross gcc-toolchain
Hi Guix, I am looking into ghc on ARM and the process seems like it only requires a separate gcc toolchain specified during configure. I have not packaged a gcc-toolchain yet, so I am looking for pointers. Would the gcc toolchain for cross compiling (say, from x86 to aarch64) be as simple as providing the target flag to the various toolchain packages’ configures? Thanks for your help! John
Re: building emacs from tarball inside guix env
Adam Kandur via writes: > 2) what is better way to build sources as they are (from tar, just for > testing, not for packaging)? In simple cases you can use “guix build --with-source=… emacs”, where the argument to “--with-source” is a tarball. -- Ricardo
Re: Use of `load' in declarative module
Joseph LaFreniere writes:
> When attempting to run the code in
> https://guix.gnu.org/en/blog/2020/gnu-shepherd-user-services/, I
> get the following error:
>
> 2020-08-23T22:43:48-0500 .config/shepherd/init.d $ shepherd
> Service root has been started.
> WARNING: Use of `load' in declarative module (#{ g54}#). Add
> #:declarative? #f to your define-module invocation.
This is merely a warning. It is due to a change in Guile 3 that informs
you that certain optimizations are not possible due to the use of load.
You can ignore this.
The module name indicates that this is a *generated* module and not
something you wrote by yourself.
--
Ricardo
