Ubuntu-fr

sona

Re : [RESOLU] compilation d'un programme ?

Bonjour,

oui, mais pour Dapper dans Symaptic il n'y a que la version2.2 et j'ai mis récemment les dépots à  jour car j'en avais un très grand nombre qui devenaient inutile et j'ai fait un peu le ménage, ce qui je pense n'était du luxe, du coup peut-être qu 'il en manque un...ou que simplement la version de Gimp 2.4 en .deb n'existe pas car je suis allé sur le site officiel de Gimp il n'y a que les sources (pour une 64 bits ne l'oubilons pas !)

@+

bishop

Re : [RESOLU] compilation d'un programme ?

Salut sona
Je suis allé sous Gutsy pour voir les dépendances de Gimp 2.4.

Gimp 2.4 ne peut être compilé sous Dapper parce que la version de GTK est trop basse. Voir le ./configure.
Mais même si le ./configure était passé, il y aurait certainement eu des erreurs au make pour les mêmes raison... Beaucoup de dépendances ont une version trop basses et de plus il est impossible d'installer certaines librairies de développement nécessaires à  la compilation.

Test
Installation des dépendances :

sudo apt-get install libc6-dev libgimp2.0-dev libaal-dev libart-dev libatk1.0-dev libcairo2-dev libexif-dev libfontconfig1-dev libfreetype6-dev libglib2.0-dev libgtk2.0-dev libjpeg62-dev liblcms1-dev libmng-dev libpango1.0-dev libpng12-dev librsvg2-dev libtiff4-dev libwmf-dev libx11-dev libxcursor-dev libxdamage-dev libxext-dev libxfixes-dev libxi-dev libxinerama-dev libxmu-dev libxpm-dev libxrandr-dev libxrender-dev zlib1g-dev libdbus-1-2 libdbus-glib-1-2 libhal1 libpoppler1-glib libxcomposite1

-----------------------------------------------------------

Pour amd64 installer (ou remplacer) ???
libc6-dev par  libc6-dev-amd64

Il faut peut être installer le paquet linux32 ???
linux32
Wrapper to set the execution domain
the linux32 tools allows 64bit systems with support for 32 bit
applications to set the personality to the 32 bit native type.

For instance, on an amd64 or ia64 machine, commands run with this
wrapper will think the machine type is i686, as returned by uname -m.

On systems without support for the PER_LINUX_32 execution domain, this
program has no effect.

-----------------------------------------------------------

Librairies .dev qui ne peuvent être installées :
libdbus-1-dev
  Dépend : libdbus-1-2 (=0.60-6ubuntu8.1) mais 0.62-bmp1ubuntu1 doit être installé

libdbus-glib-1-dev:
  Dépend : libdbus-glib-1-2 (=0.60-6ubuntu8.1) mais 0.62-bmp1ubuntu1 doit être installé
Dépend : libdbus-1-dev mais ne doit pas être installé

libhal-dev:
Dépend : libdbus-1-dev mais ne doit pas être installé

libxcomposite-dev:
  Dépend : libxcomposite1 (=1:0.2.2.2-0ubuntu2) mais 1:0.3-0ubuntu1 doit être installé

-----------------------------------------------------------

 _________________________________________
/ Bonjour bishop02, nous sommes le        \
| mercredi 9 janvier 2008, et il est : 18 | \ h 08  /
 -----------------------------------------
   \
    \
        .--.
       |o_o |
       |:_/ |
      //   \ \
     (|     | )
    /'\_   _/`\
    \___)=(___/

bishop02@Ubuntu-Dapper:~/gimp-2.4.3$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
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 for style of include used by make... GNU
checking dependency style of gcc... gcc3
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 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... g77
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether g77 accepts -g... yes
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... no
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
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for g77 option to produce PIC... -fPIC
checking if g77 PIC flag -fPIC works... yes
checking if g77 static flag -static works... yes
checking if g77 supports -c -o file.o... yes
checking whether the g77 linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether to enable maintainer-specific portions of Makefiles... no
checking for target architecture... i686-pc-linux-gnu
checking for some Win32 platform... no
checking for native Win32... no
checking for library containing strerror... none required
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 for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking whether to turn on debugging... no
checking whether to turn on profiling... no
checking whether gcc understands -Wdeclaration-after-statement... yes
checking whether gcc understands -Wmissing-prototypes... yes
checking whether gcc understands -Wmissing-declarations... yes
checking whether gcc understands -Winit-self... yes
checking whether gcc understands -Wpointer-arith... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking whether time.h and sys/time.h may both be included... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking for sys/wait.h... (cached) yes
checking for unistd.h... (cached) yes
checking for pid_t... yes
checking return type of signal handlers... void
checking for vprintf... yes
checking for _doprnt... no
checking for working alloca.h... yes
checking for alloca... yes
checking for difftime... yes
checking for putenv... yes
checking for mmap... yes
checking whether binary relocation support should be enabled... no
checking for _NL_MEASUREMENT_MEASUREMENT... yes
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for XML::Parser... okchecking for GTK+ - version >= 2.10.13... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GTK+ is incorrectly installed.
configure: error: Test for GTK+ failed. See the file 'INSTALL' for help.
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for catalogs to be installed...  ar bg ca cs da de dz el en_CA en_GB eo es et eu fa fi fr ga gl gu he hu hr id it ja km ko lt mk ms nb ne nl oc pa pl pt pt_BR ro ru rw sk sl sr sr@Latn sv tr tt uk vi xh yi zh_CN zh_TW
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.12.3... yes (version 2.12.11)
checking for GMODULE_NO_EXPORT... yes
checking if GLib is version 2.15.0 or newer... no
checking for bind_textdomain_codeset... (cached) yes
checking for X... libraries /usr/X11R6/lib, headers
checking whether -R must be followed by a space... neither works
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for pkg-config... /usr/bin/pkg-config
checking for GTK+ - version >= 2.10.13... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GTK+ is incorrectly installed.
configure: error: Test for GTK+ failed. See the file 'INSTALL' for help.

Dernière modification par bishop (Le 09/01/2008, à 19:58)

---

La plus grande surprise que puisse faire un con c'est de faire une pause.

sona

Re : [RESOLU] compilation d'un programme ?

Bonsoir ,

et merci pour tous ces tuyaux, mais je pense que l'expèrience s'arrête là  car comme tu le dis ,il y a des version inférieures de librairies pour être compatible avec Gimp 2.4 il me donne un message identique mais qui porte sur GlIB:

:/usr/local/src/gimp-2.4.3# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
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 for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
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 -m elf_x86_64) 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... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) 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 -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking whether to enable maintainer-specific portions of Makefiles... no
checking for target architecture... x86_64-unknown-linux-gnu
checking for some Win32 platform... no
checking for native Win32... no
checking for library containing strerror... none required
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 for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking whether to turn on debugging... no
checking whether to turn on profiling... no
checking whether gcc understands -Wdeclaration-after-statement... yes
checking whether gcc understands -Wmissing-prototypes... yes
checking whether gcc understands -Wmissing-declarations... yes
checking whether gcc understands -Winit-self... yes
checking whether gcc understands -Wpointer-arith... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for ANSI C header files... (cached) yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking whether time.h and sys/time.h may both be included... yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/times.h usability... yes
checking sys/times.h presence... yes
checking for sys/times.h... yes
checking for sys/wait.h... (cached) yes
checking for unistd.h... (cached) yes
checking for pid_t... yes
checking return type of signal handlers... void
checking for vprintf... yes
checking for _doprnt... no
checking for working alloca.h... yes
checking for alloca... yes
checking for difftime... yes
checking for putenv... yes
checking for mmap... yes
checking whether binary relocation support should be enabled... no
checking for _NL_MEASUREMENT_MEASUREMENT... yes
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking locale.h usability... yes
checking locale.h presence... yes
checking for locale.h... yes
checking for LC_MESSAGES... yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for ngettext in libc... yes
checking for dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... (cached) /usr/bin/msgfmt
checking for dcgettext... yes
checking if msgfmt accepts -c... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... (cached) /usr/bin/xgettext
checking for catalogs to be installed...  ar bg ca cs da de dz el en_CA en_GB eo es et eu fa fi fr ga gl gu he hu hr id it ja km ko lt mk ms nb ne nl oc pa pl pt pt_BR ro ru rw sk sl sr sr@Latn sv tr tt uk vi xh yi zh_CN zh_TW
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.16... yes
checking for GLIB - version >= 2.12.3... no
*** Could not run GLIB test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GLIB is incorrectly installed.
configure: error: Test for GLIB failed. See the file 'INSTALL' for help.

en revanche toutes les install des dépendances se sont faites sans problèmes, et il n'y a pas eu besoin de remplacer libc6-dev  par libc6-dev-amd64.

merci , merci beaucoup , ça au moins fonctionner pour makehuman et animorph, c'était au départ l'essentiel.

@+

Dernière modification par sona (Le 10/01/2008, à 01:47)

Gimli

Re : [RESOLU] compilation d'un programme ?

Pour poursuivre le sujet : Je suis retourné sous Feisty (bicoz wifi) et afin d'installer GIMP 2.43 à  partir des sources,  j'ai chargé les sources de GLIB 2.14.5, installées avec un

./configure
sudo make
sudo install
sudo ldconfig

Le message retourné par le ./configure de gimp 2.43 est le suivant :

checking for GLIB - version >= 2.12.3...
*** 'pkg-config --modversion glib-2.0' returned 2.14.5, but GLIB (2.12.11)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files
no
configure: error: Test for GLIB failed. See the file 'INSTALL' for help.

J'imagine qu'en désinstallant la version antérieure (GLIB 2.12.11) ça devrait résoudre cette erreur...

D'autant que le ./configure stoppant à  la première erreur rencontrée, s'il y en a d'autres, je ne les verrai pas...

Question : comment désintalle-t-on proprement une version antérieure après avoir installée une plus récente ?
Dois-je passer par Adept qui me vire glib avec tout un paquet d'autres trucs innombrables (269, en fait) ?
Peut-on simplmeent virer une version antérieure sachant que la suivante est déjà  là  pour prendre le relais ?

Dernière modification par Gimli (Le 12/01/2008, à 18:42)

---

Plus petit, tu meurs ;)

bishop

Re : [RESOLU] compilation d'un programme ?

Gimli
Désolé, c'est en dehors de mes compétences et je ne veux surtout pas t'induire en erreur.

Dernière modification par bishop (Le 12/01/2008, à 21:07)

---

La plus grande surprise que puisse faire un con c'est de faire une pause.

sona

Re : [RESOLU] compilation d'un programme ?

bonjour,

peut-être qu'il faudrait d'abord supprimer la version antérieure avec synaptic ou apt, puis compiler la nouvelle, si la compil ne fonctionne pas on peut toujours se servir de synaptic ou apt pour réinstaller la version précédente, j'essaierai puis je donnerais des nouvelles ça peut être interressant de voir ce qui se passe.

Dernière modification par sona (Le 13/01/2008, à 10:02)

Gimli

Re : [RESOLU] compilation d'un programme ?

Toujours dans ma tentative d'installer gimp 2.4.3 via les sources, j'ai tenté d'enlever le glib en version 2.12.11 (ce que m'indiquait le message d'erreur après un ./configure ... et voilà  ma tentative ainsi que le message retourné :

checking for GLIB - version >= 2.12.3...
*** 'pkg-config --modversion glib-2.0' returned 2.14.5, but GLIB (2.12.11)
*** was found! If pkg-config was correct, then it is best
*** to remove the old version of GLib. You may also be able to fix the error
*** by modifying your LD_LIBRARY_PATH enviroment variable, or by editing
*** /etc/ld.so.conf. Make sure you have run ldconfig if that is
*** required on your system.
*** If pkg-config was wrong, set the environment variable PKG_CONFIG_PATH
*** to point to the correct configuration files
no
configure: error: Test for GLIB failed. See the file 'INSTALL' for help.
navillot@navillot-portable:~/Photos/gimp-2.4.3/gimp-2.4.3$ sudo apt-get remove libglib2.0-0=2.12.11
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture de l'information d'état... Fait
E: La version « 2.12.11 » de « libglib2.0-0 » n'a pu être trouvée

Donc : comment on enlève quelque chose qui semble ne plus exiter ?
Ou comment dit-on que ce "glib" n'existe plus dans sa version 2.12.12 mais qu'on a bien mis une version 2.14.5 à  sa place... ?

---

Plus petit, tu meurs ;)

sona

Re : [RESOLU] compilation d'un programme ?

bonsoir,

là je ne suis pas compétent et n'ai pas eu le temps de faire l'expèrience aussi pour pouvoir comparer...désolé...

Coolgeek

Re : [RESOLU] compilation d'un programme ?

le message te dis qu'il te faut GLIB version 2.13.3 ou superieur. arrange toi pour avoir cette librairie (en la recuperant sur le ste officiel et en la compilant ou en ayant le paquet qui va bien)

Gimli

Re : [RESOLU] compilation d'un programme ?

Solution trouvée !
solution via google...

il faut redéfinir le LD_LIBRARY_PATH, ce que j'avais fait selon la méthode donnée là  o๠j'ai chargé les sources...

En fait, il faudrait faire comme suit :

LD_LIBRARY_PATH=/usr/local/lib:/lib:/usr/lib:/usr/X11R6/lib
     export LD_LIBRARY_PATH

Bon, maintenant, c'est GTK qui ne va plus...

checking for GTK+ - version >= 2.10.13... no
*** Could not run GTK+ test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GTK+ is incorrectly installed.
configure: error: Test for GTK+ failed. See the file 'INSTALL' for help.

---

Plus petit, tu meurs ;)

Gimli

Re : [RESOLU] compilation d'un programme ?

Pour finir, et comme ça saoule quelque peu de gérer des dépendances en chaînes (pour gimp faut glib mais aussi gtk+ qui demande pango qui demande libpng (présent mais pas reconnu...)) dont certaines semble insolubles (spa du café), j'ai fait un brin de méthode bourrin... j'ai remplacé feisty par gutsy dans mon sources.list, juste pour que Adept me charge et configure Gimp avec ses dépendances (en gérer 2 ou 3 à la mano, ok, mais des dizaines....).

C'est fait, je suis content !

---

Plus petit, tu meurs ;)