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 kris at 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-15 /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
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
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
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!
Configure question about Wine / HAL
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. -- Kris Moore PC-BSD Software http://www.pcbsd.com
Re: Patch for process title on FreeBSD
How exactly would you like that done? I'm not much of a C programmer, I
live more in the C++ / Shell world :)
--
Kris Moore
PC-BSD Software
http://www.pcbsd.com
Alexandre Julliard wrote:
Kris Moore [EMAIL PROTECTED] writes:
--- dlls/kernel32/process.c.orig 2007-12-12 12:34:45.0 -0500
+++ dlls/kernel32/process.c 2007-12-12 12:35:17.0 -0500
@@ -853,6 +853,11 @@
*/
static void set_process_name( int argc, char *argv[] )
{
+
+#if defined(__FreeBSD__)
+setproctitle(-%s, argv[1]);
+#endif
You should add a configure check for this function, instead of checking
for __FreeBSD__.
Re: Patch for process title on FreeBSD
Stefan Dösinger wrote: Am Mittwoch, 12. Dezember 2007 18:50:39 schrieb Kris Moore: Hey all! One of our devs noticed that on FreeBSD we don't get the process name set properly, so in ps we get a lot of wine-pthread garbage. Here's a small patch to fix this in dlls/kernel32/process.c I tried to make this as small simple as possible, please let me know what you think! I think using argv[1] is not the best way, as some wine parameter might be added in the future, or someone might use something like binfmt_misc on Linux to launch the app. In that case the .exe name is propably argv[0], but I am not sure. Any suggestions on how we should weed through this / add this function? It looks like the rest of the function assumes removing argv[0] as well, if I'm reading it right. I've tested this fix out on FreeBSD here, and it looks like it works, showing a process as the actual win exe instead of wine-pthread now. -- Kris Moore PC-BSD Software http://www.pcbsd.com
wine proccess list
Gonzalo sent me this thread, and I may be able to get a patch put together here soon. First, I wanted to make sure I'm on the right path: Can somebody confirm for me that this is the right location where I should be trying to fix this? http://source.winehq.org/source/loader/preloader.c#L1006 FreeBSD has a function called setproctitle(), which I'm pretty sure is the right one for this task. http://www.freebsd.org/cgi/man.cgi?query=setproctitleapropos=0sektion=0manpath=FreeBSD+6.2-RELEASEformat=html I'll probably try and see about a patch here in the next day or so. Who do I send it to if I can get it working? -- Kris Moore PC-BSD Software http://www.pcbsd.com Am Dienstag, 11. Dezember 2007 20:25:20 schrieb Gonzalo Martinez - Sanjuan Sanchez: El Tuesday 11 December 2007 7:34:49 pm escribió: Am Dienstag, 11. Dezember 2007 18:02:53 schrieb Gonzalo Martinez - Sanjuan Sanchez: Hello to all. I have something in mind that I would like to ask to Wine developers. Is it possible using a hack/trick or a hidden option to change the name of wine in the proccess lists? I mean, Is it possible to list 'wine' proccess as, for example 'iexplorer' when I use Internet Explorer under Wine? Thanks a lot for your work, hope my question find the answer here. This is done since quite some time. apps are usually called iexplore.exe, or they have the name of the file that was passed to wine, like C:\Program Files\Internet Explorer\iexplore.exe If you still see wine, wineloader or something similar you have a very outdated version of wine. Well, im talking about Wine 0.9.48 under FreeBSD/PC-BSD OS. Ow, ah, this is a different business. I think we use some Linux-only feature to set the name, and Alexandre told me that at least MacOS doesn't have it. I have no idea if there is a way to change the process name under BSD. If there is, feel free to implement it and send a patch
Looking for Dev to help with BSD Port
Hey all! We're looking for a Wine dev to assist us with some porting issues over to PC-BSD / FreeBSD. We've recently begun to embrace making packages with wine embedded, making the process of loading windows programs a snap. The end user only needs to double-click, insert their CD, and click next a few times. This allowed us to make some packages for programs such as PhotoShop Dreamweaver which even a non-linux/BSD user could install. We really want to expand these packages, to include things such as games, and others, but there are a few problems with running Wine on BSD at the moment. If anybody is willing to help us out with this, please let me know! Here's a list of some of the porting issues were aware of: http://wiki.freebsd.org/Wine Thanks! -- Kris Moore PC-BSD Software http://www.pcbsd.com
