Mk/Uses/ssl.mk and OpenSSL 1.1.x in base
Hi, FreeBSD 12 has switched to OpenSSL 1.1 in 1200085 (https://svnweb.freebsd.org/changeset/base/r339270) and there's considerable fall-out in packages as a result. The fall-out in packages should align nicely with the results of building with security/openssl-devel or security/openssl111 (see https://wiki.freebsd.org/OpenSSL/1.1.0 and https://wiki.freebsd.org/OpenSSL/1.1.1 respectively). Many ports are already marked BROKEN_SSL= openssl-devel, and openssl111 should be added to these ports as well (see https://reviews.freebsd.org/D17136) Should we extend Mk/Uses/ssl.mk to include a check for BROKEN_SSL= openssl-devel|openss111 and __FreeBSD_version >= 1200085? Cheers, Bernard. ___ 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: Compiling firefox on Raspberry Pi 2
On Sat, 20 Oct 2018 05:32:14 +0200, bob prohaska wrote: Attempts to compile firefox63 on an RPI2 fail with ===> rust-1.29.2 is only for aarch64 amd64 i386, while you are running armv6 (reason: requires prebuilt bootstrap compiler). *** Error code 1 while compilation of firefox-esr stops with dt_modtext:/usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_link.c(856): arm not implemented dtrace: failed to link script /usr/ports/www/firefox-esr/work/firefox-52.8.0esr/js/src/devtools/javascript-trace.d: an error was encountered while processing jsarray.o gmake[5]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/rules.mk:788: js-dtrace.o] Error 1 gmake[5]: Leaving directory '/usr/ports/www/firefox-esr/work/.build/js/src' gmake[4]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/recurse.mk:71: js/src/target] Error 2 gmake[4]: Leaving directory '/usr/ports/www/firefox-esr/work/.build' gmake[3]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/recurse.mk:33: compile] Error 2 gmake[3]: Leaving directory '/usr/ports/www/firefox-esr/work/.build' gmake[2]: *** [/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/rules.mk:523: all] Error 2 Can anybody suggest workaround for either problem? Not a workaround. Buy you can try to port rust to armv6. Which will benefit some other ports also. Rust has tier 2 support for linux/arm, so it might be not so hard to do. https://forge.rust-lang.org/platform-support.html For Firefox-esr, try to disable DTRACE in the build options of the port. It says it is not implemented on arm. Regards, Ronald. Thanks for reading, bob prohaska ___ 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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
looking for someone to commit 3 PRs
Hi, Could a committer look at the following 3 PRs i submitted 6 months ago? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227375 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227376 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227378 They're pretty simple updates. Thanks, Daniel. ___ 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"
INDEX build failed for 10.x
INDEX build failed with errors: Generating INDEX-10 - please wait..--- describe.accessibility --- --- describe.arabic --- --- describe.archivers --- --- describe.astro --- --- describe.audio --- --- describe.benchmarks --- --- describe.biology --- --- describe.cad --- --- describe.chinese --- --- describe.comms --- --- describe.converters --- --- describe.databases --- --- describe.deskutils --- --- describe.devel --- --- describe.dns --- --- describe.editors --- --- describe.devel --- sh: clang60: not found make[5]: "/home/indexbuild/tindex/ports/Mk/Uses/compiler.mk" line 78: warning: "clang60 --version" returned non-zero status make[5]: "/home/indexbuild/tindex/ports/Mk/Uses/compiler.mk" line 133: warning: "clang++60 -### /dev/null 2>&1" returned non-zero status [...] --- describe.print --- --- describe.russian --- --- describe.science --- --- describe.security --- --- describe.shells --- --- describe.sysutils --- --- describe.textproc --- --- describe.ukrainian --- --- describe.vietnamese --- --- describe.www --- --- describe.x11 --- --- describe.x11-clocks --- --- describe.x11-drivers --- --- describe.x11-fm --- --- describe.x11-fonts --- --- describe.x11-servers --- --- describe.x11-themes --- --- describe.x11-toolkits --- --- describe.x11-wm --- Done. make_index: /home/indexbuild/tindex/ports/www/p5-WWW-OAuth: no entry for /home/indexbuild/tindex/ports/devel/p5-Class-Tiny-Chained Committers on the hook: danilo jrm mfechner sunpoet tobik zi Most recent SVN update was: Updating '.': UMk/bsd.ruby.mk Ulang/ruby23/Makefile Ulang/ruby23/distinfo Dlang/ruby23/files/patch-lib_rdoc_generator_json_index.rb Ulang/ruby23/files/patch-configure.in Alang/ruby23/files/patch-lib_rdoc_generator_json__index.rb Ulang/ruby23/files/patch-thread__pthread.c Ulang/ruby23/pkg-plist Ulang/ruby24/Makefile Ulang/ruby24/distinfo Dlang/ruby24/files/patch-ext-openssl-extconf.rb Dlang/ruby24/files/patch-lib_rdoc_generator_json_index.rb Ulang/ruby24/files/patch-configure.in Alang/ruby24/files/patch-lib_rdoc_generator_json__index.rb Ulang/ruby24/files/patch-tool_mkconfig.rb Ulang/ruby24/pkg-plist Ulang/ruby25/Makefile Ulang/ruby25/distinfo Dlang/ruby25/files/patch-ext-openssl-extconf.rb Dlang/ruby25/files/patch-lib_rdoc_generator_json_index.rb Ulang/ruby25/files/patch-configure.ac Ulang/ruby25/files/patch-lib_mkmf.rb Alang/ruby25/files/patch-lib_rdoc_generator_json__index.rb Ulang/ruby25/files/patch-tool_mkconfig.rb Ulang/ruby25/pkg-plist Ulang/libhx/Makefile Ulang/libhx/distinfo Usecurity/vuxml/vuln.xml Usecurity/rubygem-openssl/Makefile Usecurity/rubygem-openssl/distinfo Usecurity/rubygem-googleauth/Makefile Usecurity/rubygem-googleauth/distinfo Usecurity/rubygem-googleauth/pkg-descr Usecurity/pev/Makefile Asecurity/pev/files/patch-src_pehash.c Asecurity/pev/files/patch-src_pesec.c Uwww/Makefile Awww/p5-WWW-OAuth Awww/p5-WWW-OAuth/Makefile Awww/p5-WWW-OAuth/distinfo Awww/p5-WWW-OAuth/pkg-descr Awww/p5-WWW-OAuth/pkg-plist Uwww/rubygem-jekyll-watch/Makefile Uwww/rubygem-jekyll-watch/distinfo Uwww/rubygem-rdf/Makefile Uwww/rubygem-rdf/distinfo Uwww/p5-WWW-Mechanize/Makefile Uwww/p5-WWW-Mechanize/distinfo Uwww/p5-HTTP-Body/pkg-plist Uwww/p5-Catalyst-Runtime/Makefile Uwww/p5-Catalyst-Runtime/distinfo Uwww/py-flask-migrate/Makefile Uwww/py-flask-migrate/distinfo Awww/py-biscuits Awww/py-biscuits/Makefile Awww/py-biscuits/distinfo Awww/py-biscuits/pkg-descr Udevel/p5-Class-C3-Adopt-NEXT/Makefile Udevel/rubygem-xpath/Makefile Udevel/rubygem-xpath/distinfo Udevel/rubygem-tins/Makefile Udevel/rubygem-tins/distinfo Udevel/rubygem-strong_migrations/Makefile Udevel/rubygem-strong_migrations/distinfo Udevel/rubygem-pleaserun/Makefile Udevel/rubygem-mustache/Makefile Udevel/rubygem-mustache/distinfo Udevel/rubygem-message_bus/Makefile Udevel/rubygem-message_bus/distinfo Udevel/rubygem-i18n/Makefile Udevel/rubygem-i18n/distinfo Udevel/rubygem-holidays/Makefile Udevel/rubygem-holidays/distinfo Udevel/ruby-build/Makefile Udevel/ruby-build/distinfo Udevel/py-ipyparallel/Makefile Udevel/py-ipyparallel/distinfo Udevel/nuitka/Makefile Udevel/nuitka/distinfo Udevel/p5-Sub-Exporter-ForMethods/Makefile Udevel/p5-Module-ExtractUse/Makefile Udevel/p5-Module-ExtractUse/distinfo Udevel/p5-Getopt-Long-Descriptive/Makefile Udevel/p5-Badger/Makefile Udevel/p5-Badger/distinfo Udevel/p5-Badger/pkg-plist Udevel/rubygem-tzinfo-data/Makefile Udevel/rubygem-tzinfo-data/distinfo Udevel/rubygem-tzinfo/Makefile Udevel/rubygem-tzinfo/pkg-descr Udevel/rubygem-aws-sdk/Makefile Udevel/rubygem-aws-sdk/distinfo Udevel/rubygem-aws-sdk-resources/Makefile Udevel/rubygem-aws-sdk-resources/distinfo Udev
orphaned: www/suphp
I just updated my ports tree and then proceeded to run: "pkg version -vL=" which produced this: suphp-0.7.2_2 ? orphaned: www/suphp There is nothing about this in either the UPDATING or MOVED files. Has this port actually been removed and if so, why? -- Carmel ___ 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: orphaned: www/suphp
> I just updated my ports tree and then proceeded to run: "pkg version -vL=" > which produced this: > > suphp-0.7.2_2 ? orphaned: www/suphp > > There is nothing about this in either the UPDATING or MOVED files. Has this > port actually been removed and if so, why? I have it in my port tree, which I just updated. Lorenzo Salvadore. ___ 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"
korean/man-doc: picking it up
Hi, I just noticed that tobik@ set the port [deprecated](https://svnweb.freebsd.org/ports?view=revision&revision=482496). If it's okay I'll take the maintainership and try to revamp all the translation gradually. Thank you, -- Hyun Hwang ___ 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: korean/man-doc: picking it up
On Sat, Oct 20, 2018, at 18:14, Hyun Hwang wrote: > Hi, > > I just noticed that tobik@ set the port [deprecated] > (https://svnweb.freebsd.org/ports?view=revision&revision=482496). If > it's okay I'll take the maintainership and try to revamp all the > translation gradually. > > Thank you, > -- > Hyun Hwang Sure, I just assigned the port to you. Thanks! https://svnweb.freebsd.org/changeset/ports/482588 ___ 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: korean/man-doc: picking it up
On Saturday, October 20, 2018, 6:19 PM (UTC+0200), Tobias Kortkamp wrote: > On Sat, Oct 20, 2018, at 18:14, Hyun Hwang wrote: > > Hi, > > > > I just noticed that tobik@ set the port [deprecated] > > (https://svnweb.freebsd.org/ports?view=revision&revision=482496). If > > it's okay I'll take the maintainership and try to revamp all the > > translation gradually. > > > > Thank you, > > -- > > Hyun Hwang > > Sure, I just assigned the port to you. Thanks! > > https://svnweb.freebsd.org/changeset/ports/482588 Appreciated! -- Hyun Hwang ___ 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"
INDEX now builds successfully on 10.x
___ 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: orphaned: www/suphp
On 20/10/2018 16:28, Lorenzo Salvadore via freebsd-ports wrote: >> I just updated my ports tree and then proceeded to run: "pkg version -vL=" >> which produced this: >> >> suphp-0.7.2_2 ? orphaned: www/suphp >> >> There is nothing about this in either the UPDATING or MOVED files. Has this >> port actually been removed and if so, why? > > I have it in my port tree, which I just updated. The port has been flavourized, so the name has changed. It's now something like suphp-php71-0.7.2_2 (depending on what version of PHP you have installed). If you just re-install the port, pkg(8) will sort everything out for you. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: orphaned: www/suphp
On Sat, 20 Oct 2018 19:31:52 +0100, Matthew Seaman stated: >On 20/10/2018 16:28, Lorenzo Salvadore via freebsd-ports wrote: >>> I just updated my ports tree and then proceeded to run: "pkg version -vL=" >>> which produced this: >>> >>> suphp-0.7.2_2 ? orphaned: www/suphp >>> >>> There is nothing about this in either the UPDATING or MOVED files. Has >>> this port actually been removed and if so, why? >> >> I have it in my port tree, which I just updated. > >The port has been flavourized, so the name has changed. It's now >something like > > suphp-php71-0.7.2_2 > >(depending on what version of PHP you have installed). > >If you just re-install the port, pkg(8) will sort everything out for you. > > Cheers, > > Matthew I have this in my /etc/make.conf file: DEFAULT_VERSIONS+=php=7.2 I have the same listing in my "/usr/local/poudriere/make.conf" and "/usr/local/etc/poudriere.d/make.conf" files. Never-the-less, when I used poudriere to build the www/suphp port, it insisted on installing php56 and deleting php72 as well as www/suphp. I had to reinstall php72 and then build build the www/suphp port manually, which also rebuilt the dependencies removed by poudriere. Why is poudriere ignoring the directives in the various make.conf files? -- Carmel ___ 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: [j...@freebsd.org: svn commit: r482272 - in head/emulators: virtualbox-ose virtualbox-ose-additions virtualbox-ose-additions-nox11 virtualbox-ose-kmod virtualbox-ose-nox11 virtualbox-ose/files]
В Thu, 18 Oct 2018 09:50:31 +0200 Florian Smeets via freebsd-ports пишет: > does 5.2.20 break VNC remote console to VBoxHeadless VMs for anyone > else? I can still connect to the console with VNC but all I get is a > black screen. Going back to 5.2.18 restores VNC functionality. I can confirm that. Also I have to notice, that while there is an active VNC connection to the some machine, the second connection to the same machine crashes a VirtualBox process (this applies to all versions). -- Alexander Zagrebin ___ 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: Compiling firefox on Raspberry Pi 2
On Sat, Oct 20, 2018 at 11:01:15AM +0200, Ronald Klop wrote: > > Not a workaround. Buy you can try to port rust to armv6. Which will > benefit some other ports also. > Rust has tier 2 support for linux/arm, so it might be not so hard to do. > https://forge.rust-lang.org/platform-support.html > You give me too much credit 8-), but I'll look into it. I thought there was an option somewhere to disable rust-dependent features, but I can't find it now. > For Firefox-esr, try to disable DTRACE in the build options of the port. > It says it is not implemented on arm. The default is to build without dtrace: one has to check the box to "Build with DTrace probes" which I've been leaving unchecked. Is there something else I'm missing? Thanks! bob prohaska > > > > > Thanks for reading, > > > > bob prohaska > > > > ___ > > 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@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@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: orphaned: www/suphp
On 20/10/18 21:43, Carmel NY wrote: > On Sat, 20 Oct 2018 19:31:52 +0100, Matthew Seaman stated: > >> On 20/10/2018 16:28, Lorenzo Salvadore via freebsd-ports wrote: I just updated my ports tree and then proceeded to run: "pkg version -vL=" which produced this: suphp-0.7.2_2 ? orphaned: www/suphp There is nothing about this in either the UPDATING or MOVED files. Has this port actually been removed and if so, why? >>> >>> I have it in my port tree, which I just updated. >> >> The port has been flavourized, so the name has changed. It's now >> something like >> >> suphp-php71-0.7.2_2 >> >> (depending on what version of PHP you have installed). >> >> If you just re-install the port, pkg(8) will sort everything out for you. >> >> Cheers, >> >> Matthew > > I have this in my /etc/make.conf file: > DEFAULT_VERSIONS+=php=7.2 > > I have the same listing in my "/usr/local/poudriere/make.conf" and > "/usr/local/etc/poudriere.d/make.conf" files. Never-the-less, when I used > poudriere to build the www/suphp port, it insisted on installing php56 and > deleting php72 as well as www/suphp. I had to reinstall php72 and then build > build the www/suphp port manually, which also rebuilt the dependencies > removed by poudriere. Why is poudriere ignoring the directives in the various > make.conf files? > List it in poudriere as www/suphp@php72. the part after the @ is the flavor, otherwise the default flavor is built. Although it should work with your DEFAULT_VERSIONS setup being pedantic is safer. -- Guido Falsi ___ 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"
