I am seeing the same symptoms as reported in #49102.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49102
$ guix describe
Generation 17 May 06 2022 18:17:56 (current)
guix 0e94295
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 0e9429544fd737079b9c15
I am seeing the following warning running Guix on a foreign distribution:
$ man man
man: can't set the locale; make sure $LC_* and $LANG are correct
The errors disappear when I manually configure GUIX_LOCPATH, as
described at
https://guix.gnu.org/manual/devel/en/html_node/Application-Set
Hi,
I would like to use both gcc-toolchain (for compiling) and
clang-toolchain (for the tools) in the same profile, which as
previously discussed requires the gcc version to match that used to
build clang, llvm, etc. So to use a newer gcc-toolchain I need to
upgrade the default gcc version.
When
On Tue, Sep 27, 2022 at 12:14 PM jgart wrote:
>
> guix upgrade * or guix upgrade '*' don't work for me :(
The shell looks to be running filename expansion [0] in your current
directory. Try `guix upgrade .` or simply `guix upgrade`.
[0] https://www.gnu.org/software/bash/manual/html_node/Filename
On Fri, Jan 20, 2023 at 7:18 AM Simon Tournier wrote:
>
> > Maybe then add an option to guix pack to accept optional name? And if not
> > provided, fall back to manifest->friendly-name.
>
> …yes, I agree. It could be nice to be able to directly name the image.
> However, this would mean that the
Guix,
The icecat package description currently includes the warning:
"WARNING: IceCat 102 has not yet been released by the upstream IceCat
project. This is a preview release, and does not currently meet the
privacy-respecting standards of the IceCat project."
Why? The icecat project states [1]
On Mon, Feb 13, 2023 at 9:51 AM Gottfried wrote:
>
> Hi,
> since many weeks the two packages
>
> rust-sha2 and tealdeer fail to be build during upgrading.
>
> Do only I have this problem?
No, though at least for tealdeer the issue has been previously reported.
> or is something wrong with those
Having failed a year ago to build the latest gcc and latest clang
together using "with-c-toolchain", the following succeeds using
"package-input-rewriting/spec".
My current issue is that glibc@2.33 on master fails to build with
gcc@12 ("cc1: all warnings being treated as errors") and my attempts
t
On Thu, Feb 23, 2023 at 1:30 PM Greg Hogan wrote:
>
> Having failed a year ago to build the latest gcc and latest clang
> together using "with-c-toolchain", the following succeeds using
> "package-input-rewriting/spec".
>
> My current issue is that glibc@2.
Hi Guix,
>From my x86_64 machine I am executing offload builds targeting an
aarch64 machine:
$ guix build --system=aarch64-linux --manifest=manifest.scm
Several packages do not build for aarch64 and need to be filtered out.
%current-target-system is #f as these are offload builds not cross
compi
On Tue, Mar 7, 2023 at 10:56 AM Ludovic Courtès wrote:
>
> But then again, I wonder why you end up rebuilding glibc. For example,
> this would only rebuild LLVM and everything above:
>
> --8<---cut here---start->8---
> $ guix build clang --with-c-toolchain=llvm
On Tue, May 23, 2023 at 1:23 PM Soren Stoutner via wrote:
>
> I just tried it again with 6783f558fa2bcbc662e021e1b3bf502c64706177 and
> had the same issue.
proot-static fails to build. The issue has been reported upstream.
https://github.com/proot-me/proot/issues/352
The recent 5.4.0 release f
mentions, it
> works on the build farm.
>
> Le 24 juillet 2023 10:17:54 GMT+02:00, Andreas Enge a écrit
> :
> >Hello Greg,
> >
> >Am Thu, Jul 20, 2023 at 11:32:40AM -0400 schrieb Greg Hogan:
> >> I have tried everything I could think of but have been unable to
On Thu, Nov 2, 2023 at 11:26 AM Suhail wrote:
> Perhaps not all. The thing that sets the "check" phase (#:tests?) apart
> from the rest is that it's an identity transform with a
> side-effect. i.e., it simply reports on the state of its input (i.e.,
> the build artifact) leaving the build artifact
On Wed, Mar 13, 2024 at 1:49 AM Pan Xie wrote:
>
> Hello
>
> I find this issue on both GuixSD and guix package manager on ArchLinux.
> The problem is `man -k' can not find manpages installed by guix. I
> believe the issue is caused by `mandb' does not include guix packages'
> man pages when genera
On Sun, Mar 31, 2024 at 5:39 PM Spencer Skylar Chan
wrote:
>
> Dear Guix,
>
> How do I run guix size with a manifest? Most guix shell commands use -m
> for a manifest file, but guix size uses -m for map-file. Right now I'm using
>
> grep -F \" manifest.scm | cut -d \" -f 2 | xargs guix size
>
> bu
The "build daemon can offload derivation builds to other machines
running Guix" [1], except source derivations look to always be fetched
from the host machine.
Would it be feasible to optionally allow source derivations to be
fetched on an offload machine for cases where the host machine does
not
On Fri, Sep 20, 2024 at 9:47 AM Reza Housseini wrote:
>
> Hi Guixers
>
> From guix shell I can call
>
> guix shell -D -f guix.scm
>
> Now I want to pack those into a container with guix pack, but there is
> no equivalent command there, how would I achieve this, is there an
> expression I could u
On Wed, Mar 5, 2025 at 7:48 AM Guillaume Le Vaillant wrote:
[...]
> You could also use btrfs instead of ext4 as file system; and if you
> activate compression, it divides the actual size taken by the Guix store
> by 3 (approximately).
With the default zstd compression I am seeing a ratio of 2. Is
On Fri, Mar 21, 2025 at 9:53 AM aneris via wrote:
>
> Hello Guix,
>
> I have been trying to setup a C++ development environment in Guix,
> however clangd has been very annoying.
>
> The simple hello world in C++
>
> ```
>
> #include
>
> int main() {
>
>std::cout << "Hello World";
>
> }
>
> ``
20 matches
Mail list logo
