From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] FTBFS: agg
Date: Sun, 16 Oct 2022 01:57:16 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39976@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3036 bytes --]
New issue by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/39976
Description:
[current upstream](https://agg.sourceforge.net/antigrain.com/) only has source for v2.4, we should probably try to move to a different fork and update. debian has [source for the version we package](https://packages.debian.org/stretch/source/agg), but it fails to build:
```
Making all in font_freetype
make[1]: Entering directory '/builddir/agg-2.5+dfsg1/font_freetype'
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -I../include -I/usr/include/freetype2 -I/usr/include/libpng16 -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -fdebug-prefix-map=/builddir/agg-2.5+dfsg1=. -MT libaggfontfreetype_la-agg_font_freetype.lo -MD -MP -MF .deps/libaggfontfreetype_la-agg_font_freetype.Tpo -c -o libaggfontfreetype_la-agg_font_freetype.lo `test -f 'agg_font_freetype.cpp' || echo './'`agg_font_freetype.cpp
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -I/usr/include/freetype2 -I/usr/include/libpng16 -fstack-clash-protection -D_FORTIFY_SOURCE=2 -mtune=generic -O2 -pipe -fdebug-prefix-map=/builddir/agg-2.5+dfsg1=. -MT libaggfontfreetype_la-agg_font_freetype.lo -MD -MP -MF .deps/libaggfontfreetype_la-agg_font_freetype.Tpo -c agg_font_freetype.cpp -fPIC -DPIC -o .libs/libaggfontfreetype_la-agg_font_freetype.o
In file included from agg_font_freetype.h:34,
from agg_font_freetype.cpp:26:
../include/agg_scanline_u.h: In member function 'void agg::scanline32_u8_am<AlphaMask>::finalize(int)':
../include/agg_scanline_u.h:482:39: error: cannot call member function 'void agg::scanline_u8::finalize(int)' without object
482 | base_type::finalize(span_y);
| ^
../include/agg_scanline_u.h:485:70: error: cannot call member function 'agg::scanline_u8::span* agg::scanline_u8::begin()' without object
485 | typename base_type::iterator span = base_type::begin();
| ^
../include/agg_scanline_u.h:486:55: error: cannot call member function 'unsigned int agg::scanline_u8::num_spans() const' without object
486 | unsigned count = base_type::num_spans();
| ^
../include/agg_scanline_u.h:490:62: error: cannot call member function 'int agg::scanline_u8::y() const' without object
490 | base_type::y(),
| ^
make[1]: *** [Makefile:471: libaggfontfreetype_la-agg_font_freetype.lo] Error 1
make[1]: Leaving directory '/builddir/agg-2.5+dfsg1/font_freetype'
make: *** [Makefile:496: all-recursive] Error 1
```
this is only used by one package (desmume), and it seems that agg is an optional dependency, so maybe it would be better to just remove it.
next reply other threads:[~2022-10-15 23:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 23:57 classabbyamp [this message]
2023-01-14 1:56 ` 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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39976@inbox.vuxu.org \
--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).