From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Building gcc fails with circular dependencies.
Date: Tue, 25 Feb 2020 10:56:56 +0100 [thread overview]
Message-ID: <20200225095656.zZnOsXEh9ELuZvqXXBeacHkC5DWqWQQXbN-RhXFb2aE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13782@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
Closed issue by gravicappa on void-packages repository
https://github.com/void-linux/void-packages/issues/13782
Description:
### System
Ubuntu with xbps-src set up by [manual](https://github.com/void-linux/void-packages/blob/master/README.md#using-xbps-src-in-a-foreign-linux-distribution).
* void-packages:
7a59e00e2d0e268b59821165c7458c442fb666a6
* package:
- gcc-9.1.0_3
- glibc-2.30_1
- python3-3.6.9_1
### Actual behavior
There is a circular dependencies between gcc, glibc and python3.
### Steps to reproduce the behavior
```
./xbps-src zap
./xbps-src bootstrap
./xbps-src -C -E -N pkg base-files
```
I suspect that this is unintended use of xbps-src, but not sure.
parent reply other threads:[~2020-02-25 9:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13782@inbox.vuxu.org>]
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=20200225095656.zZnOsXEh9ELuZvqXXBeacHkC5DWqWQQXbN-RhXFb2aE@z \
--to=xtraeme@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).