Re: Wine & PlayOnBSD
Am 09.01.2017 um 21:20 schrieb Grzegorz Junka:
> Thank you for the additional information. The PlayOnLinux documentation
> mentions some dedicated application to actually install or run the
> Windows apps from some UI. Is this supported in PlayOnBSD?
Yes, there is an UI that allows to modify settings (e.g. whether to use
some native DLL) for supported Windows applications.
You can also create Desktop Icons that let you directly start Wine with
the covered Windows applications.
Somebody reported, that these icons were not correctly created. I have
tried to implement a fix, but I'm not sure that it works (do not use KDE
or any other XDG compatible WM). If you give PlayOnBSD a try and find,
that these icons do not work, than I'll take another look at the script
that creates these icons and puts the required path and options into
the parameters for that icon.
> Also, is there any reason why PlayOnBSD depends on a 64-bit version of
> wine? I would have thought that 32-bit version could give a better
> compatibility?
See this comment for "${ARCH} == amd64" in emulators/wine/Makefile:
% # Wine is composed of three parts:
% # - wine (aka this port) is the 32-bit component and runs 32-bit
programs (on FreeBSD/i386)
% # - wine64 (aka this part of this port) is the 64-bit component and
runs 64-bit programs
% #(on FreeBSD/amd64)
% # - wow64 (a subset of emulators/i386-wine-devel) is a part of the
64-bit component that runs
% #32-bit programs (on FreeBSD/amd64)
% # We also currently have:
% # - "wine32" (aka emulators/i386-wine-devel) is the 32-bit component
and runs 32-bit programs
% #(on FreeBSD/amd64). This will be superseded by wow64.
I do not have any i386 systems (except for poudriere jails used to build
and test new/modified ports), but IMHO i386-wine is compiled for a real
i386 as "host" and runs 32 bit Windows programs only (for lack of 64
bit support in the host processor).
I have tested a number of 32 bit Windows applications with the 64 bit
version of Wine (i.e. built for amd64), and they worked as expected.
Regards, STefan
___
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: openldap-client vs openldap-sasl-client
Franco Fichtner wrote on 2017/01/10 06:48: On 9 Jan 2017, at 11:54 PM, Miroslav Lachman <000.f...@quip.cz> wrote: I don't need SASL for LDAP client, but somebody messed up ports tree with WANT_OPENLDAP_SASL which is for users and not maintainers: # WANT_OPENLDAP_SASL # - User-defined variable to depend upon SASL-enabled OpenLDAP # client. Must NOT be set in a port Makefile. This note was added two days ago and it's simply not correct, and/or overcome by events as it is against the common practice in the tree *and* adhering to it would break currently working ports. Even if this doesn't exist at all the change was bad handled. No info in UPDATING and what was working for years now doesn't work. Simple "pkg upgrade" failed because of conflicting versions of openldap-client. OpenLDAP needs framework improvements of the sort that gssapi or ssl received, but we have yet to hear from the maintainer of OpenLDAP on the matter. And changes like this must be better tested before committing... Breakages are too common in these days. Miroslav Lachman ___ 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: Wine & PlayOnBSD
10.01.2017 12:41, Stefan Esser пишет:
Am 09.01.2017 um 21:20 schrieb Grzegorz Junka:
Thank you for the additional information. The PlayOnLinux documentation
mentions some dedicated application to actually install or run the
Windows apps from some UI. Is this supported in PlayOnBSD?
Yes, there is an UI that allows to modify settings (e.g. whether to use
some native DLL) for supported Windows applications.
You can also create Desktop Icons that let you directly start Wine with
the covered Windows applications.
Somebody reported, that these icons were not correctly created. I have
tried to implement a fix, but I'm not sure that it works (do not use KDE
or any other XDG compatible WM). If you give PlayOnBSD a try and find,
that these icons do not work, than I'll take another look at the script
that creates these icons and puts the required path and options into
the parameters for that icon.
Also, is there any reason why PlayOnBSD depends on a 64-bit version of
wine? I would have thought that 32-bit version could give a better
compatibility?
See this comment for "${ARCH} == amd64" in emulators/wine/Makefile:
% # Wine is composed of three parts:
% # - wine (aka this port) is the 32-bit component and runs 32-bit
programs (on FreeBSD/i386)
% # - wine64 (aka this part of this port) is the 64-bit component and
runs 64-bit programs
% #(on FreeBSD/amd64)
% # - wow64 (a subset of emulators/i386-wine-devel) is a part of the
64-bit component that runs
% #32-bit programs (on FreeBSD/amd64)
% # We also currently have:
% # - "wine32" (aka emulators/i386-wine-devel) is the 32-bit component
and runs 32-bit programs
% #(on FreeBSD/amd64). This will be superseded by wow64.
I do not have any i386 systems (except for poudriere jails used to build
and test new/modified ports), but IMHO i386-wine is compiled for a real
i386 as "host" and runs 32 bit Windows programs only (for lack of 64
bit support in the host processor).
I have tested a number of 32 bit Windows applications with the 64 bit
version of Wine (i.e. built for amd64), and they worked as expected.
i386-wine is created for amd64 systems. wine on amd64 can't execute
32-bit programs.
See emulators/wine/Makefile
# Wine assumes a WoW64 package is available however WoW64 is not yet
available on FreeBSD.
___
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"
Nieuwe vacatures voor verkoper 2017-01-10
___ 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"
several ports: clang include errors on 12
Hello. I'm trying the drm-next source tree (Macy et al.) Naturally I have to re-build all ports (appx 2100) for my testing. Im getting a common build error for several ports (15+ so far) with fail point as "compiler include" for: xmmintrin.h emmintrin.h cpuid.h The poudriere build environment has ccache enabled and the "missing" includes are under ~jail/usr/lib/clang/3.9.1/include/ Can anyone give some pointers where to look further? I have not tested with ccache disabled, but since some 300 ports already built without problem, I doubt the problem is ccache. I can't tell whether the source is per port or in a MK/bsd* file, the problem involve sse2 AFIK, but world/kernel should not cause this? Some pointers please on how to debug and I'll get to it... ___ 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: several ports: clang include errors on 12
On 10 Jan 2017, at 17:45, Raif S. Berent via freebsd-ports wrote: > > Hello. I'm trying the drm-next source tree (Macy et al.) > Naturally I have to re-build all ports (appx 2100) for my testing. > > Im getting a common build error for several ports (15+ so far) with fail > point as "compiler include" for: xmmintrin.h emmintrin.h cpuid.h > > The poudriere build environment has ccache enabled and the "missing" includes > are under > ~jail/usr/lib/clang/3.9.1/include/ > > Can anyone give some pointers where to look further? I have not tested with > ccache disabled, but since some 300 ports already built without problem, I > doubt the problem is ccache. > I can't tell whether the source is per port or in a MK/bsd* file, the problem > involve sse2 AFIK, but world/kernel should not cause this? > > Some pointers please on how to debug and I'll get to it... As a rule, if you are having any compilation problem involving ccache, the first step is always to disable ccache, and see if the problem(s) go away. If so, the issue is with ccache, otherwise it is something else. That said, which ports are failing, in particular? -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
Re: several ports: clang include errors on 12
Hi I was just about to post confirming ccache is not an issue; fails at same point. Modifying ~jail/etc/libmap.conf (and re-snapshot) did not help either. > That said, which ports are failing, in particular? too many for complete list, but includes llvm37, qt5-qmake, openjpeg15, openjpeg, OpenEXR, ghostscript9-agpl-base Sample fail log (OpenEXR): libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../config -I.. -I../config -pthread -I/usr/local/include/OpenEXR -I. -I../IlmImf -pipe -O2 -pipe -fstack-protector -fno-strict-aliasing -MT ImfDwaCompressor.lo -MD -MP -MF .deps/ImfDwaCompressor.Tpo -c ImfDwaCompressor.cpp -fPIC -DPIC -o .libs/ImfDwaCompressor.o In file included from ImfDwaCompressor.cpp:131: In file included from ./ImfDwaCompressorSimd.h:47: ./ImfSimd.h:54:14: fatal error: 'emmintrin.h' file not found #include Regards -- FreeBSD_amd64_12 Please CC my email when responding, mail from list is not delivered. ___ 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: several ports: clang include errors on 12
I just got another strange error: poudriere built emulators/linux_base-c6 when ı have in poudriere.d/make.conf DEFAULT_VERSIONS+= linux=c I cloned ports as: git clone --depth 1 --branch master https://github.com/freebsd/freebsd-ports I'd guess that's where the problem is. Should I have chosen "--branch svn-head"? -- FreeBSD_amd64_12 Please CC my email when responding, mail from list is not delivered. ___ 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: several ports: clang include errors on 12
On 10/01/2017 19:23, Beeblebrox via freebsd-ports wrote: > Hi > > I was just about to post confirming ccache is not an issue; fails at same > point. > Modifying ~jail/etc/libmap.conf (and re-snapshot) did not help either. > >> That said, which ports are failing, in particular? > too many for complete list, but includes > llvm37, qt5-qmake, openjpeg15, openjpeg, OpenEXR, ghostscript9-agpl-base > Sample fail log (OpenEXR): > libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../config -I.. -I../config > -pthread -I/usr/local/include/OpenEXR -I. -I../IlmImf -pipe -O2 -pipe > -fstack-protector -fno-strict-aliasing -MT ImfDwaCompressor.lo -MD -MP -MF > .deps/ImfDwaCompressor.Tpo -c ImfDwaCompressor.cpp -fPIC -DPIC -o > .libs/ImfDwaCompressor.o > In file included from ImfDwaCompressor.cpp:131: > In file included from ./ImfDwaCompressorSimd.h:47: > ./ImfSimd.h:54:14: fatal error: 'emmintrin.h' file not found > #include Hi, What does pkg check -s say? -- J. ___ 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"
Ports on 10.3 upgrade (was Re: portsnap temporary files)
On Sat, 7 Jan 2017, RW via freebsd-ports wrote: > If you mean files under /var/db/portsnap/files/ then these are not > temporary files, they are the compressed snapshot, and you should not > delete them without very good reason. They are supposed to persist and > may remain unmodified for many months. Yeah, so I quickly learned... Won't do it again :-) BTW, upgrading to 10.3 was seamless; it was so easy that I could've sworn something was wrong, in fact :-) Kudos to the 10.3 team. Wish I could say the same thing about ports, though; the guide blithely states "rebuild all third-party applications (e.g. ports installed from the ports tree)" without giving any hints, thus my system is now 10.3 kernel + userland, with mostly 9.3 applications such as Alpine. Speaking of Alpine, it now wants OpenSSL >= 1.0.1c; I have 1.0.2j installed, yet it still whinges. I've emailed the maintainer, but I had to use my Gmail account (since Alpine was now broken). I've since restored the required 9.3 libraries to get the thing to work. Now to see why my nameserver is partly broken... -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: several ports: clang include errors on 12
Sorry for the noise, linux-c7-* builds as expected. devel/linux-c6-devtools & devel/linux-c6-libgfortran (I assume) were built as part of a number of normally dependent ports. Nothing out of the ordinary there -- FreeBSD_amd64_12 Please CC my email when responding, mail from list is not delivered. ___ 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: openldap-client vs openldap-sasl-client (Miroslav Lachman)
> Jan Bramkamp wrote on 2017/01/05 11:30: > > On 04/01/2017 18:32, Andriy Gapon wrote: > >> > >> Do you I understand correctly that it is impossible now to install > >> both samba44 > >> and libreoffice using the official FreeBSD package repository? > >> Or samba44 and KDE? > >> > >> If yes, then that sucks... > > > > Yes and yes it sucks. The "solution" is to build your own repo and set > > the right flags to always use the same LDAP client port. With binary > > packages and the speed of modern x86_64 systems I for one no longer see > > removing SASL support from OpenLDAP as useful enough to justify the > > complexity. Are there any reasons other than saved build time to disable > > this dependency (e.g. a bad security track record/process, different > > licenses)? > > And what is the right way to choose SASL / NON-SASL version globaly? > We are building packages in our poudriere, but I cannot find the proper > variable / option for this. > > Miroslav Lachman (sorry for losing the headers, I had to copy/paste this as I switched from digest to individual). Is there a satisfactory answer to Miroslav's question? I'm in the same predicament, I can't upgrade anything without removing libreoffice, presumably because of samba. I've tried looking through the tree of options for libreoffice and samba, but I'm at a loss. ___ 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"
[CFD] changes to Handbook chapter on Ports
Executive summary: the chapter needed help, and still needs more. Full explanation: I have submitted https://reviews.freebsd.org/D9124 to add a section about ports-mgmt/synth, and a compare-and-contrast table for it and poudriere, portupgrade, and portmaster. I fully expect this section to be controversial. My aim is twofold: - try to make our documentation as useful for our users as possible (while still trying to be succinct) - try to meet the objections that have arisen about its favorable treatment of portupgrade and portmaster. I don't think the Handbook is the place for a full discussion of the controversy around these tools (see "succinct"). I'll leave the judgement about whether that should be a wiki entry, or a new Article, to someone else. When I started working on this task, I found that the whole chapter was stale and sometimes awkward. I submitted changes to Phabricator as: https://reviews.freebsd.org/D8838 https://reviews.freebsd.org/D8839 which now correspond, respectively, to: https://svnweb.freebsd.org/doc?view=revision&revision=49827 https://svnweb.freebsd.org/doc?view=revision&revision=49828 Although the reviews were made public, only my doc mentor (wblock) commented. A followup commit: https://svnweb.freebsd.org/doc?view=revision&revision=49829 was only reviewed between he and I. I am somewhat hopeful that the above commits will invite minimum controversy. However, I am reasonably confident that D9124 will. And now I'll sit back and await feedback. References: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214679 mcl ___ 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"
FreeBSD Port: mail/phpmailer2
___ 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: openldap-client vs openldap-sasl-client (Miroslav Lachman)
Lee Brown wrote on 2017/01/11 00:31: Jan Bramkamp wrote on 2017/01/05 11:30: On 04/01/2017 18:32, Andriy Gapon wrote: Do you I understand correctly that it is impossible now to install both samba44 and libreoffice using the official FreeBSD package repository? Or samba44 and KDE? If yes, then that sucks... Yes and yes it sucks. The "solution" is to build your own repo and set the right flags to always use the same LDAP client port. With binary packages and the speed of modern x86_64 systems I for one no longer see removing SASL support from OpenLDAP as useful enough to justify the complexity. Are there any reasons other than saved build time to disable this dependency (e.g. a bad security track record/process, different licenses)? And what is the right way to choose SASL / NON-SASL version globaly? We are building packages in our poudriere, but I cannot find the proper variable / option for this. Miroslav Lachman (sorry for losing the headers, I had to copy/paste this as I switched from digest to individual). Is there a satisfactory answer to Miroslav's question? I'm in the same predicament, I can't upgrade anything without removing libreoffice, presumably because of samba. I've tried looking through the tree of options for libreoffice and samba, but I'm at a loss. It should be fixed now in the ports tree. I don't know when new packages will be available for pkg install / pkg upgrade. https://svnweb.freebsd.org/ports?view=revision&revision=431079 Miroslav Lachman ___ 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: openldap-client vs openldap-sasl-client (Miroslav Lachman)
On Tue, Jan 10, 2017 at 5:27 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > Lee Brown wrote on 2017/01/11 00:31: >>> >>> Jan Bramkamp wrote on 2017/01/05 11:30: On 04/01/2017 18:32, Andriy Gapon wrote: > > > Do you I understand correctly that it is impossible now to install > both samba44 > and libreoffice using the official FreeBSD package repository? > Or samba44 and KDE? > > If yes, then that sucks... Yes and yes it sucks. The "solution" is to build your own repo and set the right flags to always use the same LDAP client port. With binary packages and the speed of modern x86_64 systems I for one no longer see removing SASL support from OpenLDAP as useful enough to justify the complexity. Are there any reasons other than saved build time to disable this dependency (e.g. a bad security track record/process, different licenses)? >>> >>> >>> And what is the right way to choose SASL / NON-SASL version globaly? >>> We are building packages in our poudriere, but I cannot find the proper >>> variable / option for this. >>> >>> Miroslav Lachman >> >> (sorry for losing the headers, I had to copy/paste this as I switched >> from digest to individual). >> >> Is there a satisfactory answer to Miroslav's question? >> >> I'm in the same predicament, I can't upgrade anything without removing >> libreoffice, presumably because of samba. >> I've tried looking through the tree of options for libreoffice and >> samba, but I'm at a loss. > > > It should be fixed now in the ports tree. I don't know when new packages > will be available for pkg install / pkg upgrade. > > https://svnweb.freebsd.org/ports?view=revision&revision=431079 > > Miroslav Lachman > Oh awesome, that should be ready for me tomorrow morning then (I build by own too). Thank you -- lee ___ 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"
libstdc++
Sigh... Will I ever get ports going under 10.3? I want to install "aspell", and it wants "libstdc++.so.6". All I can find under ports is /usr/ports/lang/libstdc++_stldoc_4.2.2, which seems to be documentation only. Is the port for the library itself available, to make "aspell" happy? Or is it one of those silly GNU things are aren't allowed to be distributed under another licence? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ 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: libstdc++
> On 10 Jan, 2017, at 19:56, Dave Horsfall wrote: > > Sigh... Will I ever get ports going under 10.3? > > I want to install "aspell", and it wants "libstdc++.so.6". All I can find > under ports is /usr/ports/lang/libstdc++_stldoc_4.2.2, which seems to be > documentation only. Is the port for the library itself available, to make > "aspell" happy? Or is it one of those silly GNU things are aren't allowed > to be distributed under another licence? You said in a prior message that you'd put 9.x libraries into your system. That's quite far from being a supported operation and it will lead to failures. Assuming that you have installed everything from packages, you can upgrade and reinstall all of them with "pkg upgrade -f". Remove all those 9.x libraries that you installed and run that command. If you're getting packages with the wrong ABI, have you changed anything in /etc/pkg/ or /usr/local/etc/pkg/? # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.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"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ net/yaz | 5.19.0 | 5.20.0 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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"
