From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Search for absolute symlinks in cross* and possibly other packages.
Date: Sat, 22 Feb 2020 23:01:17 +0100 [thread overview]
Message-ID: <20200222220117.jDcoBX2l32RxSDcCmM4_w5_qnD3PVypTZdNQCUX7Yus@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11541@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Closed issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/11541
Description:
In the face of https://github.com/void-linux/void-packages/commit/9e1db28d09988efa3ea64ab8e5aeec6ec58ecf0d we should look for other packages with invalid symbolic links crossing the `host <-> cross base` border. If they exist they may explain strange errors with cross building we see here and there.
Perhaps someone has an idea how such a search could be scripted for a repository. The official repo does not have any `mips*-musl` packages thus a script should allow to specify the repo to scan.
prev parent reply other threads:[~2020-02-22 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 17:06 [ISSUE] " voidlinux-github
2020-02-22 22:01 ` pullmoll [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=20200222220117.jDcoBX2l32RxSDcCmM4_w5_qnD3PVypTZdNQCUX7Yus@z \
--to=pullmoll@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).