Re: [CBLX] Compilation speech-dispatcher

[Pierre Lorenzon <devel@xxxxxxxxxxxxxxxxxxxx>]

From: Raphaël POITEVIN <raphael.poitevin@xxxxxxxxx>
Subject: [CBLX] Compilation speech-dispatcher
Date: Thu, 1 Sep 2011 20:28:57 +0200

> Bonjour la liste, peut-être particulièrement Pierre,
> 
> Je travaille sur une Debian squeeze.
> Je vais être amené à bricoler avec speech-dispatcher. Or, je n'arrive
> pas à résoudre tous les problèmes détectés par configure. Il me dit
> qu'il ne trouve pas libtool, ni glib2.0.
> 
> Voici la sortie du configure :
> 
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> 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 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... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking how to run the C preprocessor... gcc -E
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -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 limits.h usability... yes
> checking limits.h presence... yes
> checking for limits.h... yes
> checking sys/ioctl.h usability... yes
> checking sys/ioctl.h presence... yes
> checking for sys/ioctl.h... yes
> checking sys/time.h usability... yes
> checking sys/time.h presence... yes
> checking for sys/time.h... yes
> checking for unistd.h... (cached) yes
> checking for an ANSI C-conforming const... yes
> checking whether time.h and sys/time.h may both be included... yes
> checking for a Python interpreter with version >= 2.4... python
> checking for python... /usr/bin/python
> checking for python version... 2.6
> checking for python platform... linux2
> checking for python script directory... ${prefix}/lib/python2.6/dist-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.6/dist-packages
> checking whether gcc needs -traditional... no
> checking for select... yes
> checking for socket... yes
> checking whether make sets $(MAKE)... (cached) yes
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for a sed that does not truncate output... /bin/sed
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for ar... ar
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) 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
> Fixing libtool for -rpath problems.
> ./configure: line 10990: libtool: No such file or directory
> mv: cannot stat `libtool-2': No such file or directory
> chmod: cannot access `libtool': No such file or directory
> checking for sqrt in -lm... yes
> 
> checking for main in -ldl... yes
> 
> checking for main in -ldotconf... yes
> 
> checking for g_list_append in -lglib-2.0... no
> *** Required Glib-2.0 library missing! See INSTALL .
> 
> Pourtant, le paquet libtool semble être installé, et glib, qui
> n'apparaît pas sous ce nom mais sous le nom de libglib est installé
> également.
> 
> Quelle est ma bévue ?

  De compiler sous debian alors que debian est prévu pour
  installer des .deb ... C'est tout et c'est tant pis pour toi
  ! Euh !!!!! Enfin ! Excuse-moi ! Mais effectivement ça me
  semble être un problème de packaging et du coup
  d'architecture du package manager de debian. J'ai connu ces
  problèmes mais moi j'étais exclusivement en .tar.gz +
  configure + make + make install. Alors je savais résoudre il
  fallait installer les librairies incriminées. Mais si elle
  sont là et que le ./configure de speech-dispatcher ne les
  trouve pas je ne sais pas.


  Mais ce qui m'intéresse beaucoup plus c'est qu-qu'ext-ce que
  donc que tu veux bricoler avec speech-dispatcher ...

  Pierre




> -- 
> Raphaël
> 
> ---
> -- 
>    CarrefourBLinuX MailingListe 
>    Pour obtenir de l'aide, envoyez le sujet  help  à: 
>    carrefourblinux-request@xxxxxxxxxxxxxxxxxxx
>    Archives: 
>    http://listengine.tuxfamily.org/lists.tuxfamily.org/carrefourblinux
> 

---
-- 
   CarrefourBLinuX MailingListe 
   Pour obtenir de l'aide, envoyez le sujet  help  �
   carrefourblinux-request@xxxxxxxxxxxxxxxxxxx
   Archives: 
   http://listengine.tuxfamily.org/lists.tuxfamily.org/carrefourblinux