Porting to anything

The currently unsatisfying situation, according to "HACKING", is that bootstrapping guix essentially starts by installing (and thus in the worst case porting) nix. I have spent the evening working on a shell script automating the compilation of the bootstrap binaries. Unsurprisingly, I end up

New “guix pull” command

Hi, Commit f651b47 adds a “guix pull” command. It fetches a Guix source tarball, unpacks it, compiles Scheme code (so not the daemon), and changes ~/.config/guix/latest to point to it. The commit also changes the ‘guix’ command to put ~/.config/guix/latest at the front of the search path (except

Re: A logo

Ludovic Courtès wrote .. > Should we do it differently? Ah, you're referring to the "Use of Graphics" section in the stylesheet [0]. That's actually referring to main graphics page [1] although this is fine too. Adding it to the GNU Art Gallery might be a good thing too. I'll make sure that gets

Re: Problem with texinfo 5.0 package

Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> The built texinfo 5.0 packages contain a few uses of 'perl' that are not >>> pointing to a specific version in /nix/store: >> >> Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang

Re: A logo

Hi Jason, "Jason Self" skribis: > Assuming that's the decision... it's currently in an href tag and it > doesn't really need to be. It used to(?) be a convention that the logo would point to a page containing info about it. Should we do it differently? > I'm also assuming that the right margi

Re: Problem with texinfo 5.0 package

l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> The built texinfo 5.0 packages contain a few uses of 'perl' that are not >> pointing to a specific version in /nix/store: > > Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang’ to > handle /usr/bin/env special

Re: Problem with texinfo 5.0 package

l...@gnu.org (Ludovic Courtès) writes: > carl hansen skribis: > >> FYI When I recently upgraded to texinfo-5, I had to make a soft link >> ln -s texi2any makeinfo >> The link was supposed to be made in the package, but it wasn't. It >> might be relevant to you. > > I just installed (from Guix)

GSoC?

Hello! Should we submit a project for GSoC? There’s some info regarding GNU’s participation at . (I have zero experience with GSoC, though.) One project that would be suitable, because it’s orthogonal and challenging yet doab

Re: Problem with texinfo 5.0 package

carl hansen skribis: > FYI When I recently upgraded to texinfo-5, I had to make a soft link > ln -s texi2any makeinfo > The link was supposed to be made in the package, but it wasn't. It > might be relevant to you. I just installed (from Guix) it and it did create the symlink. Ludo’.

Re: Porting to mips64el

Andreas Enge skribis: > Am Mittwoch, 20. Februar 2013 schrieb Nikita Karetnikov: >> > Could you maybe provide some, Nikita? >> Sure. But what should I do? >> Should I adjust '%bootstrap-glibc' somehow? > > I think adding something like > (arguments > '(#:configure-flags >(list "

Re: Problem with texinfo 5.0 package

Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> The built texinfo 5.0 packages contain a few uses of 'perl' that are not >>> pointing to a specific version in /nix/store: >> >> Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang

Re: Problem with texinfo 5.0 package

On Wed, Feb 20, 2013 at 10:42 AM, Mark H Weaver wrote: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> The built texinfo 5.0 packages contain a few uses of 'perl' that are not >>> pointing to a specific version in /nix/store: >> >> Yes, I know, but since in ‘core-updat

Re: Porting to mips64el

Am Mittwoch, 20. Februar 2013 schrieb Nikita Karetnikov: > > Could you maybe provide some, Nikita? > Sure. But what should I do? > Should I adjust '%bootstrap-glibc' somehow? I think adding something like (arguments '(#:configure-flags (list "CFLAGS=-march=mips64 -mabi=64"))) to %

Re: A logo

> Can we ask the GNU webmasters? > > I think there’s one lurking here. Jason? :-) > > Ludo’. Yeah, I think it's better to the left as well. Assuming that's the decision... it's currently in an href tag and it doesn't really need to be. I'm also assuming that the right margin between the logo an

Re: Problem with texinfo 5.0 package

l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> The built texinfo 5.0 packages contain a few uses of 'perl' that are not >> pointing to a specific version in /nix/store: > > Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang’ to > handle /usr/bin/env special

Re: Porting to mips64el

> Could you maybe provide some, Nikita? Sure. But what should I do? Should I adjust '%bootstrap-glibc' somehow? pgpNbt1ePcXrM.pgp Description: PGP signature

Re: Porting to mips64el

Andreas Enge skribis: > The file > /nix/store/j2gf9gm512s8y64pgvw84258p3qsqfkq-glibc- > bootstrap-0/include/gnu/stubs.h > tries to include stubs-n64_hard.h ("hard" standing for "hard float"); > but there is only a stubs-n32_hard.h in the directory. Ah I see, that’s because the glibc-bootstrap-0

Re: Porting to mips64el

Am Mittwoch, 20. Februar 2013 schrieb Ludovic Courtès: > How exactly did you modify gcc-boot0? For the time being, I simply hard-coded two additional configure flags: diff --git a/gnu/packages/base.scm b/gnu/packages/base.scm index 5c39ec3..25e07bc 100644 --- a/gnu/packages/base.scm +++ b/gnu/pac

Re: Porting to mips64el

Andreas Enge skribis: > Am Dienstag, 19. Februar 2013 schrieb Andreas Enge: >> I think it might be enough to add the following configure flags: >>--with-arch=mips64 -with-abi=64 > > Unfortunately, it failed after some compilation time with [...] > checking how to run the C preprocessor... /

Re: A logo

Andreas Enge skribis: > Am Dienstag, 19. Februar 2013 schrieb Ludovic Courtès: >> Help welcome! Note that if you have commit access to the source code >> repo, you also have access to the web page repo (CVS) > > Seriously? Yep. :-) That’s how gnu.org and nongnu.org web pages are managed, and

Re: Problem with texinfo 5.0 package

Mark H Weaver skribis: > The built texinfo 5.0 packages contain a few uses of 'perl' that are not > pointing to a specific version in /nix/store: Yes, I know, but since in ‘core-updates’ we’ll change ‘patch-shebang’ to handle /usr/bin/env specially, that’ll work well there. Ludo’.

Re: Toward 0.2

Nikita Karetnikov skribis: >> wrapProgram $out/bin/guile-snarf --prefix PATH : "${gawk}/bin" > > How can I get the output of a package? With the recently-added ‘package-output’ (singular): --8<---cut here---start->8--- scheme@(guile-user)> (package-output s

Re: Porting to mips64el

Am Dienstag, 19. Februar 2013 schrieb Andreas Enge: > I think it might be enough to add the following configure flags: >--with-arch=mips64 -with-abi=64 Unfortunately, it failed after some compilation time with make[2]: Leaving directory `/tmp/nix-build-gcc-cross- boot0-4.7.2.drv-0/build/gcc'

Re: Toward 0.2

Am Sonntag, 17. Februar 2013 schrieb Ludovic Courtès: > • Xorg & co. packaged (Andreas? :-)); Ok, I will have a look during the weekend. Andreas

Re: A logo

Am Dienstag, 19. Februar 2013 schrieb Ludovic Courtès: > Help welcome! Note that if you have commit access to the source code > repo, you also have access to the web page repo (CVS) Seriously? I think I forgot how to use cvs 10 years ago... How about updating it to git? Also, I noticed that the