public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/25799] python dependency (as strict requirement) Date: Tue, 07 Apr 2020 18:18:56 +0000 [thread overview] Message-ID: <bug-25799-131-qvYoOXjwRf@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25799-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25799 --- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Tue, 7 Apr 2020, serg.brester at sebres dot de via Glibc-bugs wrote: > Assume you have ONLY initially built system without anything from GNU (and no > python)... > The question was: is that even possible any more, starting with no gnu software > and compiling everything from scratch? I'm pretty sure you can build Python with a non-GNU C compiler, if you're starting from a proprietary Unix with the OS-provided proprietary C compiler (as would have been the typical starting point for people building GCC in the 1980s and early 1990s). To build GCC you do of course now need a C++ compiler, but I think the last version of GCC that could be built as C works for building current GCC (until GCC moves to requiring C++11, at which point the bootstrap sequence from a C compiler will become longer). > I tend to interpret your answer as "No" and that the bootstrapping of the gnu > toolchain isn't considered a requirement any more. Look at the Guix / GNU Mes project's work on bootstrapping with a reduced binary seed. Guix / GNU Mes is where such issues are addressed in the GNU project, not glibc. It may not yet be at the point of the starting binaries needed being of the size that someone can assemble by hand, but that would be a natural end-goal to aim for. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2020-04-07 18:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-07 15:32 [Bug build/25799] New: " serg.brester at sebres dot de 2020-04-07 15:57 ` [Bug build/25799] " joseph at codesourcery dot com 2020-04-07 16:26 ` serg.brester at sebres dot de 2020-04-07 18:18 ` joseph at codesourcery dot com [this message]
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-25799-131-qvYoOXjwRf@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).