aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: trotz howto Probleme beim Kompilieren unter Debian (sarge)  (Read 5156 times)

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
trotz howto Probleme beim Kompilieren unter Debian (sarge)
« on: July 05, 2004, 07:30:39 PM »

Hallo Leute,
ich habe das howto inzwischen zigmal gelesen und hab's etliche Male probiert, jedoch verabschiedet sich make mit folgender Zeile

gcc  -Wall -g -ggdb -fno-inline -D__DEBUG__ -g     -o cas  cas-cas.o cas-functions.o cas-configfile.o cas-graphics.o  -ljpeg -lfreetype -lpng12 -lz -lm -lgd  -lcrypto++
/usr/bin/ld: cannot find -lcrypto++
collect2: ld returned 1 exit status

in meiner /etc/apt/sources.list steht die Zeile
deb http://debian.thermoman.de/ woody libcrypto++


auch habe ich als root folgende Befehle ausgeführt:
apt-get update
apt-get install libcrypto++5.1 libcrypto++-dev

sowie
ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

Ich bin vollkommen ratlos. Was könnte ich übersehen haben?
Vielen Dank für Eure Unterstützung

Gruß
Fränk
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #1 on: July 06, 2004, 11:32:47 AM »

hast du mal
ldconfig
gemacht? das die libs neu geladen werden?

stefanero
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #2 on: July 06, 2004, 06:49:35 PM »

Hallo stefanero,
ja, habe ich gerade auch mal gemacht.

gleiches Resultat.

aus lauter Frust werde ich jetzt sogar mal den Rechner rebooten.

Gruß
Frank


[edit:]
was natürlich auch nichts gebracht hat[/edit]
« Last Edit: July 06, 2004, 06:56:56 PM by Fraenk »
Logged

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #3 on: July 07, 2004, 07:18:27 PM »

Ich bin weiterhin für jeden Kleinsttipp äusserst dankbar.
Logged

Hinnerk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
configure mit --includedir=/usr/include/crypto++
« Reply #4 on: July 07, 2004, 07:25:40 PM »

probier configure mal mit --includedir=/usr/include/crypto++
Logged

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #5 on: July 07, 2004, 08:41:00 PM »

selbes Problem :-(


sonst noch Ideen?


eine hab ich noch.............
Logged

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #6 on: July 07, 2004, 09:04:02 PM »

hat auch nicht geklappt...

ich poste mal ein  strace /usr/bin/gcc  -lcrypto++  
vielleicht fällt Euch da ja was auch :-/


--- SIGCHLD (Child exited) @ 0 (0) ---
exit_group(1)                           = ?
butterblume:~# less bla
butterblume:~# strace /usr/bin/gcc  -lcrypto++  >> bla
execve("/usr/bin/gcc", ["/usr/bin/gcc", "-lcrypto++"], [/* 12 vars */]) = 0
uname({sys="Linux", node="butterblume", ...}) = 0
brk(0)                                  = 0x805db94
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=47986, ...}) = 0
old_mmap(NULL, 47986, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200^\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1243856, ...}) = 0
old_mmap(NULL, 1254020, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40024000
old_mmap(0x4014c000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x127000) = 0x4014c000
old_mmap(0x40154000, 8836, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40154000
close(3)                                = 0
munmap(0x40018000, 47986)               = 0
brk(0)                                  = 0x805db94
brk(0)                                  = 0x805db94
brk(0x807eb94)                          = 0x807eb94
brk(0)                                  = 0x807eb94
brk(0x807f000)                          = 0x807f000
rt_sigaction(SIGINT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {0x8052310, [INT], SA_RESTORER|SA_RESTART, 0x4004d658}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGHUP, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGHUP, {0x8052310, [HUP], SA_RESTORER|SA_RESTART, 0x4004d658}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGTERM, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGTERM, {0x8052310, [TERM], SA_RESTORER|SA_RESTART, 0x4004d658}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGPIPE, {0x8052310, [PIPE], SA_RESTORER|SA_RESTART, 0x4004d658}, {SIG_IGN}, 8) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
lstat64("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
lstat64("/usr/bin", {st_mode=S_IFDIR|0755, st_size=32768, ...}) = 0
lstat64("/usr/bin/gcc", {st_mode=S_IFLNK|0777, st_size=7, ...}) = 0
readlink("/usr/bin/gcc", "gcc-3.3", 4096) = 7
lstat64("/usr/bin/gcc-3.3", {st_mode=S_IFREG|0755, st_size=85164, ...}) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/", X_OK) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/", X_OK) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/specs", R_OK) = 0
open("/usr/lib/gcc-lib/i486-linux/3.3.4/specs", O_RDONLY) = 3
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/specs", {st_mode=S_IFREG|0644, st_size=3927, ...}) = 0
read(3, "*asm:\n%{v:-V} %{Qy:} %{!Qn:-Qy} "..., 3927) = 3927
close(3)                                = 0
access("/usr/lib/gcc-lib/i486-linux/specs", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/", X_OK) = 0
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/collect2", {st_mode=S_IFREG|0755, st_size=85324, ...}) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/collect2", X_OK) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/crt1.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/i486-linux/3.3.4/crt1.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/i486-linux/3.3.4/crt1.o", R_OK) = -1 ENOENT (No such file o
r directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/crt1.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../i486-linux/3.3.4/crt1.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../crt1.o", R_OK) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/crti.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/i486-linux/3.3.4/crti.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/i486-linux/3.3.4/crti.o", R_OK) = -1 ENOENT (No such file o
r directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/crti.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../i486-linux/3.3.4/crti.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../crti.o", R_OK) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/crtbegin.o", R_OK) = 0
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/.", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
stat64("/usr/lib/gcc/i486-linux/3.3.4/.", 0xbffff18c) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/i486-linux/3.3.4/.", 0xbffff15c) = -1 ENOENT (No such file
or directory)
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/.", 0xbffff17c) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../i486-linux/3.3.4/.", 0xbffff17c) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../.", {st_mode=S_IFDIR|0755, st_size=32768, ...}) = 0
stat64("/lib/i486-linux/3.3.4/.", 0xbffff19c) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/i486-linux/3.3.4/.", 0xbffff19c) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/crtend.o", R_OK) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/crtn.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc/i486-linux/3.3.4/crtn.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/i486-linux/3.3.4/crtn.o", R_OK) = -1 ENOENT (No such file o
r directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../../i486-linux/lib/crtn.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../i486-linux/3.3.4/crtn.o", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/gcc-lib/i486-linux/3.3.4/../../../crtn.o", R_OK) = 0
stat64("/usr/lib/gcc-lib/i486-linux/3.3.4/collect2", {st_mode=S_IFREG|0755, st_size=85324, ...}) = 0
access("/usr/lib/gcc-lib/i486-linux/3.3.4/collect2", X_OK) = 0
fork()                                  = 10829
wait4(-1, /usr/bin/ld: cannot find -lcrypto++
collect2: ld returned 1 exit status



Danke für jeden Hinweis
« Last Edit: July 07, 2004, 09:04:20 PM by Fraenk »
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #7 on: July 07, 2004, 09:08:39 PM »

viell. sollst du mal versuchen crypto selbst zu kompilieren ..

gruss

stroesen

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #8 on: July 07, 2004, 10:00:56 PM »

mach doch mal 'ls /usr/lib/libcrypto*'
Logged
"I'd never join a club that accepts people like me as a member" (Groucho Marx)

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #9 on: July 08, 2004, 10:35:19 AM »

butterblume:~# ls -ltra /usr/lib/libcrypto*
-rw-r--r--    1 root     root          847 Apr  5 18:34 /usr/lib/libcrypto++5.1.la
-rw-r--r--    1 root     root      9529404 Apr  5 18:34 /usr/lib/libcrypto++5.1.so.0.0.0
-rw-r--r--    1 root     root     30774854 Apr  5 18:34 /usr/lib/libcrypto++5.1.a
-rw-r--r--    1 root     root      1045608 May 24 17:49 /usr/lib/libcrypto.so.0.9.7
-rw-r--r--    1 root     root      1954846 May 24 17:49 /usr/lib/libcrypto_pic.a
-rw-r--r--    1 root     root      1735308 May 24 17:49 /usr/lib/libcrypto.a
lrwxrwxrwx    1 root     root           18 Jul  4 04:44 /usr/lib/libcrypto.so -> libcrypto.so.0.9.7
lrwxrwxrwx    1 root     root           23 Jul  5 18:57 /usr/lib/libcrypto++5.1.so.0 -> libcrypto++5.1.so.0.0.0
lrwxrwxrwx    1 root     root           23 Jul  5 18:57 /usr/lib/libcrypto++5.1.so -> libcrypto++5.1.so.0.0.0
butterblume:~#
Logged

stroesen

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 10
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #10 on: July 08, 2004, 04:31:47 PM »

die Option '-lcrypto++' lässt den Linker nach libcrypto++.so suchen, und
die gibt's bei Dir nicht ("/usr/bin/ld: cannot find -lcrypto++"); mit '-lcrypto++5.1' dürfte er fündig werden; alternativ kannst einen neuen
Verweis libcrypto++.so -> libcrypto++5.1.so.0.0.0 erzeugen

falls alle Stricke reissen: '-lcrypto' wie im Makefile vorgesehen
Logged
"I'd never join a club that accepts people like me as a member" (Groucho Marx)

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #11 on: July 08, 2004, 06:43:15 PM »

habe jetzt einen solchen link angelegt, leider bricht der make prozess jetzt mit folgender Meldung ab.

gcc  -Wall -g -ggdb -fno-inline -D__DEBUG__ -g     -o cas  cas-cas.o cas-functions.o cas-configfile.o cas-graphics.o  -ljpeg -lfreetype -lpng12 -lz -lm -lgd  -lcrypto++
/usr/lib/gcc-lib/i486-linux/3.3.4/../../../libcrypto++.so: undefined reference to `pthread_getspecific'
/usr/lib/gcc-lib/i486-linux/3.3.4/../../../libcrypto++.so: undefined reference to `pthread_key_delete'
/usr/lib/gcc-lib/i486-linux/3.3.4/../../../libcrypto++.so: undefined reference to `pthread_key_create'
/usr/lib/gcc-lib/i486-linux/3.3.4/../../../libcrypto++.so: undefined reference to `pthread_setspecific'
collect2: ld returned 1 exit status
make[2]: *** [cas] Fehler 1
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #12 on: July 08, 2004, 06:46:48 PM »

lösche/uninstalliere alles an libcrypto++ paketen, schaue dir unseres howto an und compiliere es selbst.

gruss

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #13 on: July 08, 2004, 07:32:30 PM »

ja, da komme ich wohl nicht drum herum, fürchte ich :-/

Danke für Eure Unterstützung.
Gruß
Fränk


ansonsten: falls noch jemand eine Idee haben sollte, ruhig heraus damit, heute komm ich ohnehin nicht mehr dazu
Logged

Fraenk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 11
Re: trotz howto Probleme beim Kompilieren unter Debian (sarge)
« Reply #14 on: July 09, 2004, 03:03:22 AM »

schließlich und endlich hat es ausschießlich mit der Hasty Installation funktioniert.
Danke für Eure Hilfe!

Fränk
Logged