Re: Updating emulators/i386-wine-devel but get a runtime error
Nevermind, it was that WINEDLLPATH was missing. -Neel On 2021-02-23 13:01, Neel Chauhan wrote: Hi freebsd-ports@ I recently adopted emulators/i386-wine-devel and am attempting to update it to 6.2 along with adding 14.0 support. Phabricator URL: https://reviews.freebsd.org/D28908 When I attempt to run the `wine` command, I get this error: root@omen:/usr/ports.dev/emulators/i386-wine-devel # wine wine: could not load ntdll.so: (null) root@omen:/usr/ports.dev/emulators/i386-wine-devel # It seems ntdll.so is a new DLL. For anyone who has worked with Wine, is there a reason why this is happening and how I can solve this? -Neel ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Updating emulators/i386-wine-devel but get a runtime error
Hi freebsd-ports@ I recently adopted emulators/i386-wine-devel and am attempting to update it to 6.2 along with adding 14.0 support. Phabricator URL: https://reviews.freebsd.org/D28908 When I attempt to run the `wine` command, I get this error: root@omen:/usr/ports.dev/emulators/i386-wine-devel # wine wine: could not load ntdll.so: (null) root@omen:/usr/ports.dev/emulators/i386-wine-devel # It seems ntdll.so is a new DLL. For anyone who has worked with Wine, is there a reason why this is happening and how I can solve this? -Neel signature.asc Description: OpenPGP digital signature
emulators/i386-wine{-devel} unable to run config-recursive
I ran into an interesting scenario. While attempting to build emulators/i386-wine-devel within a FreeBSD 12 i386 poudriere jail, I found that I was unable to run make config-recursive (via poudriere options). The error was: root@portbuild:/usr/ports/emulators/i386-wine-devel # make config-recursive ===> Setting user-specified options for i386-wine-devel-4.21,1 and dependencies make[1]: "/usr/ports/Mk/bsd.port.mk" line 1577: Unassociated shell command "@${FALSE}" make[1]: "/usr/ports/Mk/bsd.gcc.mk" line 190: warning: duplicate script for target "test-gcc" ignored make[1]: "/usr/ports/Mk/bsd.gcc.mk" line 215: warning: using previous script for "test-gcc" defined here ... The first line is make attempting to complain that bsd.port[.post].mk was loaded twice. That is probably its own bug in that it could not report the error correctly. I am not sure why the code does not just use .error to exit at that point. The issue stopping the port from building is that it has a Makefile.i386 file in it. At first, I thought it was because it was including the Makefile which included the master Makefile and had an error due to some sort of SHLVL equivalent. That was not it. It turns out that the Makefile.i386 existence was the issue causing bsd.port.mk to be included twice. I renamed it to Makefile.cross, and it worked. My question is whether it should have worked as Makefile.i386, as it used to work, or should the i386-wine and i386-wine-devel ports have their Makefile.i386 files renamed. Sean -- s...@freebsd.org ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
emulators/i386-wine-devel build failure
Hi, Subj i386-wine-devel depends on file /usr/local/share/wine/mono/wine-mono-4.7.1.msi But we have wine-mono-devel-4.7.5 in ports tree. [tiger@laptop]:/<2>emulators/wine-devel>pkg info -xl wine-mo |grep msi /usr/local/share/wine/mono/wine-mono-4.7.5.msi -- wbr, Sergey ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: emulators/i386-wine-devel
On Sunday, 16 September 2018 23:51:01 SAST Rozhuk Ivan wrote: > On Sat, 15 Sep 2018 10:06:01 +0200 > Thanks! > I already subscribe to this and post few comments. > I have no choice - I need wine to few win programs. Is the current version of i386-wine(-devel) not working for you? I understand that these are become quite old version. I'm hoping that we can complete the lib32 work (and then the WOW64 patch) before things become too stale. Regards signature.asc Description: This is a digitally signed message part.
Re: emulators/i386-wine-devel
On Sat, 15 Sep 2018 10:06:01 +0200 David Naylor wrote: > Hi > > > What happen with emulators/i386-wine-devel ? > > Honestly, I've lost interest in compiling the port. I'm working on a > means to avoid manual compilation [1][2]. I've attached the scripts > I use to build and update the ports - if anyone is interested. > > > I use it on FreeBSD 11.2 x64 to run old win32 apps. > > The above mentioned work will also make running win64 apps > concurrently with win32 apps. > > Regards > > [1] https://reviews.freebsd.org/D14721 > [2] https://reviews.freebsd.org/D16830 Thanks! I already subscribe to this and post few comments. I have no choice - I need wine to few win programs. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: emulators/i386-wine-devel
On Saturday, 01 September 2018 22:45:58 SAST Rozhuk Ivan wrote: > Hi! Hi > What happen with emulators/i386-wine-devel ? Honestly, I've lost interest in compiling the port. I'm working on a means to avoid manual compilation [1][2]. I've attached the scripts I use to build and update the ports - if anyone is interested. > I use it on FreeBSD 11.2 x64 to run old win32 apps. The above mentioned work will also make running win64 apps concurrently with win32 apps. Regards [1] https://reviews.freebsd.org/D14721 [2] https://reviews.freebsd.org/D16830 signature.asc Description: This is a digitally signed message part.
emulators/i386-wine-devel
Hi! What happen with emulators/i386-wine-devel ? I use it on FreeBSD 11.2 x64 to run old win32 apps. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"