[Python-de] Python Test schlägt fehl in configure Skript

[Malte Gell]

Am 24.01.2013 08:44, schrieb Rüdiger Ranft:

> Versuche zuerst, ob das linken gegen libm überhaupt funktioniert:

Ja, das hat funktioniert.

> cat <<EOF > bar.c
> #include <Python.h>
> 
> int main()
> {
>     Py_Initialize();
>     return 0;
> }
> EOF
> gcc -I/usr/include/python2.7 bar.c -lpython2.7

Oha! Das hat nicht funktioniert und hat mit einigen Fehlermedlungen
abgebrochen:

/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
warning: libpthread.so.0, needed by
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so,
not found (try using -rpath or -rpath-link)
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
warning: libdl.so.2, needed by
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so,
not found (try using -rpath or -rpath-link)
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
warning: libutil.so.1, needed by
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so,
not found (try using -rpath or -rpath-link)
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../x86_64-suse-linux/bin/ld:
warning: libm.so.6, needed by
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so,
not found (try using -rpath or -rpath-link)
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `floor at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `hypot at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `sem_post at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `dlopen at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `dlerror at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `forkpty at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `sem_wait at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `sincos at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `openpty at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `fmod at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `atan2 at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `pthread_create at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `sem_destroy at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `exp at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `sem_init at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `log at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `dlsym at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `sem_trywait at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `pthread_detach at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `pthread_attr_setstacksize at GLIBC_2.2.5'
/usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libpython2.7.so:
undefined reference to `pow at GLIBC_2.2.5'

Da fehlen wohl einige Libs auf meinem System wie es aussieht? Ich werde
jetzt mal prüfen, ob diese Libs bei mir fehlen, die da nicht gefunden
werden.

Gruß
Malte