From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Help updating GZdoom to 4.10.0
Date: Sat, 01 Jul 2023 16:47:57 +0200 [thread overview]
Message-ID: <20230701144757.hdg-WcHHD_HowSBfaHEkDQOW1b9otlzYeKM63qU20NE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44762@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Closed issue by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/44762
Description:
### Discussed in https://github.com/void-linux/void-packages/discussions/44756
<div type='discussions-op-text'>
<sup>Originally posted by **SpidFightFR** July 1, 2023</sup>
Hey guys how are you all doing?
I need help regarding [the PR i tried to make earlier](https://github.com/void-linux/void-packages/pull/44504), basically, the package builds without issue on x64 GlibC, but not on i686 or x64 musl (check [here](https://github.com/void-linux/void-packages/pull/44504/checks))...
At first i thought it was the [patch](https://gist.github.com/SpidFightFR/78914fe5db2062cf247362b91715e21c#file-fix-i686-modified-patch) i made for i686 but after reviewing it, i have trouble finding where the issue lies...
Also there is a [Gist](https://gist.github.com/SpidFightFR/78914fe5db2062cf247362b91715e21c) with the updated template, the patch and some useful links in an index.
Any help is welcome, don't hesitate to propose changes, and i'll make them !
Thanks by advance !</div>
prev parent reply other threads:[~2023-07-01 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-01 14:47 [ISSUE] " classabbyamp
2023-07-01 14:47 ` classabbyamp
2023-07-01 14:47 ` [ISSUE] [CLOSED] " classabbyamp
2023-07-01 14:47 ` classabbyamp [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=20230701144757.hdg-WcHHD_HowSBfaHEkDQOW1b9otlzYeKM63qU20NE@z \
--to=classabbyamp@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).