Github messages for voidlinux
 help / color / mirror / Atom feed
From: wael444 <wael444@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: stw-0.2
Date: Tue, 05 Jul 2022 17:03:03 +0200	[thread overview]
Message-ID: <20220705150303.LBeNfigVvAN_2nxj0Uez1u76_Oxox4VJxQXqXttQ_ng@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37834@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 885 bytes --]

New comment by wael444 on void-packages repository

https://github.com/void-linux/void-packages/pull/37834#issuecomment-1175166754

Comment:
> You will need to add -I/usr/aarch64-linux-gnu/usr/include/ to the command. -I/usr/aarch64-linux-gnu/usr/include/X11 will try to search for <X11/Xft/Xft.h> in /usr/aarch64-linux-gnu/usr/include/X11/X11/Xft/Xft.h which obviously doesn't exist

```
cc -std=c99 -pedantic -Wall -Werror -I/usr/include/X11 `pkg-config --cflags fontconfig` -I/usr/aarch64-linux-gnu/usr/include -D_DEFAULT_SOURCE -D_BSD_SOURCE -D_POSIX_C_SOURCE=2 -c stw.c
In file included from stw.c:3:
/usr/aarch64-linux-gnu/usr/include/limits.h:124:3: error: #include_next is a GCC extension [-Werror]
  124 | # include_next <limits.h>
      |   ^~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [Makefile:8: stw.o] Error 1
```
note: `-Wall` in `CFLAGS`

  parent reply	other threads:[~2022-07-05 15:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 11:33 [PR PATCH] New package: stw-0.1 wael444
2022-07-04 11:44 ` wael444
2022-07-04 17:53 ` [PR REVIEW] " paper42
2022-07-04 17:53 ` paper42
2022-07-04 17:54 ` paper42
2022-07-05 11:20 ` sineemore
2022-07-05 11:55 ` wael444
2022-07-05 11:59 ` sineemore
2022-07-05 13:34 ` [PR PATCH] [Updated] " wael444
2022-07-05 13:42 ` New package: stw-0.2 sineemore
2022-07-05 13:44 ` wael444
2022-07-05 14:11 ` [PR REVIEW] " paper42
2022-07-05 14:16 ` wael444
2022-07-05 14:16 ` [PR PATCH] [Updated] " wael444
2022-07-05 14:20 ` [PR REVIEW] " paper42
2022-07-05 14:22 ` wael444
2022-07-05 14:24 ` paper42
2022-07-05 14:42 ` sineemore
2022-07-05 14:49 ` sineemore
2022-07-05 15:03 ` wael444 [this message]
2022-07-05 15:23 ` [PR PATCH] [Updated] " wael444
2022-07-05 15:31 ` New package: stw-0.3 sineemore
2022-07-05 15:32 ` sineemore
2022-10-04  2:14 ` github-actions
2022-10-19  2:14 ` [PR PATCH] [Closed]: " github-actions

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=20220705150303.LBeNfigVvAN_2nxj0Uez1u76_Oxox4VJxQXqXttQ_ng@z \
    --to=wael444@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).