From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Nieuwenhuizen Subject: Re: Mes 0.5 released Date: Fri, 28 Apr 2017 10:16:51 +0200 Message-ID: <87inlpt098.fsf@gnu.org> References: <8760hqxcxr.fsf@gnu.org> <87h919dkjd.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <87h919dkjd.fsf@web.de> (Arne Babenhauserheide's message of "Fri, 28 Apr 2017 09:59:11 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guile-user-bounces+guile-user=m.gmane.org@gnu.org Sender: "guile-user" To: Arne Babenhauserheide Cc: guix-devel@gnu.org, guile-user@gnu.org, epsilon-devel@gnu.org List-Id: guix-devel.gnu.org Arne Babenhauserheide writes: > Wow! Congratulation on full bootstrapping of mes! Thanks, Arne! > So we can now build mes.c with mescc driven by Guile and then use mes to > run mescc again to build mes.c? Yes, that's correcct. mes.c can be compiled with either gcc make out/mes or with [32 bit] gcc -nostdinc -nostdlib make out/i686-unknown-linux-gnu-mes or with guile guile/mescc.scm src/mes.c > out/mes.guile or with mes scripts/mescc.mes src/mes.c > out/mes.mes Now the route can go up (my first aim) - compile tcc, guile or gcc or it can go down - add separate assembly step, assembly output - use stage0+ project, esp rewrite mes.c in stage2-LISP - use/work with epsilon? or it can stay level - cleanup mescc - fix bugs - look into Nyacc - decide on psyntax Greetings, janneke --=20 Jan Nieuwenhuizen | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar=C2=AE http://AvatarAcademy.nl= =20=20