public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "serg.brester at sebres dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/25799] python dependency (as strict requirement)
Date: Tue, 07 Apr 2020 16:26:37 +0000	[thread overview]
Message-ID: <bug-25799-131-UnU14Napcn@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 #2 from Sergey Brester (aka sebres) <serg.brester at sebres dot de> ---
> When bootstrapping for a new target, you already have native Python on the build system

Unless you don't have native python on build system (or even a host system with
gnu toolchain at all). I did not mean a cross-compiling in my question.
You seem to strange understand the sentence "compile from scratch".

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 tend to interpret your answer as "No" and that the bootstrapping of the gnu
toolchain isn't considered a requirement any more.

I'd only say then - there was "*nix from scratch" once.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-04-07 16:26 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 [this message]
2020-04-07 18:18 ` joseph at codesourcery dot com

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-UnU14Napcn@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: link
Be 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).