[Jde] mas datos de #200

JoseMaria jmplaza en gsyc.es
Mie Dic 17 19:49:29 CET 2008 

Claro, aqui van mis pistas.

He instalado jde 4.3 (release 259) desde svn en dos máquinas diferentes
con Ubuntu 8.04. Una es un PC HP con una mochila bluetooth USB y otra
portátil Asus que tiene bluetooth incorporado). En ambos casos la
instalación se rompe en el mismo sitio.

Al hacer el ./configure de jde, en lo que se refiere al driver wiimote:
configure: **** Checking driver wiimote:
checking cwiid.h usability... no
checking cwiid.h presence... no
checking for cwiid.h... no
checking for main in -lcwiid... yes
configure: error: --enable-drivers-wiimote was given, but there was
errors: , cwiid.h not found
See `config.log' for more details.

Obsérvese cómo la biblioteca sí que la encuentra. Sin embargo no
encuentra cwiid.h, aunque sí está en la máquina. De hecho pertenece al
paquete libcwiid1-dev, que está instalado.  

$ dpkg -S cwiid.h
libcwiid1-dev: /usr/include/cwiid.h




Al mirar en config.log para ver los detalles aparece:

configure:23502: **** Checking driver wiimote:
configure:23519: checking cwiid.h usability
configure:23536: gcc -c -g -O2 -pedantic -Wall -pthread -D_REENTRANT
-D_POSIX_PTHREAD_SEMANTICS  conftest.c >&5
In file included from conftest.c:60:
/usr/include/cwiid.h:63:48: error: bluetooth/bluetooth.h: No such file
or directory
In file included from conftest.c:60:
/usr/include/cwiid.h:295: error: expected specifier-qualifier-list
before 'bdaddr_t'
/usr/include/cwiid.h:311: error: expected ')' before '*' token
/usr/include/cwiid.h:345: error: expected ')' before '*' token

Vamos, que no encuentra bluetooth.h, que está referenciado en cwiid.h.
Sin embargo ese fichero sí está en el sistema, pertenece al paquete
linux-headers-2.6.24-22, que está perfectamente instalado. El 2.6.24-22
es justo el kernel que tengo instalado.

$> dpkg -S bluetooth.h
linux-headers-2.6.24-22: /usr/src/linux-headers-2.6.24-22/include/net/bluetooth/bluetooth.h
linux-headers-2.6.24-21: /usr/src/linux-headers-2.6.24-21/include/net/bluetooth/bluetooth.h

Adjunto el fichero config.log y "miconfiguracion" con la salida que veo
por pantalla al ejectuar ./configure . Creo que Eduardo y Jamal han
instalado el driver wiimote sin mayores problemas. Eduardo, qué dice el
configure cuando instalas jde en tu máquina??

Saludos,

JoseMaria
PD: Por cierto, en config.log aparecen cosas como 
| #define PACKAGE_NAME "jdec"
| #define PACKAGE_TARNAME "jdec"
| #define PACKAGE_VERSION "4.2"
| #define PACKAGE_STRING "jdec 4.2"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE "jdec"
| #define VERSION "4.2"

¿No habría que cambiarlo por 4.3?

On Wed, 2008-12-17 at 15:34 +0100, Roberto Calvo wrote:
> Creo que este ticket le pusimos en la última reunión de desarrolladores,
> y era porque lo comento Jose María.
> 
> Jose María, cuando tengas un ratillo dile a David como reproducirlo.
> 
> El mié, 17-12-2008 a las 13:37 +0100, David Lobato escribió:
> > A ver si podemos acelerar un poco esto...
> > 
> > Quiero dejarlo cerrado antes de irme de vacas, si no, ya hasta Enero
> > no podré tocarlo.
> > 
> > 
> > Saludetes!
> > 
> > El 15 de diciembre de 2008 11:52, David Lobato <dav.lobato en gmail.com>
> > escribió:
> >         ¿A quien le había fallado la comprobación del driver wiimote?
> >         ¿Puede aportar mas información? No puedo reproducirlo en mi
> >         máquina.
> >         Agradecería que adjuntaseis el config.log que se genera tras
> >         el error.
> >         
> >         Saludetes. 
> > 
> > _______________________________________________
> > Jde-developers mailing list
> > Jde-developers en gsyc.es
> > http://gsyc.escet.urjc.es/cgi-bin/mailman/listinfo/jde-developers
> _______________________________________________
> Jde-developers mailing list
> Jde-developers en gsyc.es
> http://gsyc.escet.urjc.es/cgi-bin/mailman/listinfo/jde-developers
-- 
http://gsyc.es/jmplaza 
Universidad Rey Juan Carlos

------------ próxima parte ------------
Se ha borrado un mensaje que no está en formato texto plano...
Nombre     : config.log
Tipo       : text/x-log
Tamaño     : 44044 bytes
Descripción: no disponible
Url        : http://gsyc.escet.urjc.es/pipermail/jde-developers/attachments/20081217/96fc97bd/attachment-0001.bin 
------------ próxima parte ------------
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking for ANSI C header files... (cached) yes
checking for dlfcn.h... (cached) yes
checking for dlopen in -ldl... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking for pthread_create in -lpthread... yes
checking math.h usability... yes
checking math.h presence... yes
checking for math.h... yes
checking for floor in -lm... yes
configure: *** Checking drivers:
configure: **** Checking driver evi:
configure: **** Checking driver firewire:
checking for FIREWIRE... yes
configure: **** Checking driver gazebo:
checking gazebo.h usability... yes
checking gazebo.h presence... yes
checking for gazebo.h... yes
checking for main in -lgazebo... yes
configure: **** Checking driver imagefile:
configure: **** Checking driver mplayer:
checking for mplayer... /usr/bin/mplayer
checking for mencoder... /usr/bin/mencoder
configure: **** Checking driver networkclient:
configure: **** Checking driver pantilt:
configure: *** Checking driver player:
checking libplayerc/playerc.h usability... yes
checking libplayerc/playerc.h presence... yes
checking for libplayerc/playerc.h... yes
checking for main in -lplayerc... yes
checking for main in -lplayerxdr... yes
checking for main in -lplayererror... yes
configure: **** Checking driver video4linux:
configure: **** Checking driver wiimote:
checking cwiid.h usability... no
checking cwiid.h presence... no
checking for cwiid.h... no
checking for main in -lcwiid... yes
configure: error: --enable-drivers-wiimote was given, but there was errors: , cwiid.h not found
See `config.log' for more details.

More information about the Jde-developers mailing list