Conversation
precedente ou
suivante
Page: 1 sur 2
Compiler
Envoyé par:
xunil2003
Salut
Je voulais installé xmule et quand je tape ./configure il m'affiche le message ci-dessous.
j'ai du réinstaller plusieur fois ma mdk 10.1 causé par des conflit entre fichier version et les progs qui ne demare plus !
Je pense qu'il y a un probleme de copilation mais le quel et comment le résoudre, a moin que je me trompe; je n'ai pas assez d'expérience dans linux pour savoir comment faire, mais je me débrouille.
que veut il dire avec config.log et C++ Compiler ?
Que faut il lui installer comme Packetage et comment voir le dépendence dot il aura besoin ?
Que faut il faire en deux mots ?
[laurent@linux-laurent captive-1.1.5]$ rpm -qa | grep gcc
libgcc1-3.4.1-3mdk
gcc-3.4.1-3mdk
gcc-cpp-3.4.1-3mdk
gcc2.96-cpp-2.96-0.83mdk
[laurent@linux-laurent captive-1.1.5]$
[laurent@linux-laurent xmule-1.7.4a]$ ./configure
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 for C++ compiler default output file name... configure: error: C++ compiler cannot create executables
See `config.log' for more details.
Je voulais installé xmule et quand je tape ./configure il m'affiche le message ci-dessous.
j'ai du réinstaller plusieur fois ma mdk 10.1 causé par des conflit entre fichier version et les progs qui ne demare plus !
Je pense qu'il y a un probleme de copilation mais le quel et comment le résoudre, a moin que je me trompe; je n'ai pas assez d'expérience dans linux pour savoir comment faire, mais je me débrouille.
que veut il dire avec config.log et C++ Compiler ?
Que faut il lui installer comme Packetage et comment voir le dépendence dot il aura besoin ?
Que faut il faire en deux mots ?
[laurent@linux-laurent captive-1.1.5]$ rpm -qa | grep gcc
libgcc1-3.4.1-3mdk
gcc-3.4.1-3mdk
gcc-cpp-3.4.1-3mdk
gcc2.96-cpp-2.96-0.83mdk
[laurent@linux-laurent captive-1.1.5]$
[laurent@linux-laurent xmule-1.7.4a]$ ./configure
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 for C++ compiler default output file name... configure: error: C++ compiler cannot create executables
See `config.log' for more details.
Poste le Sunday 7 November 2004 20:20:25
Re: Compiler
Envoyé par:
Aciid_wAshOr
Bonsoir,
Essaye en installant gcc-c++
Essaye en installant gcc-c++
Poste le Sunday 7 November 2004 20:49:38
Re: Compiler
Envoyé par:
xunil2003
sur pmfind.net, j'ai tapé GCC-C++ il
ma afficher la liste et j'ai telechargé pour ma mandrake 10.1 ---> "gcc-c++-3.4.1-4mdk.i586.rpm"
et lorsque je l'install il m'affiche :
Certains paquetages demandés ne peuvent pas être installés :
gcc-c++-3.4.1-4mdk.i586 (car gcc[== 3.4.1-4mdk] est non satisfait)
Êtes-vous d'accord ?
alors, j'annule l'istallation etant donné que je ne trouve pas gcc-c++-3.4.1-3mdk.i586.rpm car quand je tape "rpm -qa | grep gcc" il affiche que des versions 3.4.1-3mdk.
libgcc1-3.4.1-3mdk
gcc-3.4.1-3mdk
gcc-cpp-3.4.1-3mdk
gcc2.96-cpp-2.96-0.83mdk
[laurent@linux-laurent captive-1.1.5]$
Ou faut il installer que des 3.4.1-4mdk ?
Donc comment faire ?
Merci davance, salutations
ma afficher la liste et j'ai telechargé pour ma mandrake 10.1 ---> "gcc-c++-3.4.1-4mdk.i586.rpm"
et lorsque je l'install il m'affiche :
Certains paquetages demandés ne peuvent pas être installés :
gcc-c++-3.4.1-4mdk.i586 (car gcc[== 3.4.1-4mdk] est non satisfait)
Êtes-vous d'accord ?
alors, j'annule l'istallation etant donné que je ne trouve pas gcc-c++-3.4.1-3mdk.i586.rpm car quand je tape "rpm -qa | grep gcc" il affiche que des versions 3.4.1-3mdk.
libgcc1-3.4.1-3mdk
gcc-3.4.1-3mdk
gcc-cpp-3.4.1-3mdk
gcc2.96-cpp-2.96-0.83mdk
[laurent@linux-laurent captive-1.1.5]$
Ou faut il installer que des 3.4.1-4mdk ?
Donc comment faire ?
Merci davance, salutations
Poste le Sunday 7 November 2004 21:31:12
Re: Compiler
Envoyé par:
Aciid_wAshOr
A priori, je dirai qu'il faut toute les meme version ex:
sous Fedora Core 2, j'ai
[tom@localhost tom]$ rpm -qa | grep gcc
gcc-3.3.3-7
gcc-objc-3.3.3-7
libgcc-3.3.3-7
gcc-c++-3.3.3-7
gcc-gnat-3.3.3-7
gcc-java-3.3.3-7
gcc-g77-3.3.3-7
[tom@localhost tom]$
Il n'existe pas un service comme apt ou yum sous Mandrake?
sous Fedora Core 2, j'ai
[tom@localhost tom]$ rpm -qa | grep gcc
gcc-3.3.3-7
gcc-objc-3.3.3-7
libgcc-3.3.3-7
gcc-c++-3.3.3-7
gcc-gnat-3.3.3-7
gcc-java-3.3.3-7
gcc-g77-3.3.3-7
[tom@localhost tom]$
Il n'existe pas un service comme apt ou yum sous Mandrake?
Poste le Sunday 7 November 2004 21:39:45
Re: Compiler
Envoyé par:
xunil2003
Ok , mais lorsque j'installe gcc-c++, il m'affiche :
Certains paquetages demandés ne peuvent pas être installés :
gcc-c++-3.4.1-4mdk.i586 (car gcc[== 3.4.1-4mdk] est non satisfait)
Êtes-vous d'accord ?
alors Comment faire ?????????
Merci
Certains paquetages demandés ne peuvent pas être installés :
gcc-c++-3.4.1-4mdk.i586 (car gcc[== 3.4.1-4mdk] est non satisfait)
Êtes-vous d'accord ?
alors Comment faire ?????????
Merci
Poste le Sunday 7 November 2004 22:22:46
Re: Compiler
Envoyé par:
xunil2003
j'ai réussi a trouver "gcc-c++-3.4.1-3mdk.i586.rpm" et a l'installer sans probleme et lorsque je tape ./configure il m'affiche ci-dessous :
Que veut dire "configure: error: Captive requires glib-2.0 library."
Que reste t'il a faire ?
[root@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... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... cs
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.
[root@linux-laurent captive-1.1.5]#
Que veut dire "configure: error: Captive requires glib-2.0 library."
Que reste t'il a faire ?
[root@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... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... cs
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.
[root@linux-laurent captive-1.1.5]#
Poste le Sunday 7 November 2004 23:04:26
Re: Compiler
Envoyé par:
Aciid_wAshOr
Meme chose que pour gcc, tu installes une version de glib qui est supérieure a 2.0.0
Poste le Monday 8 November 2004 05:20:17
Re: Compiler
Envoyé par:
P Hoquet
Pour glib s'il manque quelque chose utilise les rpm fournis avec la distribution.
As-tu installé les packages de développement.
L'erreur dans le configure peut indiquer qu'il manque les packages de développement alors que la bibliothèque est bien présente.
As-tu installé les packages de développement.
L'erreur dans le configure peut indiquer qu'il manque les packages de développement alors que la bibliothèque est bien présente.
Poste le Monday 8 November 2004 09:33:57
Re: Compiler
Envoyé par:
xunil2003
salut,
comment s'apercevoir si les packages de développement son bien installé, y a t'il une commande pour me le dire ?
Question es-ce que glib doit etre en version 3.4.1-3mdk tout comme gcc (identique en version)
Merci
comment s'apercevoir si les packages de développement son bien installé, y a t'il une commande pour me le dire ?
Question es-ce que glib doit etre en version 3.4.1-3mdk tout comme gcc (identique en version)
Merci
Poste le Monday 8 November 2004 09:59:45
Re: Compiler
Envoyé par:
P Hoquet
La version de glib n'a rien à voir avec la version de gcc.
Les package de développement ont le même nom que le package principal mais avec le suffixe -devel.
Pour trouver le nom des packages tu peux par exemple afficher la source main et faire une recherche dans la page basée sur glib.
Les package de développement ont le même nom que le package principal mais avec le suffixe -devel.
Pour trouver le nom des packages tu peux par exemple afficher la source main et faire une recherche dans la page basée sur glib.
Poste le Monday 8 November 2004 10:16:11
Re: Compiler
Envoyé par:
xunil2003
Comment afficher la source main et faire la recherche de page basée sur glib ?
j'ai l'impression qu'il y a plusieur version de glib, comment faire ?
es-ce comme sa la recherche de page basée sur glib et dit moi ce que tu comprend :
[laurent@linux-laurent win_c3]$ 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
taglib-1.2-1mdk
glibc-devel-2.3.3-20mdk
[laurent@linux-laurent win_c3]$
Merci
j'ai l'impression qu'il y a plusieur version de glib, comment faire ?
es-ce comme sa la recherche de page basée sur glib et dit moi ce que tu comprend :
[laurent@linux-laurent win_c3]$ 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
taglib-1.2-1mdk
glibc-devel-2.3.3-20mdk
[laurent@linux-laurent win_c3]$
Merci
Poste le Monday 8 November 2004 10:22:51
Re: Compiler
Envoyé par:
xunil2003
ok, mais quel version mdk de libglib1.2-devel et libglib2.0_0-devel, car rien est satidfait
Es-ce libglib1.2-devel-1mdk et libglib2.0_0-devel-2.4.6-1mdk qu'il me faut ou je me trompe car j'ai téléchargé libglib2.0_0-devel-2.4.6-1mdk.i586.rpm et il me repond que c'est non satisfait et idem pour l'autre je ne sais quel version il lui faut, comment le savoir ?
[laurent@linux-laurent win_c3]$ rpm -qa | grep glib
libdbus-glib-1_0-0.22-1mdk
libtaglib0-1.22.4.6-1mdk
libglib2.0_0-2.4.6-1mdk
libglib1.2-1.2.10-13mdk
glibc-2.3.3-20mdk
taglib-1.2-1mdk
glibc-devel-2.3.3-20mdk
[laurent@linux-laurent win_c3]$
Merci
Es-ce libglib1.2-devel-1mdk et libglib2.0_0-devel-2.4.6-1mdk qu'il me faut ou je me trompe car j'ai téléchargé libglib2.0_0-devel-2.4.6-1mdk.i586.rpm et il me repond que c'est non satisfait et idem pour l'autre je ne sais quel version il lui faut, comment le savoir ?
[laurent@linux-laurent win_c3]$ rpm -qa | grep glib
libdbus-glib-1_0-0.22-1mdk
libtaglib0-1.22.4.6-1mdk
libglib2.0_0-2.4.6-1mdk
libglib1.2-1.2.10-13mdk
glibc-2.3.3-20mdk
taglib-1.2-1mdk
glibc-devel-2.3.3-20mdk
[laurent@linux-laurent win_c3]$
Merci
Poste le Monday 8 November 2004 11:04:13
Re: Compiler
Envoyé par:
xunil2003
Pour libglib1.2-devel-1.2.10-13mdk je les téléchargé et installé sans problême, Mais pour glib il y a toujour probleme, regarde ci dessous et dit moi ce que tu comprend. Que faire ?
il dit "GLIB is incorrectly installed" alors comment l'installer correctement ?
Merci d'avance, salutation
[laurent@linux-laurent captive-1.1.5]$ 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
libglib1.2-devel-1.2.10-13mdk
glibc-2.3.3-20mdk
taglib-1.2-1mdk
glibc-devel-2.3.3-20mdk
[laurent@linux-laurent captive-1.1.5]$
[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... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... cs
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]$
il dit "GLIB is incorrectly installed" alors comment l'installer correctement ?
Merci d'avance, salutation
[laurent@linux-laurent captive-1.1.5]$ 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
libglib1.2-devel-1.2.10-13mdk
glibc-2.3.3-20mdk
taglib-1.2-1mdk
glibc-devel-2.3.3-20mdk
[laurent@linux-laurent captive-1.1.5]$
[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... /usr/bin/msgfmt
checking for dcgettext... yes
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for catalogs to be installed... cs
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 Thursday 11 November 2004 15:40:24
Re: Compiler
Envoyé par:
xunil2003
Salut,
J'ai téléchargé libglib2.0_0-devel-2.4.6-1mdk.i589.rpm [rpm.pbone.net]
Mais a l'installation de ce rpm que tu me dit à installer, m'indique des messages d'erreur , explique moi comment faire ?
Comment lui satisfaire glib-gettextize[>= 2.4.6] pour installer libglib2.0_0-devel-2.4.6-1mdk.i586 ?
Certains paquetages demandés ne peuvent pas être installés :
libglib2.0_0-devel-2.4.6-1mdk.i586 (car glib-gettextize[>= 2.4.6] est non satisfait)
Êtes-vous d'accord ? (Répondu non, attend ta réponse)
Merci d'avance, salutation.
J'ai téléchargé libglib2.0_0-devel-2.4.6-1mdk.i589.rpm [rpm.pbone.net]
Mais a l'installation de ce rpm que tu me dit à installer, m'indique des messages d'erreur , explique moi comment faire ?
Comment lui satisfaire glib-gettextize[>= 2.4.6] pour installer libglib2.0_0-devel-2.4.6-1mdk.i586 ?
Certains paquetages demandés ne peuvent pas être installés :
libglib2.0_0-devel-2.4.6-1mdk.i586 (car glib-gettextize[>= 2.4.6] est non satisfait)
Êtes-vous d'accord ? (Répondu non, attend ta réponse)
Merci d'avance, salutation.
Poste le Sunday 14 November 2004 15:26:21
Re: Compiler
Envoyé par:
Dorian
Citation
xunil2003
Salut,
Comment lui satisfaire glib-gettextize[>=
2.4.6] pour installer
libglib2.0_0-devel-2.4.6-1mdk.i586 ?
Certains paquetages demandés ne peuvent pas être
installés :
libglib2.0_0-devel-2.4.6-1mdk.i586 (car
glib-gettextize[>= 2.4.6] est non satisfait)
Merci d'avance, salutation.
Ben tu fais urpmi glib-gettextize ou tu télécharges une version 2.4.6 ou supérieure de glib-gettextize. La prochaine fois que tu installes ta Mandrake, n'oublie pas d'intégrer les outils de développement, ça t'évitera tous ces problèmes.
Poste le Sunday 14 November 2004 15:47:56
Page: 1 sur 2
Ce forum !
Compiler
Posez dans ce forum les questions qui ne trouvent pas place dans les autres...
Nouveau sujet sur ce forum
Sauf mention contraire, les documentations publiées sont sous licence Creative-Commons