Re: Emacs minor-mode highlight code stages (gexp & sexp)

2017-11-21 Thread Oleg Pykhalov
Probably need to append to commit message: * gnu/packages/patches/emacs-highlight-stages-add-gexp.patch: New file. * gnu/local.mk (dist_patch_DATA): Add this.

Re: Emacs minor-mode highlight code stages (gexp & sexp)

2017-11-21 Thread Oleg Pykhalov
Hello, Still no reply on https://github.com/zk-phi/highlight-stages/issues/10 I prepared a patch and could merge it if you agree. From aad1089320315f58147d84e7ff35b3f1f89032a9 Mon Sep 17 00:00:00 2001 From: Oleg Pykhalov Date: Wed, 22 Nov 2017 09:10:24 +0300 Subject:

Re: gcc-ddc

2017-11-21 Thread Ricardo Wurmus
Jan Nieuwenhuizen writes: > Gábor Boskovits writes: > > Hey Gábor! > > [cc: guix-devel] > >> I'm definietly making progress on this. Now I have a working debug build of >> gcc. >> Identified the critical symbols, they are: > >> static const char *const standard_exec_prefix =

Re: gcc-ddc

2017-11-21 Thread Jan Nieuwenhuizen
Gábor Boskovits writes: > I just pushed what I have right now. It's on branch gcc-ddc on my github. > Should I post a patch here?  Great! Yes, that makes commenting on it an easy option. Also, please mention the location to clone from. github is non-free, but cloning from it is ok. janneke

Re: [bootstrappable] Re: prototyping the full source bootstrap path

2017-11-21 Thread Ricardo Wurmus
Ludovic Courtès writes: > So the next steps in the dependency graph are: > > mes-boot -> mescc -> tinycc -> gcc@4.7 -> gcc > > Do I get this right? It’s not clear yet. An alternative approach is to try to build Guile first by using mes as the bootstrap Scheme interpreter.

FOSDEM 2018 and announcing a GNU Guix/Guile day!

2017-11-21 Thread Pjotr Prins
We are hosting a GNU Guix and Guile day on Friday before FOSDEM (that is Feb 2nd.). We have a large room for 40 people at http://icab.be/ for the whole day. In the morning we'll have talks - and in the afternoon it is free discussion and hacking. Write Manolis, Ludo or me if you would like to

Re: 01/01: gnu: audacity: Update to 2.2.0.

2017-11-21 Thread Pjotr Prins
On Tue, Nov 21, 2017 at 01:20:17PM -0500, Leo Famulari wrote: > On Sat, Nov 18, 2017 at 08:38:54PM +0100, Pjotr Prins wrote: > > On Sat, Nov 18, 2017 at 10:42:48AM -0500, Leo Famulari wrote: > > > On Debian, the graphical user interface is broken for me (overlapping > > > and blank elements), and

Re: 01/01: gnu: audacity: Update to 2.2.0.

2017-11-21 Thread Leo Famulari
On Sat, Nov 18, 2017 at 08:38:54PM +0100, Pjotr Prins wrote: > On Sat, Nov 18, 2017 at 10:42:48AM -0500, Leo Famulari wrote: > > On Debian, the graphical user interface is broken for me (overlapping > > and blank elements), and it crashes when opening a file, with > > "(audacity:21456):

Re: [bootstrappable] Re: prototyping the full source bootstrap path

2017-11-21 Thread Jan Nieuwenhuizen
Orians, Jeremiah (DTMB) writes: >> It wouldn’t really help in that mescc+/guilecc is just as capable as the >> earlier mescc, no? > There is however a real difference in terms of performance, guile is simply > faster Plus there is another angle on this. MesCC, the bootstrap C compiler in

Re: gcc-ddc

2017-11-21 Thread Gábor Boskovits
I just pushed what I have right now. It's on branch gcc-ddc on my github. Should I post a patch here? 2017-11-21 0:16 GMT+01:00 Gábor Boskovits : > The only problematic one seems to be standard_libexec_prefix, because that > is used in line 3654 of gcc/gcc.c in a real

Re: gcc-ddc

2017-11-21 Thread Gábor Boskovits
The wrapper approach eliminated those three, we still have in prefix.c the prefix used as static initializer. I have to investigate further, but it's only 300 lines, should be tractable. 2017-11-21 0:16 GMT+01:00 Gábor Boskovits : > The only problematic one seems to be

RE: [bootstrappable] Re: prototyping the full source bootstrap path

2017-11-21 Thread Orians, Jeremiah (DTMB)
> It wouldn’t really help in that mescc+/guilecc is just as capable as the > earlier mescc, no? There is however a real difference in terms of performance, guile is simply faster > Indeed, Guile needs a C compiler. Technically, it could be built from a lisp compiler > In general, we need a C