Problem with texinfo 5.0 package

Hi Ludovic, Regarding commit a24b75d8e1753da629ecf945f4022eee4c340aed: The built texinfo 5.0 packages contain a few uses of 'perl' that are not pointing to a specific version in /nix/store: ./bin/pod2texi:1:#!/nix/store/777jas1fcgc38hmvq6lq1sa9k67f10kl-coreutils-8.20/bin/env perl ./bin/texi2dvi

Re: Toward 0.2

> wrapProgram $out/bin/guile-snarf --prefix PATH : "${gawk}/bin" How can I get the output of a package? There is 'package-outputs': scheme@(guile-user)> ,use (gnu packages wget) (guix packages) scheme@(guile-user)> (package-outputs wget) $1 = ("out") But how can I get the value (like in '#:pha

Re: A logo

Nikita Karetnikov skribis: > "A copy of the license is included in the file 'COPYING.GPL'; [...] A > copy of the license is included in the file 'COPYING.FDL'." [1] > > I think these lines can be removed from the page. Oops, fixed now. >> I guess a bit of CSS would help (notably to leave more s

Re: A logo

Cyril Roelandt skribis: > To leave some space around the logo, I'd write: > > Oh, good. I’ve tried something along these lines. Ludo’.

Re: A logo

"A copy of the license is included in the file 'COPYING.GPL'; [...] A copy of the license is included in the file 'COPYING.FDL'." [1] I think these lines can be removed from the page. > I guess a bit of CSS would help (notably to leave more space around it), > but I’m not sure how to do it, nor h

Nix submodule updated

Hi, Commit 15b673e updates the Nix sub-module. Make sure the run ./bootstrap after pulling. The main visible difference is that log files are now stored in sub-directories: https://github.com/NixOS/nix/commit/536c85ea49c16a2ecd5a1ba169975b296cd6158c Ludo’.

Re: A logo

On 02/19/2013 10:22 PM, Ludovic Courtès wrote: Nikita Karetnikov skribis: I'm attaching a tarball. Note that Document Metadata (File -> Document Metadata in Inkscape) says that the logo is under a proprietary license (I guess it's a bug because I can't save the license), but it's not true.

Re: Porting to mips64el

Andreas Enge skribis: > Am Dienstag, 19. Februar 2013 schrieb Ludovic Courtès: >> The bootstrap binaries don’t matter much, I think. What does matter is >> to get ‘gcc-boot0’ (a fake cross-compiler) to target the right ABI by >> default. I’m not sure how to do that, though. > > I think it might

Re: A logo

Nikita Karetnikov skribis: > I'm attaching a tarball. Note that Document Metadata > (File -> Document Metadata in Inkscape) says that the logo is under a > proprietary license (I guess it's a bug because I can't save the > license), but it's not true. Nice, thanks! I’ve put the logo on the web

Re: Porting to mips64el

> I will give it a try. Thanks. > Before downloading tarballs, the following frightening warning messages are > shown: 'guix/build/download.scm': ;; Autoload GnuTLS so that this module can be used even when GnuTLS is ;; not available. At compile time, this yields "possibly unbound ;; variable

Re: Porting to mips64el

Am Dienstag, 19. Februar 2013 schrieb Ludovic Courtès: > The bootstrap binaries don’t matter much, I think. What does matter is > to get ‘gcc-boot0’ (a fake cross-compiler) to target the right ABI by > default. I’m not sure how to do that, though. I think it might be enough to add the following

Re: Porting to mips64el

FWIW, there’s a discussion of MIPS ABIs at and related pages. Andreas Enge skribis: > Good question, I do not know myself yet how to achieve the goal! Maybe it > would be enough to provide "CFLAGS=-mabi64" in the bootstrap process; or >

Re: A logo

Very nice! Andreas

Re: A logo

> So, let’s leave a few days for comments, and then dub it the Official > Logo. I'm attaching a tarball. Note that Document Metadata (File -> Document Metadata in Inkscape) says that the logo is under a proprietary license (I guess it's a bug because I can't save the license), but it's not true.

Re: Porting to mips64el

Am Dienstag, 19. Februar 2013 schrieb Nikita Karetnikov: > > Nixos on my machine uses the abi n32 (long and void* have 32 bits, > > long long 64). I would like to switch to abi 64 (long with 64 bits); > > we might be the first distribution supporting this mode. > > I think that the above contradic

Re: mips64el: guild problem

Andreas Enge skribis: > Am Montag, 18. Februar 2013 schrieb Ludovic Courtès: >> This “GOOF” cookie indicates the Guile Object Object(!) Format. Here, >> it says little endian with 8-byte pointers. That corresponds to this >> GNU triplet: >> However, my guess is that Guile was compiled with the

Re: mips64el: guild problem

> Compiling worked so far. Now there is the hash mismatch in > http://alpha.gnu.org > /gnu/guix/bootstrap/mips64el-linux/20130105/guile-2.0.7.tar.xz . Nikita, could > you push your modification with the correct hash, or should I make the > suitable > modifications on my side? You should adjust

Re: mips64el: guild problem

Am Montag, 18. Februar 2013 schrieb Ludovic Courtès: > This “GOOF” cookie indicates the Guile Object Object(!) Format. Here, > it says little endian with 8-byte pointers. That corresponds to this > GNU triplet: > However, my guess is that Guile was compiled with the N32 ABI, so it > expects 4-byt

Re: Porting to mips64el

> Nixos on my machine uses the abi n32 (long and void* have 32 bits, long long > 64). I would like to switch to abi 64 (long with 64 bits); we might be the > first distribution supporting this mode. I think that the above contradicts the following. > In the debian distribution also installed on t

Re: Porting to mips64el

Nikita Karetnikov skribis: >>> What do you mean by "host code"? > >> I mean code that runs in your ‘guix-build’ process, as opposed to >> builder code running in the chroot (search the manual for “strata”.) > > I've read the manual. But it's still not clear. > > For example: How can I tell which

Re: Porting to mips64el

>> What do you mean by "host code"? > I mean code that runs in your ‘guix-build’ process, as opposed to > builder code running in the chroot (search the manual for “strata”.) I've read the manual. But it's still not clear. For example: How can I tell which expression is run by a Guile process l