Bug 25947 - Clanlib won't compile, errors on DirectFB source...
|
Bug#:
25947
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: x86
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: major
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: games@gentoo.org
|
Reported By: dane.elwell@gmail.com
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: Clanlib won't compile, errors on DirectFB source...
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2003-08-05 04:20 0000
|
Trying to emerge Clanlib, but I'm getting these errors during the compile:
Compiling Sources/Display/Display/DirectFB/display_directfb.cpp
Compiling Sources/Display/Display/DirectFB/target_directfb.cpp
Sources/Display/Display/DirectFB/target_directfb.cpp: In member function
`virtual unsigned int CL_Target_DirectFB::get_width() const':
Sources/Display/Display/DirectFB/target_directfb.cpp:109: invalid conversion
from `int*' to `unsigned int*'
Sources/Display/Display/DirectFB/target_directfb.cpp: In member function
`virtual unsigned int CL_Target_DirectFB::get_height() const':
Sources/Display/Display/DirectFB/target_directfb.cpp:118: invalid conversion
from `int*' to `unsigned int*'
Sources/Display/Display/DirectFB/target_directfb.cpp: In member function `void
CL_Target_DirectFB::Clear(float, float, float, float)':
Sources/Display/Display/DirectFB/target_directfb.cpp:268: invalid conversion
from `int*' to `unsigned int*'
Sources/Display/Display/DirectFB/target_directfb.cpp:268: invalid conversion
from `int*' to `unsigned int*'
Compiling Sources/Display/Input/DirectFB/keyboard_directfb.cpp
make: *** [Libs/Intermediate/target_directfb.o] Error 1
make: *** Waiting for unfinished jobs....
!!! ERROR: dev-games/clanlib-0.6.5 failed.
!!! Function src_compile, Line 68, Exitcode 2
!!! (no error message)
xerxes root #
Reproducible: Always
Steps to Reproduce:
1. emerge clanlib (or in my case, Pingus. Clanlib was dependancy)
2.
3.
Actual Results:
Compile stopped.
Expected Results:
Successfully compiled Clanlib.
Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1)
=================================================================
System uname: 2.4.20-gentoo-r5 i686 Intel(R) Pentium(R) 4 CPU 2.53GHz
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="oss 3dnow arts foomaticdb kde libg++ motif nls pdflib quicktime zlib gdbm
berkdb slang readline tcpd pam esd gnome qt aalib acpi alsa apm avi cdr crypt
dga directfb dvd encode fbcon gd ggi gif gtk gtkhtml imap imlib java jpeg libwww
mad mikmod mmx mozilla mpeg ncurses opengl oggvorbis pdf perl png python sdl
spell sse ssl svga tiff truetype usb wmf X xml xml2 xmms xv x86 -gpm -cups"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
ACCEPT_KEYWORDS="x86"
MAKEOPTS="-j2"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="sandbox ccache"
As a workaround you could try it with USE="-directfb" emerge pingus...
investigating.
Could you please retry with the latest DirectFB Version? Would be a good reason
to make it stable. Works fine for me.
Yep, using the ~x86 version of DirectFB worked. Clanlib compiled successfully.
;)
Cheers.
patrick: i'm always game for making latest directfb stable ;)
SpanKY: Looks like your fix in Comment #3 on Bug #24454 broke DirectFB support
on currently stable DirectFB version. From DirectFB 0.9.18 on it seems to be
ok, this version is in portage for more than a month. I'll declare it stable
for x86 (though it does not work with mepg3 correctly, see bug #25097).
mpeg3 support was resolved ...
-v, please. which problem was resolved for which version of which package?
thought you were on the cc for it ... Bug 25097
mpeg3 support is still broken for the currently stable directfb version. Didn't
want to wait one month, so I didn't mess with that ebuild. The fix mentioned in
bug #25097 is just for the ~x86 version - tried to be conservative. Perhaps
it's time to call this bug fixed now.