From: xelxebar <xelxebar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: hyperrogue-11.3f
Date: Mon, 30 Mar 2020 07:39:11 +0200 [thread overview]
Message-ID: <20200330053911.FuczNNuPHQQKJIIw604D8RsW0b9-iGidVi0L6SUhdbE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20454@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
New comment by xelxebar on void-packages repository
https://github.com/void-linux/void-packages/pull/20454#issuecomment-605792586
Comment:
For some reason, `/usr/include/SDL/SDL_gfxPrimitives.h` from `SDL_gfx-devel` has
#include <SDL.h>
whereas `SDL-devel` installs that header to `/usr/include/SDL/SDL.h`. That is why `pre_build` has that symlink hack.
next prev parent reply other threads:[~2020-03-30 5:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20454@inbox.vuxu.org>
2020-03-30 5:38 ` xelxebar
2020-03-30 5:39 ` xelxebar [this message]
2020-03-30 6:03 ` xelxebar
2020-03-30 6:27 ` xelxebar
2020-03-30 6:31 ` xelxebar
2020-03-31 1:37 ` travankor
2020-03-31 2:16 ` [PR PATCH] [Updated] " xelxebar
2020-03-31 2:17 ` xelxebar
2020-03-31 9:27 ` xtraeme
2020-04-01 2:00 ` xelxebar
2020-04-01 2:41 ` [PR PATCH] [Updated] " xelxebar
2020-04-01 2:43 ` xelxebar
2020-04-01 10:06 ` Johnnynator
2020-04-01 10:07 ` Johnnynator
2020-04-01 12:37 ` xelxebar
2020-04-01 12:37 ` xelxebar
2020-04-01 12:38 ` [PR PATCH] [Updated] " xelxebar
2020-04-01 12:38 ` xelxebar
2020-04-01 12:53 ` Johnnynator
2020-04-01 12:57 ` Johnnynator
2020-04-01 23:46 ` xelxebar
2020-04-01 23:48 ` xelxebar
2020-04-01 23:50 ` xelxebar
2020-04-02 0:00 ` Johnnynator
2020-04-02 0:02 ` [PR PATCH] [Updated] " xelxebar
2020-04-02 0:03 ` xelxebar
2020-04-23 6:51 ` [PR PATCH] [Updated] " xelxebar
2021-11-06 23:07 ` [PR PATCH] [Closed]: " abenson
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=20200330053911.FuczNNuPHQQKJIIw604D8RsW0b9-iGidVi0L6SUhdbE@z \
--to=xelxebar@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).