Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
2490 connectés 

  FORUM HardWare.fr
  Linux et OS Alternatifs
  Logiciels

  [Debian] KDE-devel pété ?

 
 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

[Debian] KDE-devel pété ?

n°273408
Goon
Posté le 06-06-2003 à 05:19:43  profilanswer
 

Voilà je suis sous Debian Sid et pour compiler un soft (Kile), j'ai besoin des paquets de développement de KDE (les headers si j'ai bien compris). Or apt-get install kde-devel ne marche pas et me dis que j'ai des paquets cassés. Après recherche, il s'avère que c'est parce que libgdbmg1-dev dépend strictement de libgdbmg1 1.7.3-27.1 mais que c'est la 1.7.3-28 qui est installée. Comment je peux m'en sortir ?

mood
Publicité
Posté le 06-06-2003 à 05:19:43  profilanswer
 

n°273525
911GT3
en roue libre
Posté le 06-06-2003 à 11:33:41  profilanswer
 

le plus rapide consiste peut-être à récuperer l'ancienne version de libgdbmg1 sur les ftp Debian et à downgrader via un dpkg -i ... en espérant que ça ne pose pas d'autre problème de dépendance.

n°273536
Goon
Posté le 06-06-2003 à 12:05:29  profilanswer
 

Bon j'ay suis finalement arrivé, en fait il avait été remplacé par un autre paquet. Par contre quand je fais ./configure --prefix=/usr/ avec Kile, voilà ce que ça me donne
 
 

Code :
  1. goon@MrJean:~/kile-1.5.2a$ ./configure --prefix=/usr/
  2. checking build system type... i686-pc-linux-gnu
  3. checking host system type... i686-pc-linux-gnu
  4. checking target system type... i686-pc-linux-gnu
  5. checking for a BSD-compatible install... /usr/bin/install -c
  6. checking for -p flag to install... yes
  7. checking whether build environment is sane... yes
  8. checking for gawk... gawk
  9. checking whether make sets $(MAKE)... yes
  10. checking for style of include used by make... GNU
  11. checking for gcc... gcc
  12. checking for C compiler default output... a.out
  13. checking whether the C compiler works... yes
  14. checking whether we are cross compiling... no
  15. checking for suffix of executables...
  16. checking for suffix of object files... o
  17. checking whether we are using the GNU C compiler... yes
  18. checking whether gcc accepts -g... yes
  19. checking for gcc option to accept ANSI C... none needed
  20. checking dependency style of gcc... gcc
  21. checking how to run the C preprocessor... gcc -E
  22. checking for g++... g++
  23. checking whether we are using the GNU C++ compiler... yes
  24. checking whether g++ accepts -g... yes
  25. checking dependency style of g++... gcc3
  26. checking whether g++ supports -Wmissing-format-attribute... yes
  27. checking whether g++ supports -Wundef... yes
  28. checking whether g++ supports -Wno-long-long... yes
  29. checking whether g++ supports -Wnon-virtual-dtor... yes
  30. checking whether g++ supports -fno-exceptions... yes
  31. checking whether g++ supports -fno-check-new... yes
  32. checking whether g++ supports -fno-common... yes
  33. checking whether g++ supports -fexceptions... yes
  34. checking how to run the C++ preprocessor... g++ -E
  35. checking whether g++ supports -O0... yes
  36. not using lib directory suffix
  37. checking for ld used by GCC... /usr/bin/ld
  38. checking if the linker (/usr/bin/ld) is GNU ld... yes
  39. checking for /usr/bin/ld option to reload object files... -r
  40. checking for BSD-compatible nm... /usr/bin/nm -B
  41. checking for a sed that does not truncate output...
  42. checking whether ln -s works... yes
  43. checking how to recognise dependant libraries... pass_all
  44. checking for egrep... grep -E
  45. checking for ANSI C header files... no
  46. checking for sys/types.h... no
  47. checking for sys/stat.h... no
  48. checking for stdlib.h... no
  49. checking for string.h... no
  50. checking for memory.h... no
  51. checking for strings.h... no
  52. checking for inttypes.h... no
  53. checking for stdint.h... no
  54. checking for unistd.h... no
  55. checking dlfcn.h usability... no
  56. checking dlfcn.h presence... yes
  57. configure: WARNING: dlfcn.h: present but cannot be compiled
  58. configure: WARNING: dlfcn.h: check for missing prerequisite headers?
  59. configure: WARNING: dlfcn.h: proceeding with the preprocessor's result
  60. configure: WARNING:     ## ------------------------------------ ##
  61. configure: WARNING:     ## Report this to bug-autoconf@gnu.org. ##
  62. configure: WARNING:     ## ------------------------------------ ##
  63. checking for dlfcn.h... yes
  64. checking the maximum length of command line arguments... 32768
  65. checking command to parse /usr/bin/nm -B output from gcc object... failed
  66. checking for objdir... .libs
  67. checking for ranlib... ranlib
  68. checking for strip... strip
  69. checking if gcc static flag  works... no
  70. checking if gcc supports -fno-rtti -fno-exceptions... no
  71. checking for gcc option to produce PIC... -fPIC
  72. checking if gcc PIC flag -fPIC works... no
  73. checking if gcc supports -c -o file.o... no
  74. checking if we can lock with hard links... yes
  75. checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
  76. checking whether -lc should be explicitly linked in... yes
  77. checking how to hardcode library paths into programs... immediate
  78. checking whether stripping libraries is possible... yes
  79. checking dynamic linker characteristics... GNU/Linux ld.so
  80. checking if libtool supports shared libraries... yes
  81. checking whether to build shared libraries... yes
  82. checking whether to build static libraries... no
  83. configure: creating libtool
  84. appending configuration tag "CXX" to libtool
  85. checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
  86. checking for g++ option to produce PIC... -fPIC
  87. checking if g++ PIC flag -fPIC works... yes
  88. checking if g++ supports -c -o file.o... yes
  89. checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
  90. checking whether -lc should be explicitly linked in... yes
  91. checking how to hardcode library paths into programs... immediate
  92. checking whether stripping libraries is possible... yes
  93. checking dynamic linker characteristics... GNU/Linux ld.so
  94. appending configuration tag "GCJ" to libtool
  95. checking if gcj supports -fno-rtti -fno-exceptions... (cached) no
  96. checking for gcj option to produce PIC... -fPIC
  97. checking if gcj PIC flag -fPIC works... no
  98. checking if gcj supports -c -o file.o... no
  99. checking whether the gcj linker (/usr/bin/ld) supports shared libraries... yes
  100. checking whether -lc should be explicitly linked in... yes
  101. checking how to hardcode library paths into programs... immediate
  102. checking whether stripping libraries is possible... yes
  103. checking dynamic linker characteristics... GNU/Linux ld.so
  104. checking for msgfmt... /usr/bin/msgfmt
  105. checking for gmsgfmt... /usr/bin/msgfmt
  106. checking for xgettext... /usr/bin/xgettext
  107. checking for strlcat... no
  108. checking if strlcat needs custom prototype... yes - in libkdefakes
  109. checking for strlcpy... no
  110. checking if strlcpy needs custom prototype... yes - in libkdefakes
  111. checking for main in -lutil... no
  112. checking for main in -lcompat... no
  113. checking for crypt in -lcrypt... no
  114. checking for crypt in -lc... no
  115. configure: WARNING: you have no crypt in either libcrypt or libc.
  116. You should install libcrypt from another source or configure with PAM
  117. support
  118. checking for socklen_t... socklen_t
  119. checking for dnet_ntoa in -ldnet... no
  120. checking for dnet_ntoa in -ldnet_stub... no
  121. checking for inet_ntoa... no
  122. checking for inet_ntoa in -lnsl... no
  123. checking for connect... no
  124. checking for connect in -lsocket... no
  125. checking for remove... no
  126. checking for remove in -lposix... no
  127. checking for shmat... no
  128. checking for shmat in -lipc... no
  129. checking crt_externs.h usability... no
  130. checking crt_externs.h presence... no
  131. checking for crt_externs.h... no
  132. checking for _NSGetEnviron... no
  133. checking for sys/types.h... (cached) no
  134. checking for stdint.h... (cached) no
  135. checking for poll in -lpoll... no
  136. checking CoreAudio/CoreAudio.h usability... no
  137. checking CoreAudio/CoreAudio.h presence... no
  138. checking for CoreAudio/CoreAudio.h... no
  139. checking if res_init needs -lresolv... no
  140. checking if res_init is available... no
  141. checking for killpg in -lucb... no
  142. checking for int... no
  143. checking size of int... 0
  144. checking for long... no
  145. checking size of long... 0
  146. checking for char *... no
  147. checking size of char *... 0
  148. checking for dlopen in -ldl... no
  149. checking for shl_unload in -ldld... no
  150. checking for size_t... no
  151. checking size of size_t... 0
  152. checking for unsigned long... no
  153. checking size of unsigned long... 0
  154. checking sizeof size_t == sizeof unsigned long... no
  155. configure: error:
  156.        Apparently on your system our assumption sizeof size_t == sizeof unsigned long
  157.        does not apply. Please mail kde-devel@kde.org with a description of your system!

 
 
Qu'est-ce que j'ai (encore  :sarcastic: ) oublié ?


Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Linux et OS Alternatifs
  Logiciels

  [Debian] KDE-devel pété ?

 

Sujets relatifs
[Debian] pb de DMA [Résolu]Antivirus Panda sous Debian
lecteur de dvd sous debianMon menu KDE a était vidé après installation d'un logiciel....
ss Mdk : service nom_service stop|start , sous debian ? c quoidebian et dell C810 pb
[Linux Debian]Comment changer le nom de la machine?[debian] pb avec ./configure (kdestopsharing)
[Debian] Quelques problèmes après MAJ de kdeapt-get : Segmentation Fault Debian Power Users NEEDED !!!!
Plus de sujets relatifs à : [Debian] KDE-devel pété ?

Forum MesDiscussions.Net, Version 2010.2
(c) 2000-2011 Doctissimo
Page générée en 0.084 secondes

Copyright © 1997-2025 Groupe LDLC (Signaler un contenu illicite / Données personnelles)