armagetronad gentoo overlay missing patches

[bfx81]

The ftgl ebuild, required for armagetronad, fails because the "files" directory with the needed patches is missing.

These are the required patches in the ebuild.
"${FILESDIR}"/${P}-ftgl.pc.in.patch \
"${FILESDIR}"/${P}-gcc41.patch \
"${FILESDIR}"/${P}-configure.ac.patch

I used layman to get the overlay that point at this svn repository.
https://armagetronad.svn.sourceforge.ne ... oo/overlay

Tnx in advance for your great work with armagetron!

Filled also a bug on launchpad
https://bugs.launchpad.net/armagetronad/+bug/979951

[Tank Program]

Hmm. This now makes me wonder why we have our own ftgl ebuild when it already exists in the regular portage tree...

[Z-Man]

It probably didn't exist back when we started the overlay. Maybe just try what happens if we remove it now? Can't do it myself, both remaining gentoo boxes are kind of stuck.

[kyle]

that is basically what Luke-Jr said on IRC that is is not needed in there anymore so remove it

[Z-Man]

Done. Saying again: I can't test this myself. And also, I wouldn't know how to fix it if this attempt fails.

[bfx81]

I tried with the latest version on gentoo stable (it's also the latest upstream version) ftgl-2.1.3_rc5
Then building armagetronad stops on configure phase:

Code: Select all

[....]
checking for FT_Render_Glyph in -lftgl... no
configure: error: You need the library ftgl to compile Armagetron. Read the file doc/install_linux.html.

This is the list of the installed files of ftgl

Code: Select all

/usr/share/doc/ftgl-2.1.3_rc5/AUTHORS.bz2
/usr/share/doc/ftgl-2.1.3_rc5/BUGS.bz2
/usr/share/doc/ftgl-2.1.3_rc5/ChangeLog.bz2
/usr/share/doc/ftgl-2.1.3_rc5/INSTALL.bz2
/usr/share/doc/ftgl-2.1.3_rc5/NEWS.bz2
/usr/share/doc/ftgl-2.1.3_rc5/README.bz2
/usr/share/doc/ftgl-2.1.3_rc5/TODO.bz2
/usr/share/doc/ftgl-2.1.3_rc5/projects_using_ftgl.txt.bz2
/usr/include/FTGL/FTSimpleLayout.h
/usr/include/FTGL/FTLayout.h
/usr/include/FTGL/FTGLTextureFont.h
/usr/include/FTGL/FTGLPolygonFont.h
/usr/include/FTGL/FTGLPixmapFont.h
/usr/include/FTGL/FTGLOutlineFont.h
/usr/include/FTGL/FTGLExtrdFont.h
/usr/include/FTGL/FTBufferFont.h
/usr/include/FTGL/FTGLBitmapFont.h
/usr/include/FTGL/FTFont.h
/usr/include/FTGL/FTTextureGlyph.h
/usr/include/FTGL/FTPolyGlyph.h
/usr/include/FTGL/FTPixmapGlyph.h
/usr/include/FTGL/FTOutlineGlyph.h
/usr/include/FTGL/FTExtrdGlyph.h
/usr/include/FTGL/FTBufferGlyph.h
/usr/include/FTGL/FTBitmapGlyph.h
/usr/include/FTGL/FTGlyph.h
/usr/include/FTGL/FTPoint.h
/usr/include/FTGL/FTBuffer.h
/usr/include/FTGL/FTBBox.h
/usr/include/FTGL/ftgl.h
/usr/lib64/libftgl.so.2.1.3
/usr/lib64/pkgconfig/ftgl.pc
/usr/lib64/libftgl.so
/usr/lib64/libftgl.so.2

Hope it helps...

[bfx81]

Tnx z-man for the quick commit, anyway... looking at the armagetronad-0.3.0-r1.ebuild
is still required <=media-libs/ftgl-2.1.2.9999... probably to point at the custom ftgl in the overlay.

IMHO I think we can finally build (an enjoy again) armagetronad on gentoo in two ways:
1. restoring the ftgl ebuild and patches (hoping they are somewere in the svn)
2. understand why armagetronad gives the error in configure phase with ftgl-2.1.3

I can made the tests on gentoo and give you feedback, let me know if you have some advices.
Tnx in advance.
Fabio

[Tank Program]

Right-o. Old code is old and not compatible. The FTGL check is borked. Back porting from trunk. Try the attached ebuild and patch please. Just extract into your layman overlay games-action/armagetronad then run a ebuild armagetronad-0.3.0-r2.ebuild digest.

[Z-Man]

Oh, right, 0.3.0. Nobody should be using that. It has all the security flaws in there.
Also, the latest stable version in the overlay is outdated, so all the regular versions are insecure. Do we have someone to maintain it? If not, it would be better to just declare it abandoned for now.

Edit: Also, I believe 0.3.0 will crash with current FTGL if it tries to render accented letters, because 0.3.0 uses latin-1 and FTGL expects utf-8 and can't be configured otherwise.

[Tank Program]

Hrmm good point that it's all outdated. I can probably update and maintain seeing as I use Gentoo. I'll just need to find a slightly longer block of time...

[bfx81]

with armagetronad-0.3.0-r2.ebuild configure ok, but error building on amd64

Code: Select all

Portage 2.1.10.49 (default/linux/amd64/10.0/desktop, gcc-4.5.3, glibc-2.13-r4, 3.2.12-gentoo x86_64)
=================================================================
System uname: Linux-3.2.12-gentoo-x86_64-Intel-R-_Core-TM-_i5_CPU_750_@_2.67GHz-with-gentoo-2.0.3
Timestamp of tree: Mon, 16 Apr 2012 06:00:01 +0000
distcc 3.1 x86_64-pc-linux-gnu [disabled]
app-shells/bash:          4.2_p20
dev-java/java-config:     2.1.11-r3
dev-lang/python:          2.7.2-r3, 3.2.2
dev-util/cmake:           2.8.6-r4
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.0.3
sys-apps/openrc:          0.9.8.4
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.4_p6-r1, 1.9.6-r3, 1.10.3, 1.11.1
sys-devel/binutils:       2.21.1-r1
sys-devel/gcc:            4.5.3-r2
sys-devel/gcc-config:     1.5-r2
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r1
sys-kernel/linux-headers: 3.1 (virtual/os-headers)
sys-libs/glibc:           2.13-r4
Repositories: gentoo zugaina enlightenment java-overlay pcsx2 funroll-loops gamerlay-stable sunrise sabayon armagetron desktop-effects bfx
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -mtune=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"

Code: Select all

...
Making all in shttpd
make[4]: Entering directory `/tmp/portage/games-action/armagetronad-0.3.0-r2/work/build-client/src/thirdparty/shttpd'
x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd -I../../..   -I/usr/include/libxml2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/FTGL -I/usr/include/freetype2   -I/usr/include/freetype2 -DMT -DEMBEDDED -march=native -mtune=native -O2 -pipe  -MT libshttpd_a-shttpd.o -MD -MP -MF .deps/libshttpd_a-shttpd.Tpo -c -o libshttpd_a-shttpd.o `test -f 'shttpd.c' || echo '/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/'`shttpd.c
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c: In function ‘addenv’:
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c:2268:11: error: ‘ARG_MAX’ undeclared (first use in this function)
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c:2268:11: note: each undeclared identifier is reported only once for each function it appears in
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c: In function ‘spawncgi’:
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c:2286:11: error: ‘ARG_MAX’ undeclared (first use in this function)
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c:2297:2: warning: cast to pointer from integer of different size
/tmp/portage/games-action/armagetronad-0.3.0-r2/work/armagetronad-0.3.0/src/thirdparty/shttpd/shttpd.c:2297:2: warning: cast to pointer from integer of different size
make[4]: *** [libshttpd_a-shttpd.o] Errore 1
make[4]: Leaving directory `/tmp/portage/games-action/armagetronad-0.3.0-r2/work/build-client/src/thirdparty/shttpd'
make[3]: *** [all-recursive] Errore 1
make[3]: Leaving directory `/tmp/portage/games-action/armagetronad-0.3.0-r2/work/build-client/src/thirdparty'
make[2]: *** [all-recursive] Errore 1
make[2]: Leaving directory `/tmp/portage/games-action/armagetronad-0.3.0-r2/work/build-client/src'
make[1]: *** [all-recursive] Errore 1
make[1]: Leaving directory `/tmp/portage/games-action/armagetronad-0.3.0-r2/work/build-client'
make: *** [all] Errore 2
emake failed

Let me know if I can help in some way

[Z-Man]

Well, that's from the internal http server we put on ice by now. The error is an easy fix, but the warning indicates the code is not 64 bit compatible. So:

Oh, right, 0.3.0. Nobody should be using that.

IHMO, keeping it operational is not worth a single minute of dev time. I'd remove it.