From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] FTBFS: ghostscript after freetype update to 2.10.4
Date: Sun, 25 Oct 2020 07:00:13 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25866@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
New issue by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/25866
Description:
```make
cc -DHAVE_MKSTEMP -DHAVE_FILE64 -DHAVE_FSEEKO -DHAVE_MKSTEMP64 -DHAVE_FONTCONFIG -DHAVE_SETLOCALE -DHAVE_DBUS -DHAVE_BSWAP32 -DHAVE_BYTESWAP_H -DHAVE_STRERROR -DHAVE_ISNAN -DHAVE_ISINF -DHAVE_PREAD_PWRITE=1 -DGS_RECURSIVE_MUTEXATTR=PTHREAD_MUTEX_RECURSIVE -fPIC -O2 -DNDEBUG -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -fno-strict-aliasing -Werror=declaration-after-statement -fno-builtin -fno-common -Werror=return-type -DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1 -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=i686 -O2 -pipe -g -DHAVE_RESTRICT=1 -DUSE_LIBPAPER -fno-strict-aliasing -DHAVE_POPEN_PROTO=1 -DGS_DEVS_SHARED -DGS_DEVS_SHARED_DIR=\"/usr/lib32/ghostscript/9.53.3\" -I./obj -I./base -I./devices -DWHICH_CMS="lcms2" -o ./obj/gxsample.o -c ./base/gxsample.c
./base/fapi_ft.c:128:1: warning: return type defaults to 'int' [-Wimplicit-int]
128 | FT_CALLBACK_DEF(void *)
| ^~~~~~~~~~~~~~~
./base/fapi_ft.c:128:1: warning: no previous prototype for 'FT_CALLBACK_DEF' [-Wmissing-prototypes]
./base/fapi_ft.c: In function 'FT_CALLBACK_DEF':
./base/fapi_ft.c:129:1: error: expected declaration specifiers before 'FF_alloc'
129 | FF_alloc(FT_Memory memory, long size)
| ^~~~~~~~
```
next reply other threads:[~2020-10-25 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 6:00 pullmoll [this message]
2020-10-25 6:10 ` [ISSUE] [CLOSED] " pullmoll
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25866@inbox.vuxu.org \
--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).