From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: deadbeef: update to 1.8.7 and fix build
Date: Mon, 22 Feb 2021 21:23:00 +0100 [thread overview]
Message-ID: <20210222202300.xSZxEyC7FooozIzC624ynDBuYWKYC-tQxuXbT8Jo3Yg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
New comment by heliocat on void-packages repository
https://github.com/void-linux/void-packages/pull/28965#issuecomment-783650449
Comment:
An overly aggressive method for forcing clang as the compiler was the source of all build issues with the exception of i686, including the lack of PIE. Investigating that and then I'll un-draft this.
next prev parent reply other threads:[~2021-02-22 20:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 2:44 [PR PATCH] " heliocat
2021-02-22 9:09 ` ericonr
2021-02-22 20:03 ` [PR PATCH] [Updated] " heliocat
2021-02-22 20:23 ` heliocat [this message]
2021-02-23 18:27 ` heliocat
2021-02-23 18:39 ` heliocat
2021-02-23 19:06 ` [PR PATCH] [Updated] " heliocat
2021-02-23 19:14 ` [PR REVIEW] " ericonr
2021-02-23 19:14 ` ericonr
2021-02-23 19:14 ` ericonr
2021-02-23 19:14 ` ericonr
2021-02-23 19:14 ` ericonr
2021-02-23 21:56 ` heliocat
2021-02-23 21:59 ` heliocat
2021-02-23 22:02 ` heliocat
2021-02-23 22:06 ` heliocat
2021-02-23 22:07 ` heliocat
2021-02-23 22:10 ` ericonr
2021-02-23 22:10 ` ericonr
2021-02-23 22:13 ` heliocat
2021-02-23 22:14 ` heliocat
2021-02-23 22:15 ` heliocat
2021-02-23 23:02 ` [PR PATCH] [Updated] " heliocat
2021-02-24 0:20 ` heliocat
2021-02-24 0:31 ` [PR REVIEW] " heliocat
2021-02-24 0:31 ` heliocat
2021-02-24 3:37 ` [PR PATCH] [Closed]: " ericonr
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=20210222202300.xSZxEyC7FooozIzC624ynDBuYWKYC-tQxuXbT8Jo3Yg@z \
--to=heliocat@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).