From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "U.Mutlu" <um@mutluit.com>
Cc: gcc-help@gcc.gnu.org, guix-devel@gnu.org
Subject: Re: SOLVED: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
Date: Wed, 11 Jul 2018 21:23:27 +0200 [thread overview]
Message-ID: <87zhyxk24w.fsf@gnu.org> (raw)
In-Reply-To: <5B46473B.8050701@mutluit.com> (U. Mutlu's message of "Wed, 11 Jul 2018 20:06:51 +0200")
U.Mutlu writes:
>> Thanks! I'm very grateful for your help. I succeeded in building
>> gcc-4.7.4 from almost no binary seeds[0] for GuixSD!
>
> Congrats! :-)
Thanks!
> Can you give us some info on your project? (mes?)
Mes[0] aims to help create full source bootstrapping for GNU/Linux
distributions such as GuixSD[1] as part of the bootstrappable builds[2]
effort.
It consists of a mutual self-hosting Scheme interpreter written in
~5,000LOC of simple C and a Nyacc-based C compiler written in Scheme.
> As I could figure out, GuixSD is a (new) GNU package manager, right?
Correct. Guix is the packagage manager, GuixSD (for System Distribution) is
GNU's GNU/Linux distribution built around it.
> I think you mentioned TCC, scheme, own header files etc.
This MesCC compiler comes with three sizes of Mes lib C: libc for
building mes.c, libc+tcc for building TCC. Then, there is libc+gnu that
is used together with TCC to build binutils-2.20a and gcc-2.95.3.
> Did you still had to use also the old gcc 2.95.3 ?
We are using gcc 2.95.3 as the first GCC compiler mainly because (after
many experiments with versions from 1.40 to 4.1) it proved the most
"bootstrappable" GCC. GCC 3 introduces a dependency on dirent, e.g.,
that our naive C library does not support.
If we make our libc+gnu richer then we can probably target a newer GCC,
but it's not obvious to me what the bootstrap consequences of that are.
> What's the goal, and why especially that target version gcc 4.7.4 ?
GCC 4.7.4 is currently used as one of the bootstrap binaries of GuixSD.
Also, it's the most recent GCC compiler that can be considered to be
directly bootstrappable. I don't consider building a c++ bootstrap
compiler ;-)
The goal is to replace the x86 bootstrap of GNU/Linux distributions,
using a bootstrap [mostly] from source instead of what currently
happens: seeding it with a very large blob of bootstrap binaries.
GuixSD seems the best place to develop this in.
> Just a little bit curious about your complicated looking project :-)
Thanks for showing interest!
Greetings,
janneke
[0] http://gitlab.com/janneke/mes
[1] https://www.gnu.org/software/guix
[2] http://bootstrappable.org
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-07-11 19:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:57 gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF' Jan Nieuwenhuizen
2018-07-09 18:28 ` U.Mutlu
2018-07-09 19:40 ` Jan Nieuwenhuizen
2018-07-10 3:52 ` U.Mutlu
2018-07-10 7:31 ` Gábor Boskovits
2018-07-10 15:07 ` Jan Nieuwenhuizen
2018-07-10 19:51 ` Jan Nieuwenhuizen
2018-07-10 20:19 ` Jonathan Wakely
[not found] ` <5B452C86.6090003@mutluit.com>
2018-07-11 17:01 ` SOLVED: " Jan Nieuwenhuizen
2018-07-11 18:06 ` U.Mutlu
2018-07-11 19:23 ` Jan Nieuwenhuizen [this message]
2018-07-10 15:02 ` Jan Nieuwenhuizen
2018-07-10 15:54 ` Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhyxk24w.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=guix-devel@gnu.org \
--cc=um@mutluit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).