Re: [proaudio] jack compilation error again

[Frieder Bürzele <evermind@xxxxxxxxxxxxx>]

Arve Barsnes wrote:
> On Thu, Aug 14, 2008 at 12:01 PM, Frieder Bürzele
> <evermind@xxxxxxxxxxxxx> wrote:
>> Arve Barsnes wrote:
>>> For jack-audio-connection-kit-9999
>>>
>>> ./.libs/libjackserver.so: undefined reference to `dbus_error_init'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_error_is_set'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_connection_send'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_connection_flush'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_message_unref'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_bus_get'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_error_free'
>>> ./.libs/libjackserver.so: undefined reference to `dbus_message_new_method_call'
>>> collect2: ld returned 1 exit status
>> This is a linker error -- it seems that the library is not known by the linker
>> pls post also relevant messsages prior to this error
>>
> 
> configure: WARNING: overriding D-Bus service install dir
> ------------
> | D-Bus service install dir............................. :
> /usr/share/dbus-1/services
> ------------
> libtool: link: (cd ".libs" && rm -f "libjackserver.so.0" && ln -s
> "libjackserver.so.0.0.28" "libjackserver.so.0")
> libtool: link: (cd ".libs" && rm -f "libjackserver.so" && ln -s
> "libjackserver.so.0.0.28" "libjackserver.so")
> libtool: link: ( cd ".libs" && rm -f "libjackserver.la" && ln -s
> "../libjackserver.la" "libjackserver.la" )
> /bin/sh ../libtool --tag=CC   --mode=link x86_64-pc-linux-gnu-gcc
> -I../config -I.. -I.. -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g
> -O2 -march=nocona -pipe -I/usr/include/nptl
> -DJACK_LOCATION=\"/usr/bin\" -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include   -I/usr/include/libxml2   -I../config
> -I.. -I.. -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2
> -march=nocona -pipe -I/usr/include/nptl -march=nocona    -Wl,-O1
> -Wl,--as-needed -o jackd jackd.o engine.o clientengine.o transengine.o
> libjackserver.la -lcap  -lrt -ldbus-1   -lm -lpthread -ldl
> -lsamplerate
> libtool: link: x86_64-pc-linux-gnu-gcc -I../config -I.. -I..
> -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2 -march=nocona
> -pipe -I/usr/include/nptl -DJACK_LOCATION=\"/usr/bin\"
> -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include
> -I/usr/include/libxml2 -I../config -I.. -I.. -D_REENTRANT
> -D_POSIX_PTHREAD_SEMANTICS -Wall -g -O2 -march=nocona -pipe
> -I/usr/include/nptl -march=nocona -Wl,-O1 -Wl,--as-needed -o
> .libs/jackd jackd.o engine.o clientengine.o transengine.o
> ./.libs/libjackserver.so -lcap -lrt /usr/lib64/libdbus-1.so -lpthread
> -ldl /usr/lib64/libsamplerate.so -lm
> ./.libs/libjackserver.so: undefined reference to `dbus_error_init'
> ./.libs/libjackserver.so: undefined reference to `dbus_error_is_set'
> ./.libs/libjackserver.so: undefined reference to `dbus_connection_send'
> ./.libs/libjackserver.so: undefined reference to `dbus_connection_flush'
> ./.libs/libjackserver.so: undefined reference to `dbus_message_unref'
> ./.libs/libjackserver.so: undefined reference to `dbus_bus_get'
> ./.libs/libjackserver.so: undefined reference to `dbus_error_free'
> ./.libs/libjackserver.so: undefined reference to `dbus_message_new_method_call'
> collect2: ld returned 1 exit status
> make[2]: *** [jackd] Error 1
> 
> Couldn't find anything else that looked like errors at all.
> 



could you please also test what reaveals is /usr/lib64/libdbus-1.so just a symlink to /usr/lib/libdbus-1.so?
(I could not check that myself as I'm on x86)

strings /usr/lib64/libdbus-1.so|grep dbus_error_init




>> does
>> strings /usr/lib/libdbus-1.so|grep dbus_error_init
>> reveal someting?
>>
> # strings /usr/lib/libdbus-1.so | grep dbus_error_init
> dbus_error_init
> dbus_error_init
> 
>>> I tried rebuilding dbus, with no change, so I have no idea what could
>>> be wrong here.
>>>
>>> I see that jack 0.109 was released 2008, but I can't find any
>>> changelog in svn that details anything newer than 2005 changes. Is
>>> there not much development on jack1 anymore? Should I try harder to
>>> get jackdmp working?
>>>
>>>
>> thats not posssible the latest log entry is from 2008-07-25.
>> But dbus is just a patch and not yet merged into.
> 
> Where do you find this log? I noticed in the changelog for jack2
> (where latest change is in August) that this and that was backported
> to trunk. I'm guessing that trunk is jack1, but I could be wrong.
> 
>