Conversation
precedente ou
suivante
Comment savoir compiler
Envoyé par:
xunil2003
Salut,
Je voudrais installer captive mais lorsque je tape ./configure il maffiche le message ci dessous,
sa veut dire quoi ce message et comment faire ?
[laurent@linux-laurent captive-1.1.5]$ ./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 whether to enable maintainer-specific portions of Makefiles... no
checking for gcc3... no
checking for gcc-3.0... no
checking for gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
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 strerror in -lcposix... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
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 egrep... 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 recognise dependent libraries... pass_all
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++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
[laurent@linux-laurent captive-1.1.5]$
Je voudrais installer captive mais lorsque je tape ./configure il maffiche le message ci dessous,
sa veut dire quoi ce message et comment faire ?
[laurent@linux-laurent captive-1.1.5]$ ./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 whether to enable maintainer-specific portions of Makefiles... no
checking for gcc3... no
checking for gcc-3.0... no
checking for gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
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 strerror in -lcposix... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
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 egrep... 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 recognise dependent libraries... pass_all
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++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
[laurent@linux-laurent captive-1.1.5]$
Poste le Wednesday 17 November 2004 16:28:42
Re: Comment savoir compiler
Envoyé par:
AlSim
Citation
xunil2003
checking for gcc3... no
checking for gcc-3.0... no
checking for gcc... gcc
[...]
checking dependency style of gcc... gcc3
[...]
checking whether we are using the GNU C++
compiler... no
[...]
checking how to run the C++ preprocessor...
/lib/cpp
configure: error: C++ preprocessor "/lib/cpp"
fails sanity check
En gros, j'ai laissé les lignes importantes.
Il semble qu'il y ait une version un peu spéciale de gcc (le compilateur C/C++ de GNU) installée sur ta machine. La meilleure solution si tu veux VRAIMENT compiler serait de réinstaller gcc3 et g++, après ça devrait marcher.
Si tu es sous Mandrake, il faudrait que tu recherches ce genre de paquetages avec RPMdrake (cherche GCC et installe ceux dont la priorité est 'obligatoire'). Pour une autre distrib' RPM, c'est à peu près la même chose.
Mais n'oublie pas que installer un RPM est plus simple et plus rapide qu'une compilation à partir des sources parce qu'il y a la gestion des dépendances ... et pas besoin de compiler : c'est des paquetages binaires !
Essaie plutôt, si tu as une distribution RPM, de télécharger captive sous cette forme (cherche sur rpmfind.net).
Si tu n'as pas une distribution RPM (ex. Debian), utilise la commande appropriée (apt-get pour Debian, emerge pour Gentoo mais ça m'étonnerait que tu en aies une vu ton pb., ...)
Wala.
Poste le Wednesday 17 November 2004 16:56:37
Re: Comment savoir compiler
Envoyé par:
P Hoquet
Salut,
J'ai l'impression qu'on tourne en rond. Il me semble avoir déjà écrit qu'il manquait gcc-c++.
Pour voir j'ai downloadé le fameux captive (captive-1.1.5.tar.gz), et j'ai lance le configure sans aucun problème.
Je suis encore sous mdk 9.2.
Pour gcc j'ai:
$ rpm - qa | grep gcc
gcc-c++-3.3.1-2mdk
gcc-cpp-3.3.1-2mdk
libgcc1-3.3.1-2mdk
gcc-3.3.1-2mdk
Pour glib:
$ rpm -qa | grep glib
glibc-devel-2.3.2-14mdk
libglib1.2-1.2.10-11mdk
glibc-i18ndata-2.3.2-14mdk
glib-gettextize-2.2.3-1mdk
glibc_lsb-2.3.1-1mdk
libglib1.2-devel-1.2.10-11mdk
glibc-2.3.2-14mdk
libglib2.0_0-2.2.3-1mdk
libglib2.0_0-devel-2.2.3-1mdk
Et j'ai aussi:
$ rpm -qa | grep c++
gcc-c++-3.3.1-2mdk
libstdc++5-devel-3.3.1-2mdk
libstdc++2.10-2.96-0.83mdk
libstdc++5-3.3.1-2mdk
Voilà, j'espère que ça pourra t'aider.
Tu ne doit pas avoir la même version que la mienne mais prendre celles qui correspondent à ta version d mandrake.
Surtout respecter la concordance des versions.
En principe tput ça est installé d'office si lors de l'install de la distribution on coche: installer les package de développement.
J'ai l'impression qu'on tourne en rond. Il me semble avoir déjà écrit qu'il manquait gcc-c++.
Pour voir j'ai downloadé le fameux captive (captive-1.1.5.tar.gz), et j'ai lance le configure sans aucun problème.
Je suis encore sous mdk 9.2.
Pour gcc j'ai:
$ rpm - qa | grep gcc
gcc-c++-3.3.1-2mdk
gcc-cpp-3.3.1-2mdk
libgcc1-3.3.1-2mdk
gcc-3.3.1-2mdk
Pour glib:
$ rpm -qa | grep glib
glibc-devel-2.3.2-14mdk
libglib1.2-1.2.10-11mdk
glibc-i18ndata-2.3.2-14mdk
glib-gettextize-2.2.3-1mdk
glibc_lsb-2.3.1-1mdk
libglib1.2-devel-1.2.10-11mdk
glibc-2.3.2-14mdk
libglib2.0_0-2.2.3-1mdk
libglib2.0_0-devel-2.2.3-1mdk
Et j'ai aussi:
$ rpm -qa | grep c++
gcc-c++-3.3.1-2mdk
libstdc++5-devel-3.3.1-2mdk
libstdc++2.10-2.96-0.83mdk
libstdc++5-3.3.1-2mdk
Voilà, j'espère que ça pourra t'aider.
Tu ne doit pas avoir la même version que la mienne mais prendre celles qui correspondent à ta version d mandrake.
Surtout respecter la concordance des versions.
En principe tput ça est installé d'office si lors de l'install de la distribution on coche: installer les package de développement.
Poste le Wednesday 17 November 2004 17:02:39
Re: Comment savoir compiler
Envoyé par:
xunil2003
Salut,
Oui c'est vrai je tourne en rond, j'ai installé sur ma MDK 10.1 gcc-c++ il m'affiche le message ci dessous, dit moi ce qu'il me reste a faire,regarde aussi mes rpm -qa grep.
Merci d'avance, salutations
rpm -qR kernel-source
le paquetage kernel-source n'est pas installé
[laurent@linux-laurent captive-1.1.5]$
rpm -qa | grep kernel
kernel24-tmb-source-2.4.26-1.tmb.2mdk
kernel-2.6.8.1.10mdk-1-1mdk
rpm -qa | grep glib
libdbus-glib-1_0-0.22-1mdk
libtaglib0-1.2-1mdk
libglib2.0_0-2.4.6-1mdk
libglib1.2-1.2.10-13mdk
glibc-2.3.3-20mdk
glibc-i18ndata-2.3.3-21mdk
glibc-devel-2.3.3-20mdk
glib-gettextize-2.5.5-0.2.mdk10.1.thac
rpm -qa | grep c++
libstdc++6-devel-3.4.1-3mdk
libstdc++6-3.4.1-3mdk
libstdc++5-3.3.4-1mdk
rpm -qa | grep gcc
libgcc1-3.4.1-3mdk
gcc-3.4.1-3mdk
gcc-c++-3.4.1-3mdk
gcc-cpp-3.4.1-3mdk
[laurent@linux-laurent captive-1.1.5]$
gcc-c++-3.4.1-3mdk
libflac++4-1.1.1-0.beta1.1mdk
rpm -qa | grep imlib
imlib-1.9.14-9mdk
libimlib2_1-loaders-1.1.0-3mdk
libimlib2_1-filters-1.1.0-3mdk
libimlib1-1.9.14-9mdk
libimlib2_1-1.1.0-3mdk
Le message quand je tape ./configure
-------------------------------------
[laurent@linux-laurent captive-1.1.5]$ ./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 whether to enable maintainer-specific portions of Makefiles... no
checking for gcc3... no
checking for gcc-3.0... no
checking for gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
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 strerror in -lcposix... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
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 egrep... 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 recognise dependent libraries... pass_all
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 f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fl32... no
checking for af77... no
checking for fort77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for lf95... no
checking for g95... 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... 32768
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 static flag works... yes
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 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 how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
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++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
appending configuration tag "F77" to libtool
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 dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... no
checking for pkg-config... /usr/bin/pkg-config
checking for perl5... /usr/bin/perl5
checking for pod2man... /usr/bin/pod2man
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for GLIB - version >= 2.0.0... 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: Captive requires glib-2.0 library.
[laurent@linux-laurent captive-1.1.5]$
Oui c'est vrai je tourne en rond, j'ai installé sur ma MDK 10.1 gcc-c++ il m'affiche le message ci dessous, dit moi ce qu'il me reste a faire,regarde aussi mes rpm -qa grep.
Merci d'avance, salutations
rpm -qR kernel-source
le paquetage kernel-source n'est pas installé
[laurent@linux-laurent captive-1.1.5]$
rpm -qa | grep kernel
kernel24-tmb-source-2.4.26-1.tmb.2mdk
kernel-2.6.8.1.10mdk-1-1mdk
rpm -qa | grep glib
libdbus-glib-1_0-0.22-1mdk
libtaglib0-1.2-1mdk
libglib2.0_0-2.4.6-1mdk
libglib1.2-1.2.10-13mdk
glibc-2.3.3-20mdk
glibc-i18ndata-2.3.3-21mdk
glibc-devel-2.3.3-20mdk
glib-gettextize-2.5.5-0.2.mdk10.1.thac
rpm -qa | grep c++
libstdc++6-devel-3.4.1-3mdk
libstdc++6-3.4.1-3mdk
libstdc++5-3.3.4-1mdk
rpm -qa | grep gcc
libgcc1-3.4.1-3mdk
gcc-3.4.1-3mdk
gcc-c++-3.4.1-3mdk
gcc-cpp-3.4.1-3mdk
[laurent@linux-laurent captive-1.1.5]$
gcc-c++-3.4.1-3mdk
libflac++4-1.1.1-0.beta1.1mdk
rpm -qa | grep imlib
imlib-1.9.14-9mdk
libimlib2_1-loaders-1.1.0-3mdk
libimlib2_1-filters-1.1.0-3mdk
libimlib1-1.9.14-9mdk
libimlib2_1-1.1.0-3mdk
Le message quand je tape ./configure
-------------------------------------
[laurent@linux-laurent captive-1.1.5]$ ./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 whether to enable maintainer-specific portions of Makefiles... no
checking for gcc3... no
checking for gcc-3.0... no
checking for gcc... gcc
checking for C compiler default output... 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 ANSI C... none needed
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 strerror in -lcposix... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
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 egrep... 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 recognise dependent libraries... pass_all
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 f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fl32... no
checking for af77... no
checking for fort77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for lf95... no
checking for g95... 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... 32768
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 static flag works... yes
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 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 how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
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++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
appending configuration tag "F77" to libtool
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 dgettext in libc... yes
checking for bind_textdomain_codeset... yes
checking for msgfmt... no
checking for pkg-config... /usr/bin/pkg-config
checking for perl5... /usr/bin/perl5
checking for pod2man... /usr/bin/pod2man
checking for pkg-config... (cached) /usr/bin/pkg-config
checking for GLIB - version >= 2.0.0... 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: Captive requires glib-2.0 library.
[laurent@linux-laurent captive-1.1.5]$
Poste le Wednesday 17 November 2004 20:14:20
Re: Comment savoir compiler
Envoyé par:
P Hoquet
Je vois que tu n'as pas installé le kernel-source qui va avec ton noyau.
Je vois aussi que libglib2.0_0-devel-2.4.6-1mdk n'est pas non plus isntallé. Mais je te l'avais déjà dit dans une autre discussion.
Je vois aussi que libglib2.0_0-devel-2.4.6-1mdk n'est pas non plus isntallé. Mais je te l'avais déjà dit dans une autre discussion.
Poste le Wednesday 17 November 2004 22:13:36
Re: Comment savoir compiler
Envoyé par:
xunil2003
Lorsque j'execute libglib2.0_0-devel-2.4.6-1mdk.i586.rpm, il m'affiche :
Les paquetages suivants ont des signatures non valides:
/home/laurent/Sources/libglib2.0_0-devel-2.4.6-1mdk.i586.rpm: Signature incorrecte ((SHA1) DSA sha1 md5 (GPG) (MISSING KEY) GPG#70771ff3 NOT OK)
Voulez-vous continuer l'installation ?
donc je ne peut pas l'installer, comment fait tu toi dans ce cas là ?
Merci
Les paquetages suivants ont des signatures non valides:
/home/laurent/Sources/libglib2.0_0-devel-2.4.6-1mdk.i586.rpm: Signature incorrecte ((SHA1) DSA sha1 md5 (GPG) (MISSING KEY) GPG#70771ff3 NOT OK)
Voulez-vous continuer l'installation ?
donc je ne peut pas l'installer, comment fait tu toi dans ce cas là ?
Merci
Poste le Wednesday 17 November 2004 23:05:31
Ce forum !
Comment savoir compiler
Posez dans ce forum les questions qui ne trouvent pas place dans les autres...
Sauf mention contraire, les documentations publiées sont sous licence Creative-Commons