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] New: python dependency (as strict requirement)
Date: Tue, 07 Apr 2020 15:32:05 +0000 [thread overview]
Message-ID: <bug-25799-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25799
Bug ID: 25799
Summary: python dependency (as strict requirement)
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: serg.brester at sebres dot de
CC: carlos at redhat dot com
Target Milestone: ---
Starting from
[c6982f7efc1c70fe2d6160a87ee44d871ac85ab0] it is impossible to build glibc
without python (configure would fail, as well as it is added to strict
requirements now), where previously it was only needed to build some manual and
to run some tests.
But python itself needs glibc (to build or start).
This looks like a cyclic dependency, so for example it is interesting whether
it is ever possible now to compile that from scratch.
Commit-link:
https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=c6982f7efc1c70fe2d6160a87ee44d871ac85ab0;hp=5c81be53407434ce22b849722a3d691295480016
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-04-07 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 15:32 serg.brester at sebres dot de [this message]
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
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@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).