Re: Configure question about Wine / HAL
That Makefile patch fixed the issue! However, the ldd command doesn't seem to return anything for this lib: # ldd libdbus-1.so.3 libdbus-1.so.3: Will you be able to add this patch to the port? Thanks! Tijl Coosemans wrote: > On Saturday 17 May 2008 10:53:18 Jeroen Janssen wrote: >> Kris Moore pcbsd.com> writes: >>> http://www.pcbsd.org/~kris/config.log >> It seems something is wrong with your pthread library? >> >> configure:12388: checking for dbus_connection_close in -ldbus-1 >> configure:12423: cc -o conftest -O2 -fno-strict-aliasing -pipe >> -I/usr/local/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal >> -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include >> -L/usr/local/lib conftest.c -ldbus-1 -L/usr/local/lib -lhal -ldbus-1>&5 >> /usr/local/lib/libdbus-1.so: undefined reference to `pthread_equal' >> /usr/local/lib/libdbus-1.so: undefined reference to `pthread_cond_timedwait' > > This patch to the port Makefile should fix it. The problem exists only > on FreeBSD 6 because libs like libdbus-1 aren't linked to a pthread > library and so when you link an executable with libdbus-1 some > threading lib needs to be explicitly specified as well. Just to confirm > this, can you post the output of "ldd /usr/local/lib/libdbus-1.so" on > FreeBSD 6? > > > !DSPAM:1,482ee23020031175936439! >
Re: Configure question about Wine / HAL
On Saturday 17 May 2008 10:53:18 Jeroen Janssen wrote:
> Kris Moore pcbsd.com> writes:
>> http://www.pcbsd.org/~kris/config.log
>
> It seems something is wrong with your pthread library?
>
> configure:12388: checking for dbus_connection_close in -ldbus-1
> configure:12423: cc -o conftest -O2 -fno-strict-aliasing -pipe
> -I/usr/local/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal
> -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include
> -L/usr/local/lib conftest.c -ldbus-1 -L/usr/local/lib -lhal -ldbus-1>&5
> /usr/local/lib/libdbus-1.so: undefined reference to `pthread_equal'
> /usr/local/lib/libdbus-1.so: undefined reference to `pthread_cond_timedwait'
This patch to the port Makefile should fix it. The problem exists only
on FreeBSD 6 because libs like libdbus-1 aren't linked to a pthread
library and so when you link an executable with libdbus-1 some
threading lib needs to be explicitly specified as well. Just to confirm
this, can you post the output of "ldd /usr/local/lib/libdbus-1.so" on
FreeBSD 6?
--- Makefile.orig 2008-05-17 15:33:49.0 +0200
+++ Makefile2008-05-17 15:26:59.0 +0200
@@ -52,6 +52,7 @@
.if ${OSVERSION} < 700041
${REINPLACE_CMD} 's/-lpthread/-lthr/g' ${WRKSRC}/configure
.endif
+ ${REINPLACE_CMD} '/ac_hal_libs=/s/"$$/ -lthr"/' ${WRKSRC}/configure
pre-build:
cd ${WRKSRC} && make depend
Re: Configure question about Wine / HAL
Kris Moore pcbsd.com> writes: > Here you go! > > http://www.pcbsd.org/~kris/config.log Hey Kris, It seems something is wrong with your pthread library? configure:12388: checking for dbus_connection_close in -ldbus-1 configure:12423: cc -o conftest -O2 -fno-strict-aliasing -pipe -I/usr/local/include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/local/include/hal -I/usr/local/include/dbus-1.0 -I/usr/local/include/dbus-1.0/include -L/usr/local/lib conftest.c -ldbus-1 -L/usr/local/lib -lhal -ldbus-1>&5 /usr/local/lib/libdbus-1.so: undefined reference to `pthread_equal' /usr/local/lib/libdbus-1.so: undefined reference to `pthread_cond_timedwait' and also: configure:15254: checking for -ljack configure:15289: cc -o conftest -O2 -fno-strict-aliasing -pipe -I/usr/local/include -L/usr/local/lib conftest.c -ljack >&5 /usr/local/lib/libjack.so: undefined reference to `pthread_create' /usr/local/lib/libjack.so: undefined reference to `pthread_attr_init' /usr/local/lib/libjack.so: undefined reference to `pthread_exit' /usr/local/lib/libjack.so: undefined reference to `pthread_cancel' /usr/local/lib/libjack.so: undefined reference to `pthread_equal' /usr/local/lib/libjack.so: undefined reference to `pthread_testcancel' /usr/local/lib/libjack.so: undefined reference to `pthread_attr_setscope' /usr/local/lib/libjack.so: undefined reference to `pthread_attr_setinheritsched' /usr/local/lib/libjack.so: undefined reference to `pthread_setschedparam' /usr/local/lib/libjack.so: undefined reference to `pthread_attr_setstacksize' /usr/local/lib/libjack.so: undefined reference to `pthread_attr_setdetachstate' /usr/local/lib/libjack.so: undefined reference to `pthread_join' Can you check pthread is present in your /usr/local/lib? Best regards, Jeroen Janssen
Re: Configure question about Wine / HAL
Here you go! http://www.pcbsd.org/~kris/config.log Tijl Coosemans wrote: > On Friday 16 May 2008 13:26:29 Kris Moore wrote: >> I just rebuilt wine 0.9.61 from ports, and same problem: >> >> checking dbus/dbus.h usability... yes >> checking dbus/dbus.h presence... yes >> checking for dbus/dbus.h... yes >> checking hal/libhal.h usability... yes >> checking hal/libhal.h presence... yes >> checking for hal/libhal.h... yes >> checking for dbus_connection_close in -ldbus-1... no >> >> Here's the complete build.log: >> http://www.pcbsd.org/~kris/build.log.gz >> >> Here's the package list of this chroot environment >> http://www.pcbsd.org/~kris/pkg_list >> >> For the record, I'm building wine in a chroot environment for usage >> in our PBI format. However, as you can see from the pkg_list, I have >> built all the various packages that should be required. I also tried >> building the port on my desktop directly, and had the exact same >> error, so I'm sure its nothing about the chroot environment causing >> this problem. > > Thanks, but I still want to have a look at config.log because I suspect > /usr/local/include and /usr/local/lib aren't added to CPPFLAGS and > LDFLAGS properly and config.log contains more info about that. It > should be in the Wine build dir after running configure. > > !DSPAM:1,482d7d3a20034557112297! > >
Re: Configure question about Wine / HAL
On Friday 16 May 2008 13:26:29 Kris Moore wrote: > I just rebuilt wine 0.9.61 from ports, and same problem: > > checking dbus/dbus.h usability... yes > checking dbus/dbus.h presence... yes > checking for dbus/dbus.h... yes > checking hal/libhal.h usability... yes > checking hal/libhal.h presence... yes > checking for hal/libhal.h... yes > checking for dbus_connection_close in -ldbus-1... no > > Here's the complete build.log: > http://www.pcbsd.org/~kris/build.log.gz > > Here's the package list of this chroot environment > http://www.pcbsd.org/~kris/pkg_list > > For the record, I'm building wine in a chroot environment for usage > in our PBI format. However, as you can see from the pkg_list, I have > built all the various packages that should be required. I also tried > building the port on my desktop directly, and had the exact same > error, so I'm sure its nothing about the chroot environment causing > this problem. Thanks, but I still want to have a look at config.log because I suspect /usr/local/include and /usr/local/lib aren't added to CPPFLAGS and LDFLAGS properly and config.log contains more info about that. It should be in the Wine build dir after running configure.
Re: Configure question about Wine / HAL
I just rebuilt wine 0.9.61 from ports, and same problem: checking dbus/dbus.h usability... yes checking dbus/dbus.h presence... yes checking for dbus/dbus.h... yes checking hal/libhal.h usability... yes checking hal/libhal.h presence... yes checking for hal/libhal.h... yes checking for dbus_connection_close in -ldbus-1... no Here's the complete build.log: http://www.pcbsd.org/~kris/build.log.gz Here's the package list of this chroot environment http://www.pcbsd.org/~kris/pkg_list For the record, I'm building wine in a chroot environment for usage in our PBI format. However, as you can see from the pkg_list, I have built all the various packages that should be required. I also tried building the port on my desktop directly, and had the exact same error, so I'm sure its nothing about the chroot environment causing this problem. Thanks! Tijl Coosemans wrote: > On Thursday 15 May 2008 17:59:17 Kris Moore wrote: >> I was building the port, and hal / dbus were both installed. The >> funny thing was that the first time I built the port, it didn't even >> get this far, it said : "checking for hal/libhal.h... no", but if I >> checked in /usr/local/include/hal, libhal.h was in there. Then I made >> a link to /usr/include "ln -s /usr/local/include/hal >> /usr/include/hal" and was able to get this far now. > > Can you upload the config.log file somewhere? Or mail it to me > privately. > > !DSPAM:1,482d67ef20031449582031! > >
Re: Configure question about Wine / HAL
On Thursday 15 May 2008 17:59:17 Kris Moore wrote: > I was building the port, and hal / dbus were both installed. The > funny thing was that the first time I built the port, it didn't even > get this far, it said : "checking for hal/libhal.h... no", but if I > checked in /usr/local/include/hal, libhal.h was in there. Then I made > a link to /usr/include "ln -s /usr/local/include/hal > /usr/include/hal" and was able to get this far now. Can you upload the config.log file somewhere? Or mail it to me privately.
Re: Configure question about Wine / HAL
Kris Moore pcbsd.com> writes: > > I was building the port, and hal / dbus were both installed. The funny > thing was that the first time I built the port, it didn't even get this > far, it said : "checking for hal/libhal.h... no", but if I checked in > /usr/local/include/hal, libhal.h was in there. Then I made a link to > /usr/include "ln -s /usr/local/include/hal /usr/include/hal" and was > able to get this far now. > > I will cvsup again tonight and recheck this to confirm my findings though. You might want to try using --hal-includes=/usr/local/include and --hal-libraries=/usr/local/lib/ (or something similar). At least that is what should be possible if I read configure --help correctly. Maybe "checking for dbus_connection_close in -ldbus-1" requires to be able to link to the hal libraries? (and only symlinking the hal include path doesn't result in the libaries to be found). Hope this helps, Jeroen Janssen
Re: Configure question about Wine / HAL
I was building the port, and hal / dbus were both installed. The funny thing was that the first time I built the port, it didn't even get this far, it said : "checking for hal/libhal.h... no", but if I checked in /usr/local/include/hal, libhal.h was in there. Then I made a link to /usr/include "ln -s /usr/local/include/hal /usr/include/hal" and was able to get this far now. I will cvsup again tonight and recheck this to confirm my findings though. -- Kris Moore PC-BSD Software http://www.pcbsd.com Tijl Coosemans wrote: > On Wednesday 14 May 2008 22:03:35 Kris Moore wrote: >> I'm trying to get Wine to compile with HAL support on FreeBSD, and >> running into this error: >> >>> checking dbus/dbus.h usability... yes >>> checking dbus/dbus.h presence... yes >>> checking for dbus/dbus.h... yes >>> checking hal/libhal.h usability... yes >>> checking hal/libhal.h presence... yes >>> checking for hal/libhal.h... yes >>> checking for dbus_connection_close in -ldbus-1... no >>> configure: error: libhal development files not found, no dynamic device >>> support. >>> This is an error since --with-hal was requested. >> What exactly is -ldbus-1? Is there a way around this? Configure is >> finding the dbus and hal headers properly, and they both work >> properly on the system. > > Are you building using the wine port? Because that should autodetect > HAL when it's installed. If you're not using the port and running > configure yourself you probably need to set LDFLAGS. Something like: > > env CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure > --verbose --with-hal > > !DSPAM:1,482bfef620034310919711! > >
Re: Configure question about Wine / HAL
On Wednesday 14 May 2008 22:03:35 Kris Moore wrote: > I'm trying to get Wine to compile with HAL support on FreeBSD, and > running into this error: > >> checking dbus/dbus.h usability... yes >> checking dbus/dbus.h presence... yes >> checking for dbus/dbus.h... yes >> checking hal/libhal.h usability... yes >> checking hal/libhal.h presence... yes >> checking for hal/libhal.h... yes >> checking for dbus_connection_close in -ldbus-1... no >> configure: error: libhal development files not found, no dynamic device >> support. >> This is an error since --with-hal was requested. > > What exactly is -ldbus-1? Is there a way around this? Configure is > finding the dbus and hal headers properly, and they both work > properly on the system. Are you building using the wine port? Because that should autodetect HAL when it's installed. If you're not using the port and running configure yourself you probably need to set LDFLAGS. Something like: env CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" ./configure --verbose --with-hal
Re: Configure question about Wine / HAL
Hello Kris, 2008/5/14 Kris Moore <[EMAIL PROTECTED]>: > > I'm trying to get Wine to compile with HAL support on FreeBSD, and > running into this error: > > > checking dbus/dbus.h usability... yes > > checking dbus/dbus.h presence... yes > > checking for dbus/dbus.h... yes > > checking hal/libhal.h usability... yes > > checking hal/libhal.h presence... yes > > checking for hal/libhal.h... yes > > checking for dbus_connection_close in -ldbus-1... no > > configure: error: libhal development files not found, no dynamic device > > support. > > This is an error since --with-hal was requested. > > > What exactly is -ldbus-1? Is there a way around this? Configure is > finding the dbus and hal headers properly, and they both work properly > on the system. How do you link to libhal on freebsd? And how do you link to libdbus? Cheers, Maarten.
