> But anyway, the normal way to use Texinfo is like TeX: you use ASCII
> quotes, and it does the right thing (see the PDF output, and the Info
> output if you’re using makeinfo 5.x.)
I know, I was talking about the output of 'makeinfo --html'. I'm using
4.13.
> There seems to be some paragraph f
Nikita Karetnikov skribis:
>> The problem of ‘CROSS_LIBRARY_PATH’ being ignored is fixed by commit 248d08e.
>> Took me a bit of browsing to find out where that happens in GCC.
>
> That's great, thanks.
>
> Are there any other issues? Have you tried to cross-compile anything
> non-trivial?
Not y
Hello!
l...@gnu.org (Ludovic Courtès) skribis:
> Commit 827d289 of the ‘core-updates’ branch adds cross-base.scm, which
> builds a cross tool chain.
>
> So if you type ‘guix build gcc-cross-mips64el-linux-gnu’, you get a
> cross-compiler (+ libc, binutils) for that platform. The compiler is
> sl
> The problem of ‘CROSS_LIBRARY_PATH’ being ignored is fixed by commit 248d08e.
> Took me a bit of browsing to find out where that happens in GCC.
That's great, thanks.
Are there any other issues? Have you tried to cross-compile anything
non-trivial?
pgpWICOYAnoNl.pgp
Description: PGP signatur
Nikita Karetnikov skribis:
> I was able to cross-compile a "hello world" program.
>
> First, I created the following symlinks:
>
> # ln -s
> /nix/store/mifp2p1zjlvb4ndslw1r8grkpglybqjf-glibc-cross-mips64el-linux-gnu-2.17/lib/crti.o
>
> /nix/store/khdyz3i5aih56lxfk6hjvp3884apm7qb-gcc-cross-mips
Nikita Karetnikov skribis:
> Is it possible to use ’ instead of ' for the apostrophe and keep the
> source in ASCII?
There’s a contradiction: ’ is not ASCII.
But anyway, the normal way to use Texinfo is like TeX: you use ASCII
quotes, and it does the right thing (see the PDF output, and the Inf
Nikita Karetnikov skribis:
>(system* "tar" "xvf" tarball)
The ‘PATH’ environment variable is empty. So this should be:
(let ((tar (string-append (assoc-ref %build-inputs "tar")
"/bin/tar")))
(zero? (system* tar "xvf" tarball)))
And tar needs
How can I unpack the tarball? The following returns "In execvp of tar:
No such file or directory."
(arguments `(#:modules ...
#:builder
(begin
...
(let* ((tarball (assoc-ref %build-inputs "tarb
Nikita Karetnikov skribis:
> (define (gnupg-receive-keys key-id server)
> - (system* (%gpg-command) "--keyserver" server "--recv-keys" key-id))
> + (system* (%gpg-command)
> + "--keyserver" server
> + "--search-keys" (string-append "0x" key-id)))
As the name suggests, this
Nikita Karetnikov skribis:
(let* ((gh (assoc-ref %build-inputs "source"))
>>>
>>> What is the associated value here? I assume it should be 'gh.pl'.
>
>> Yes. Actually, “source” is the name of the input that corresponds to
>> the ‘source’ field of the package. So, if your package does
Is it possible to use ’ instead of ' for the apostrophe and keep the
source in ASCII?
From 3384e3e2e00d3cbef37b913c9a17df5842522ef8 Mon Sep 17 00:00:00 2001
From: Nikita Karetnikov
Date: Fri, 24 May 2013 12:02:15 +
Subject: [PATCH] doc: Improve wording and fix typos in "Introduction" and
"Re
>> And I still think that 'guix refresh' must ask before importing a key.
> Patches welcome. :-)
What do you think?
diff --git a/guix/gnupg.scm b/guix/gnupg.scm
index c17a495..ba5160a 100644
--- a/guix/gnupg.scm
+++ b/guix/gnupg.scm
@@ -143,7 +143,9 @@ missing key."
status))
(define
>>>(let* ((gh (assoc-ref %build-inputs "source"))
>>
>> What is the associated value here? I assume it should be 'gh.pl'.
> Yes. Actually, “source” is the name of the input that corresponds to
> the ‘source’ field of the package. So, if your package does
> (package
> (source (origi
13 matches
Mail list logo
