Is setting +pulseaudio by default for gstreamer1-gst-plugins-good really necessary?
Hi everyone, The dependency on gstreamer plugins has recently grown in Wine. When installing -good I noticed it has pulseaudio as a default variant. Looking at the portfile I couldn't find a reason why. Building with -pulseaudio works fine for me. Could anyone shed some light on this decision? Using/requiring pulseaudio seems counterproductive to me. Kind regards, Gijs
Re: wine-devel could not load binary
Hi Ryan, Thank you for the fast responses and sorry for my late one. I can confirm that 4.0-rc3 works again. I haven't tested extensively, but if I notice anything odd I'll let you know. Regards, Gijs Op vr 28 dec. 2018 om 20:10 schreef Ryan Schmidt : > > > On Dec 22, 2018, at 16:06, Ryan Schmidt wrote: > > > On Dec 22, 2018, at 15:33, Ryan Schmidt wrote: > > > >> Another possible solution is to remove our wrapper -- I don't remember > why it exists. When I first added the wine port 12 years ago, I said there > were "font issues", but I don't remember what I meant by that: > >> > >> https://trac.macports.org/ticket/11779#comment:2 > >> > >> I apparently fixed it by adding the wrapper script: > >> > >> > https://github.com/macports/macports-ports/commit/88d79d741bf86b96ce4fd23386d05b0f90001867 > > > > To try removing the wrapper, you could: > > > > sudo mv /opt/local/libexec/wine/wine /opt/local/bin/wine > > > > See if you notice any font problems or error messages with programs you > run using wine after that. > > > > If you later want to undo the change, you can: > > > > sudo port -f deactivate wine-devel && sudo port activate wine-devel > > I've made this change in 4.0-rc3. If you notice any font problems or other > errors, let me know. > >
wine-devel could not load binary
Hi everyone, I'm having issues with wine-devel since upgrading from 3.18 to 4.0rc2. When I run wine --help it works, but running anything else yields "/opt/local/lib/../bin/wine: could not load binary" My machine is a 2015 MacBook Pro running macOS High Sierra (fully updated). I have tried completely removing macports and installing everything again from scratch. I was wondering if anyone else has experienced this issue. Regards, Gijs
Re: rdepof:wine-devel +x11 +universal fails on installing xattr
Hi, Thank you both for the answers. In the end I ended up using Ryan's command that excludes xattr and that worked perfectly. Thanks again! Regards, Gijs Op za 8 sep. 2018 om 02:54 schreef Ken Cunningham < ken.cunningham.web...@gmail.com>: > > On 2018-09-07, at 5:33 PM, Ryan Schmidt wrote: > > > > I understand that you are saying that, but I'm not convinced that's > desirable behavior. > > > > What criteria do you propose to use to exclude the dependency? The > dependency is written "bin:xattr:xattr". Do you propose to exclude all bin > (and lib?) dependencies? Or do you only propose to exclude bin (and lib?) > dependencies that are already satisfied by the specified program (or > library?)? And if so, do you exclude the dependency regardless of how the > dependency was satisfied, or only if the dependency was satisfied by a file > outside of MacPorts? And if the latter, where in MacPorts base should that > determination be made? (As far as I know, MacPorts base doesn't currently > care where the file that satisfies a bin (or lib) dependency is located.) > > > > Whew -- might take me a while to digest all that. > > In essence, I think most users would expect that: > > port echo rdepof:wine-devel +x11 +universal > > would lead to more or less the same dependencies being listed as would be > installed if you instead did: > > port install wine-devel +x11 +universal > > But if that is not desirable behaviour for some reason, OK. I actually > don't use rdepof. > > Best, > > Ken
Re: rdepof:wine-devel +x11 +universal fails on installing xattr
Hi again, Thank you for the reply! Op vr 7 sep. 2018 om 22:34 schreef Ryan Schmidt : > The xattr command is included in Mac OS X Leopard and later, so there > should be no need to install the xattr port on recent systems. The xattr > port only exists for Tiger, which did not include that command. > > If MacPorts is trying to install the xattr port on your system, that > implies that your operating system's /usr/bin/xattr command is missing. If > that's so, restore it from your backups or reinstall macOS. > I am trying this on a clean (just installed xcode, command line tools, java and macports) install of High Sierra (fully updated). I just checked and xattr exists in /usr/bin/xattr: Gijss-MacBook-Pro:~ gverm$ which xattr /usr/bin/xattr So I'm not sure what could be wrong. Regards, Gijs
Re: rdepof:wine-devel +x11 +universal fails on installing xattr
Sorry for the noise, but I'm running the latest version of macports on macOS High Sierra, also the latest version. Op vr 7 sep. 2018 om 19:19 schreef Gijs Vermeulen : > Hi, > > I need some help installing wine dependencies. > I tried running port install -v rdepof:wine-devel +x11 +universal but it > fails when it tries to install xattr. > > I get "Error: xattr cannot be installed for the configured universal_archs > 'x86_64 i386' because it only supports the arch(s) 'i386 ppc'." > > Is there anything wrong with the command I am running or is there > something I can do to fix it (I can't add ppc to the universal_archs > because then other stuff will start failing)? > > Regards, > Gijs >
rdepof:wine-devel +x11 +universal fails on installing xattr
Hi, I need some help installing wine dependencies. I tried running port install -v rdepof:wine-devel +x11 +universal but it fails when it tries to install xattr. I get "Error: xattr cannot be installed for the configured universal_archs 'x86_64 i386' because it only supports the arch(s) 'i386 ppc'." Is there anything wrong with the command I am running or is there something I can do to fix it (I can't add ppc to the universal_archs because then other stuff will start failing)? Regards, Gijs
