Re: Skype 4.3 core dump
On Sunday, September 28, 2014 6:08:01 AM Ajtim wrote: > Hi! > > I use Linux c6 from end of July and at the same time I have to used Skype > 4.2 which worked very good. Than I updated to version 4.3 which start and -snip- If it worked, why did you update? Skype 4.3 needs newer features than our linux emulation layer supports yet, but there is ongoing work in this area.. Just remember "If it ain't broke, don't fix it" -- Chuck Burns Audemus Jura Nostra Defendere ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Current problem reports assigned to emulat...@freebsd.org
On Monday, November 05, 2012 01:30:17 PM Tijl Coosemans wrote: > > S Tracker Resp. Description > > -- > > -- o ports/172619 emulation [patch] www/linux-f10-flashplugin11: > > security update > Can I politely ask for emulation@ to give up maintainership for this port? > Nobody here keeps this port updated and when patches are submitted nobody > commits them. That's the point of having emulation@ being the maintainer, when there isn't another maintainer, for a port that is in-use. Otherwise, if someone wants to maintain this port, just contact the team, and have it moved to you. -- Chuck Burns (brea...@gmail.com) ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: [Call for Testers] VirtualBox 4.2.4
On 10/30/2012 3:41 PM, Mike Jakubik wrote: On Tuesday 30 October 2012 4:24:24 PM Mikhail Tsatsenko wrote: 2012/10/31 Mike Jakubik : On Tuesday 30 October 2012 3:56:29 PM Bernhard Fröhlich wrote: On Tue, Oct 30, 2012 at 8:12 PM, Mike Jakubik My understanding is that Clang will be the default compiler in FreeBSD 10, how will the port be compiled then? VBox port will be using gcc from ports tree (as a build dependency). I see, should it not support an up to date version of gcc then? I dont like the idea of having a dependancy on an obsolete compiler just to compile one port. Then try it with the "stable" gcc: 4.6.x -- It should compile then. -- Chuck Burns ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On 09/30/2012 11:34 AM, David Naylor wrote: On Sunday, 30 September 2012 16:22:30 Chuck Burns wrote: On 09/30/2012 09:06 AM, David Naylor wrote: The current pkg format can be installed along side a pkgng installation (the nvidia patching will detect the pkgng packages). Has this not worked on your setup? Yes, this works, I was hoping to be as "native" as possible. :) Doing so will increase my workload by 33% and I'm not willing to devote extra resources given that it currently works anyway. However, the usage of the FreeBSD-8 packages are low, so I may drop support for them and reconsider supporting pkgng for FreeBSD 9. It would also provide an interesting barometer for adoption of pkgng (I myself use it, except for wine packages, on FreeBSD-9). Regards How do you build this, anyway? I would love to be able to "cut out the middle man" so to speak. I know the general idea is: build it in a 32bit jail. But do you do it with a script? or just manually build the packages? -- Chuck Burns ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On 09/30/2012 09:06 AM, David Naylor wrote: The current pkg format can be installed along side a pkgng installation (the nvidia patching will detect the pkgng packages). Has this not worked on your setup? Yes, this works, I was hoping to be as "native" as possible. :) Chuck Burns ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine-fbsd64 updated to 1.5.13 (32bit Wine for 64bit FreeBSD)
On 9/24/2012 3:29 PM, David Naylor wrote: Hi, NOTICE: - fix: CUPS support should now work - fix: GNUTLS support should now work - CFT: with FreeBSD(-current) planning on switching to clang as default compiler (for world/kernel) could you please check if wine runs with a clang compiled world. Previous reports indicate wine (and libreoffice) didn't work with a clang libc however that may have been fixed. Please report for both success or failure and include `uname -a` and `clang --version`. Thanks Packages [1] for wine-fbsd64-1.5.13 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. Regards, David What is the possibility of a pkgng package for 9-stable, for those of us already using/testing pkgng on our 9.x systems? -- Chuck Burns ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: wine && libgnutls
On Sat, Sep 15, 2012 at 4:33 AM, Matthias Apitz wrote: > > Hello, > > I must use wine(1) to run some Adobe Digital Editions tool (which seems > to work fine with wine in general, the wine pages say it runs); > > When I start: > > $ wine digitaleditions_172.exe > > it can't find some shared lib for TLS: > > err:secur32:SECUR32_initSchannelSP libgnutls not found, SSL connections > will fail > > I have: > > $ uname -a > 9.0-CURRENT #1 r21: Thu Oct 28 10:56:32 CEST 2010 > $ pkg_info | egrep 'wine|gnutls' > gnutls-2.8.6_2 GNU Transport Layer Security library > wine-1.3.6,1Microsoft Windows compatibility layer for Unix-like > systems > > Any idea why wine(1) can't see the gnutls lib? Thanks > > matthias > > -- > Matthias Apitz | /"\ ASCII Ribbon Campaign: www.asciiribbon.org > E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail > WWW: http://www.unixarea.de/ | X - No proprietary attachments > phone: +49-170-4527211 | / \ - Respect for open standards > ___ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" Just because they both exist does not mean that wine was compiled to take advantage of it. Did you install from package, or build wine yourself? If you build it yourself, you can make config -C /usr/ports/emulators/wine and enable gnutls support. ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD)
On 01/11/12 10:24, Martin Simmons wrote: On Tue, 10 Jan 2012 17:20:04 -0600, Chuck Burns said: On 01/10/12 10:49, David Naylor wrote: I wasn't aware of WoW64 (and how it will make my packages redundent :->). I see there are two wiki pages: + http://wiki.winehq.org/Wine64 + http://wiki.winehq.org/Wine64ForPackagers The latter makes this statement "Wine 64bit works at the moment only on Linux." which would indicate that, at this stage, FreeBSD is precluded. That, however, is just my speculation. To answer your question directly, I have put no thought or effort into wine64. There is still a need for the 32bit wine, as the wow64 build will ONLY run 64bit windows apps, so for the majority of applications and games, we'll still need the 32bit wine. Is that because wow64 is unstable in wine64? Wow64's reason for existence is to run 32-bit Windows binaries on 64-bit Windows/Wine and it works pretty well for most applications. __Martin ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org" wow64 doesnt -exist- in wine64 unless you compile the 32bit wine alongside it. You have to build it twice, to get two binaries "wine" and "wine64" and if you build them "properly" what happens when you attempt to execute a 64bit app with "wine" it's automatically relaunched with "wine64" But the reverse is NOT true. -- Chuck Burns The Southern Libertarian http://www.thesouthernlibertarian.com/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD)
On 01/10/12 10:49, David Naylor wrote: I wasn't aware of WoW64 (and how it will make my packages redundent :->). I see there are two wiki pages: + http://wiki.winehq.org/Wine64 + http://wiki.winehq.org/Wine64ForPackagers The latter makes this statement "Wine 64bit works at the moment only on Linux." which would indicate that, at this stage, FreeBSD is precluded. That, however, is just my speculation. To answer your question directly, I have put no thought or effort into wine64. There is still a need for the 32bit wine, as the wow64 build will ONLY run 64bit windows apps, so for the majority of applications and games, we'll still need the 32bit wine. -- Chuck Burns The Southern Libertarian http://www.thesouthernlibertarian.com/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
Re: Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD)
On 01/09/12 12:17, David Naylor wrote: Hi, Packages [1] for wine-fbsd64-1.3.36 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.36,1.tbz) = 019cdde0ff7fad7dc877ed1e3bc3c481 MD5 (freebsd9/wine-fbsd64-1.3.36,1.txz) = 7fe1bbd75c8c6af1d3fe6f0a03841fa2 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh Have you put any thought into getting both wine and wine64 (for Wow64 apps) working? There have been more than a few people hopping onto IRC asking about wine64 (full 64bit wine) -- Chuck Burns The Southern Libertarian http://www.thesouthernlibertarian.com/ ___ freebsd-emulation@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
