Hello Carl,
Carl Dong skribis:
> I have my manifest.scm here:
> https://github.com/dongcarl/bitcoin/blob/2019-06-guix-channels-and-inferiors/contrib/guix/manifest.scm,
> and it references the aforementioned Guix channel.
This one appears to work for me (I interrupted it before it was done
compi
Hi Julien,
Julien Lepiller skribis:
> Le 26 juillet 2019 01:03:08 GMT+02:00, "Ludovic Courtès" a
> écrit :
[...]
>>;; In 0.15.0+ we'd create ~/.config/guix/current-[0-9]*-link symlinks.
>>Move
>> ;; them to %PROFILE-DIRECTORY.
>> (unless (string=? %profile-directory
>> (dirna
Hello Jakob,
zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) skribis:
> I believe there is an issue with 'lower-gexp'. Running the following
> snippet to lower a G-Expression for "i686-linux" yields output that
> references store paths built for x86_64. In this case, the Guile
> interpreter us
Hello!
Ludovic Courtès skribis:
> $ guix build guile-gcrypt --with-commit=guile-gcrypt=v1.0.0
> updating checkout of 'https://notabug.org/cwebber/guile-gcrypt.git'...
> guix build: error: cannot fetch commit v1.0.0 from
> https://notabug.org/cwebber/guile-gcrypt.git: unable to parse OID - conta
Hi Ludo,
Ludovic Courtès writes:
> Note: #:target must be a “GNU triplet” like “arm-linux-gnueabihf”, not
> a system type like “i686-linux”.
Thanks, is 'nix-system->gnu-triplet' the suggested way of obtaining the
triplet for a system?
> That’s because the Guile used here comes from the #:guile
I think I just encountered the same bug today. I got stuck at some
completely irrelevant kernel message in the boot screen. Couldn't
switch to TTY, nada. I worked around it by adding
> modprobe.blacklist=amdgpu
To the kernel parameters in grub. But the graphical installer still
didn't work becaus
Hi,
so I've got a new drive and installed Guix (from the iso from the homepage) on
it.
Then I ran guix pull.
Then I installed gcc-toolchain and tried to compile the following program:
int main() {
return 42;
}
using
gcc a.c
but I get:
ld: cannot find crt1.o: No such file or direc
zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) skribis:
> Changing it to the following:
>
> #+BEGIN_SRC scheme
> (lower-gexp exp
> #:system "i686-linux"
> #:target "i686-unknown-linux-gnu"
> #:guile-for-build #f)
> #+END_SRC
>
> The Guile used is still a 64-
Hi Florian,
"pelzflorian (Florian Pelz)" skribis:
> On Fri, Jul 26, 2019 at 01:04:40AM +0200, Ludovic Courtès wrote:
>> What about adding a few words under “Hardware Considerations”?
Oops, I hadn’t seen your patch when I replied.
> While my patch before addresses AMD-specific tweaks in the man
Could you please try to reproduce using the example I provided? The derivation
itself is handled appropriately, but its references are not.
On July 26, 2019 11:28:11 AM EDT, "Ludovic Courtès" wrote:
>zerodaysford...@sdf.lonestar.org (Jakob L. Kreuze) skribis:
>
>> Changing it to the following:
>
Apologies, I should clarify -- the Guile for the S-Expression appears to be
fine, but the Guile referenced in the shebang of the ungexp'd program-file does
not reflect the system.
On July 26, 2019 11:37:20 AM EDT, "Jakob L. Kreuze"
wrote:
>Could you please try to reproduce using the example I
Hmm,
$ guix environment --ad-hoc gcc-toolchain
makes it work in there.
Maybe I forgot to actually reboot? brb...
pgpzq41JHNgos.pgp
Description: Digitale Signatur von OpenPGP
I was receiving X.509 certificate errors when attempting to run `guix
download`. After investigating, I found that it was because my
`SSL_CERT_DIR` environmental variable had two paths separated by a
colon. The two paths were actually the same. After removing the second
path, `guix download` began
Hi all,
I did some more digging, and have included a git-bisect log, the -info-dir.drv,
and -info-dir-builder here:
https://gist.github.com/dongcarl/0a305badf20c9b5cfae738147ca416af
Please let me know if I can provide more information.
Cheers,
Carl Dong
cont...@carldong.me
"I fight for the user
On Fri, Jul 26, 2019 at 05:56:23PM +0200, Ludovic Courtès wrote:
> "pelzflorian (Florian Pelz)" skribis:
> > While my patch before addresses AMD-specific tweaks in the manual
> > under Hardware Considerations, it is not enough if on the *download
> > page* Guix is claimed to run on “an i686, x86_6
Hello everyone,
I found a bug on the Guix installer.
GuixSD Installer freezes my UEFI-only PC, image was successfully verified over
gpg.
I have a Trekstor Surfbook A13B running Parabola (so other installers/distros
work fine)
Installer works on other PCs, so the installer is not corrupt.
I would
"Jakob L. Kreuze" skribis:
> Apologies, I should clarify -- the Guile for the S-Expression appears to be
> fine, but the Guile referenced in the shebang of the ungexp'd program-file
> does not reflect the system.
Got it now. This is fixed by 2e8cabb8d630a8423e2e5a3bf150c1c0310b945d.
Thanks!
17 matches
Mail list logo
