ubuntuusers.de

problem kompilieren siproxd

Status: Ungelöst | Ubuntu-Version: Ubuntu 10.04 (Lucid Lynx)
Antworten |

menzbua

Anmeldungsdatum:
2. April 2008

Beiträge: 32

hallo zusammen,

ich habe ein problem beim compilieren von siproxd. ich brauche die aktuelle version weil ich einen tcp sip proxy brauche. tcp funktioniert mit der mitgelieferten version noch nicht. wenn ich make mache bekomme ich folgende fehler:

if gcc -DHAVE_CONFIG_H -I. -I. -I..    -Wall -D_GNU_SOURCE  -DBUILDSTR="\"`cat .buildno`\"" -g -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -MT plugins.o -MD -MP -MF ".deps/plugins.Tpo" -c -o plugins.o plugins.c; \
        then mv -f ".deps/plugins.Tpo" ".deps/plugins.Po"; else rm -f ".deps/plugins.Tpo"; exit 1; fi
/bin/bash ../libtool --tag=CC --mode=link gcc -Wall -D_GNU_SOURCE  -DBUILDSTR="\"`cat .buildno`\"" -g -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS   -o siproxd -export-dynamic siproxd.o proxy.o register.o sock.o utils.o sip_utils.o sip_layer.o log.o readconf.o rtpproxy.o rtpproxy_relay.o accessctl.o route_processing.o security.o auth.o fwapi.o resolve.o dejitter.o plugins.o  -dlopen plugin_demo.la -dlopen plugin_shortdial.la -dlopen plugin_logcall.la -dlopen plugin_defaulttarget.la -dlopen plugin_fix_bogus_via.la -dlopen plugin_stun.la -lresolv -lresolv -losipparser2 -losip2   -lltdl 
rm -f .libs/siproxd.nm .libs/siproxd.nmS .libs/siproxd.nmT
creating .libs/siproxdS.c
(cd .libs && gcc  -g -O2 -c -fno-builtin "siproxdS.c")
rm -f .libs/siproxdS.c .libs/siproxd.nm .libs/siproxd.nmS .libs/siproxd.nmT
gcc -Wall -D_GNU_SOURCE -DBUILDSTR=\"5680\" -g -O2 -pthread -D_POSIX_THREAD_SAFE_FUNCTIONS -o siproxd siproxd.o proxy.o register.o sock.o utils.o sip_utils.o sip_layer.o log.o readconf.o rtpproxy.o rtpproxy_relay.o accessctl.o route_processing.o security.o auth.o fwapi.o resolve.o dejitter.o plugins.o .libs/siproxdS.o -Wl,--export-dynamic  -lresolv /usr/lib/libosip2.so -lnsl /usr/lib/libosipparser2.so /usr/lib/libltdl.so -ldl  
plugins.o: In function `load_plugins':
/home/user/Downloads/siproxd-0.8.1dev/src/plugins.c:65: undefined reference to `lt__PROGRAM__LTX_preloaded_symbols'
collect2: ld returned 1 exit status
rm -f .libs/siproxdS.o
make[2]: *** [siproxd] Error 1
make[2]: Leaving directory `/home/user/Downloads/siproxd-0.8.1dev/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user/Downloads/siproxd-0.8.1dev'
make: *** [all] Error 2

kann mir hier jemand helfen?

vielen dank

gruß manuel

chrkl

Anmeldungsdatum:
25. März 2009

Beiträge: 42

Wohnort: Paderborn

Das sieht nach einem Problem mit libtool aus. Du solltest mal überprüfen, ob libtool korrekt installiert ist und vielleicht versuchen den libtool Pfad beim "configure" explizit anzugehen.

Viele Grüße, chrkl

menzbua

(Themenstarter)

Anmeldungsdatum:
2. April 2008

Beiträge: 32

wie kann ich das prüfen ob das libtool korrekt installiert ist? wie kann ich den pfad im configure angeben?

vielen dank

gruß manuel

chrkl

Anmeldungsdatum:
25. März 2009

Beiträge: 42

Wohnort: Paderborn

Mit "dpkg -l" kannst du dir alle installierten Pakete anzeigen lassen. Schau einfach mal, ob libtool dabei ist (z.B. "dbkg -l | grep libtool"). Wie die configure Parameter aussehen hängt ganz von deiner Anwendung ab. Sipoxd habe ich selber noch nicht benutzt, von daher mach einfach mal ein "./configure --help". Hoffe das hilft!

Gruß, chrkl

menzbua

(Themenstarter)

Anmeldungsdatum:
2. April 2008

Beiträge: 32

also ich hab das libtool installiert:

dpkg -l |grep libtool
ii  libtool                              2.2.6b-2ubuntu1                                 Generic library support script

jetzt weiß ich allerdings nicht was ich beim configure machen soll / kann:

./configure --help
`configure' configures this package to adapt to many kinds of systems.

Usage: ./configure [OPTION]... [VAR=VALUE]...

To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE.  See below for descriptions of some of the useful variables.

Defaults for the options are specified in brackets.

Configuration:
  -h, --help              display this help and exit
      --help=short        display options specific to this package
      --help=recursive    display the short help of all the included packages
  -V, --version           display version information and exit
  -q, --quiet, --silent   do not print `checking...' messages
      --cache-file=FILE   cache test results in FILE [disabled]
  -C, --config-cache      alias for `--cache-file=config.cache'
  -n, --no-create         do not create output files
      --srcdir=DIR        find the sources in DIR [configure dir or `..']

Installation directories:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [PREFIX]

By default, `make install' will install all the files in
`/usr/local/bin', `/usr/local/lib' etc.  You can specify
an installation prefix other than `/usr/local' using `--prefix',
for instance `--prefix=$HOME'.

For better control, use the options below.

Fine tuning of the installation directories:
  --bindir=DIR           user executables [EPREFIX/bin]
  --sbindir=DIR          system admin executables [EPREFIX/sbin]
  --libexecdir=DIR       program executables [EPREFIX/libexec]
  --datadir=DIR          read-only architecture-independent data [PREFIX/share]
  --sysconfdir=DIR       read-only single-machine data [PREFIX/etc]
  --sharedstatedir=DIR   modifiable architecture-independent data [PREFIX/com]
  --localstatedir=DIR    modifiable single-machine data [PREFIX/var]
  --libdir=DIR           object code libraries [EPREFIX/lib]
  --includedir=DIR       C header files [PREFIX/include]
  --oldincludedir=DIR    C header files for non-gcc [/usr/include]
  --infodir=DIR          info documentation [PREFIX/info]
  --mandir=DIR           man documentation [PREFIX/man]

Program names:
  --program-prefix=PREFIX            prepend PREFIX to installed program names
  --program-suffix=SUFFIX            append SUFFIX to installed program names
  --program-transform-name=PROGRAM   run sed PROGRAM on installed program names

System types:
  --build=BUILD     configure for building on BUILD [guessed]
  --host=HOST       cross-compile to build programs to run on HOST [BUILD]
  --target=TARGET   configure for building compilers for TARGET [HOST]

Optional Features:
  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  --disable-dependency-tracking  speeds up one-time build
  --enable-dependency-tracking   do not reject slow dependency extractors
  --enable-shared[=PKGS]
                          build shared libraries [default=yes]
  --enable-static[=PKGS]
                          build static libraries [default=yes]
  --enable-fast-install[=PKGS]
                          optimize for fast installation [default=yes]
  --disable-libtool-lock  avoid locking (might break parallel builds)
  --disable-doc               build pdf/html doc (default=enabled)
  --enable-static-libosip2    link statically against libosip2
  --enable-dmalloc            build with DMALLOC support

Optional Packages:
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --with-gnu-ld           assume the C compiler uses GNU ld [default=no]
  --with-pic              try to use only PIC/non-PIC objects [default=use
                          both]
  --with-tags[=TAGS]
                          include additional configurations [automatic]
  --with-extra-includes=DIR   adds non standard include paths
  --with-extra-libs=DIR       adds non standard library paths
  --with-libosip-prefix=DIR   use libosip2 from DIR/include and DIR/lib
  --with-custom-fwmodule=LIBRARY.a   use custom firewall control module

Some influential environment variables:
  CC          C compiler command
  CFLAGS      C compiler flags
  LDFLAGS     linker flags, e.g. -L<lib dir> if you have libraries in a
              nonstandard directory <lib dir>
  CPPFLAGS    C/C++ preprocessor flags, e.g. -I<include dir> if you have
              headers in a nonstandard directory <include dir>
  CPP         C preprocessor
  CXX         C++ compiler command
  CXXFLAGS    C++ compiler flags
  CXXCPP      C++ preprocessor
  F77         Fortran 77 compiler command
  FFLAGS      Fortran 77 compiler flags

Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.

vielen dank

gruß manuel

Antworten |