Duncan Webb wrote:
Denis Oliver Kropp wrote:
Quoting Duncan Webb:
Anybody help me with this compile error on a amd64 system. Using cvs
version as of today.
gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../include
-I../../../include -I../../../lib -I../../../lib
-DDATADIR=\"/usr/share/directfb-0.9.24\"
-DMODULEDIR=\"/usr/lib/directfb-0.9.24\" -D_REENTRANT -Wall -O3
-ffast-math -pipe -D_GNU_SOURCE
-Werror-implicit-function-declaration -MT shmalloc.lo -MD -MP -MF
.deps/shmalloc.Tpo -c shmalloc.c -fPIC -DPIC -o .libs/shmalloc.o
In file included from /usr/include/linux/fusion.h:5,
from ../../../lib/fusion/fusion_internal.h:44,
from shmalloc.c:72:
/usr/include/asm/types.h:23: error: conflicting types for 'int64_t'
/usr/include/sys/types.h:194: error: previous declaration of
'int64_t' was here
/usr/include/asm/types.h:24: error: conflicting types for 'u_int64_t'
/usr/include/sys/types.h:200: error: previous declaration of
'u_int64_t' was here
The only workaround I know is to include <asm/types.h> before
<sys/types.h>.
Denis,
Sorry I gave you a crass answer last time. I think that the fix is as
you said add #include <asm/types.h> to include/dfb_types.h before the
sys/types.h. Would it be a problem to do this in CVS version of
dfb_types.h? I think that this was the only change I made to get
DirectFB to build on a pure64 platform. (With the server currently
down I can't fully check what I've modified from the CVS version)
I'm having problems building fusion module on amd64 all that I get
from the make is:
rm -f linux/drivers/char/fusion/Makefile
ln -s Makefile-2.6 linux/drivers/char/fusion/Makefile
make -C /lib/modules/2.6.12-elf-r3/build \
CPPFLAGS="-D__KERNEL__ -I`pwd`/linux/include
-I/lib/modules/2.6.12-elf-r3/build/include" \
SUBDIRS=`pwd`/linux/drivers/char/fusion modules
make[1]: Entering directory `/usr/src/linux-2.6.12-elf-r3'
Building modules, stage 2.
MODPOST
make[1]: Leaving directory `/usr/src/linux-2.6.12-elf-r3'
So there is not attempt to build the modules. I have no problems build
this on a 32bit system.
I've been a bit of a plonker here. The problem is that the
/usr/src/linux/.config still had the line:
CONFIG_FUSION_DEVICE=y
A simple sed and a make oldconfig fixed this problem
sed -i "/CONFIG_FUSION_DEVICE/d" .config
make oldconfig.
So this problem was not related to the 64bit build.
Regards,
Duncan
Is it possible to redirect the output from directfb to any framebuffer
device?
Thanks
Duncan
BTW some of the code in gfxdrivers/cle266 has CRLFs in the C source.
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users