/net-p2p/qbittorrent-nox11 PORT segmentation fault qbittorrent-nox
Hi, I filled a bug here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203081 because net-p2p/qbittorrent-nox11 does not works after upgrade to v3.2.3. I upgraded net-p2p/libtorrent-rasterbar to v1.0.6 too. I encounter an issue when starting qbittorrent-nox: --- Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.2.3 stack trace: segmentation fault qbittorrent-nox --- # uname -a FreeBSD sd-44877.local 10.2-RELEASE FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 -- Thank you for your support. Kind regards. Alexandre ___ 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: Anyone got RethinkDB working in FreeBSD?
Hello! On Sun, Sep 13, 2015 at 10:21:59PM +0200, Kurt Jaeger wrote: > Hi! > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203043 > > > I tried your file, but didn't get very far unfortunately. > > The newest version v4 of the shar builds on FreeBSD 11 (Current), amd64. > > It still needs more testing, especially under poudriere. > > -- > p...@opsec.eu+49 171 3101372 5 years to > go ! Thanks for your great work at this! Unfortunately I'm still not getting very far in FreeBSD 9.3. I added CXX in your Makefile, to get clang instead of gcc, like this: $ diff Makefile.orig Makefile 30c30 < ./configure --with-system-malloc --- > ./configure --with-system-malloc CXX=clang++ Then I got this error in configure: " * Detecting system configuration Bash: 4.3.42(0)-release Use ccache: no C++ Compiler: CLANG 3.4.1 (clang++) Host System:x86_64-unknown-freebsd9.3 Build System: FreeBSD 9.3-RELEASE-p24 amd64 Cross-compiling:no Host Operating System: FreeBSD Build Architecture: amd64 stdlib: -lstdc++ C++11: no * Error: C++11 not found. In file included from ./mk/gen/check_cxx11.cc:4: In file included from /usr/include/c++/4.2/map:65: In file included from /usr/include/c++/4.2/bits/stl_tree.h:69: In file included from /usr/include/c++/4.2/bits/stl_algobase.h:71: /usr/include/c++/4.2/bits/stl_pair.h:85:21: error: call to deleted constructor of 'C' * Aborting configure *** [do-configure] Error code 1 " I also tried setting CXX to just clang, but got the same error. So I ran portmaster devel/libc++ and got this result: ===>>> The following actions were performed: Installation of devel/libcxxrt (libcxxrt-20131225_2) Installation of devel/libc++ (libc++-208080) But I still get the same "Error: C++11 not found". I'm sorry that I'm not getting any further, I haven't used the clang environment anything before this. Thanks anyway for all help! Peter ___ 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 +-+ mail/pear-Mail_Mime | 1.9.0 | 1.10.0 +-+ x11-toolkits/irrlicht | 1.8.1 | 1.8.3 +-+ x11-wm/jwm | 2.3.1 | 2.3.2 +-+ 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"
FreeBSD Port: haproxy-devel-1.6.d4
Hi Demon,
Haproxy-1.6-dev5 became available today upstream, but a patch for
FreeBSD is 'missing' from that release.
When you make it available for FreeBSD, could you please include the
patch from the mail referenced below [1] ?
[1] http://marc.info/?l=haproxy&m=144162204927452&w=2
Thanks,
PiBa-NL
diff --git a/src/dns.c b/src/dns.c
index 4bc5448..f725ff4 100644
--- a/src/dns.c
+++ b/src/dns.c
@@ -819,7 +819,7 @@ int dns_init_resolvers(void)
}
/* "connect" the UDP socket to the name server IP */
- if (connect(fd, (struct
sockaddr*)&curnameserver->addr, sizeof(curnameserver->addr)) == -1) {
+ if (connect(fd, (struct
sockaddr*)&curnameserver->addr, get_addr_len(&curnameserver->addr)) == -1) {
Alert("Starting [%s/%s] nameserver:
can't connect socket.\n", curr_resolvers->id,
curnameserver->id);
close(fd);
___
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: FreeBSD Port: haproxy-devel-1.6.d4
> On 14 сент. 2015 г., at 15:38, P.Baauw wrote:
>
> Hi Demon,
>
> Haproxy-1.6-dev5 became available today upstream, but a patch for FreeBSD is
> 'missing' from that release.
>
> When you make it available for FreeBSD, could you please include the patch
> from the mail referenced below [1] ?
>
> [1] http://marc.info/?l=haproxy&m=144162204927452&w=2
Done.
>
> Thanks,
> PiBa-NL
>
> diff --git a/src/dns.c b/src/dns.c
> index 4bc5448..f725ff4 100644
> --- a/src/dns.c
> +++ b/src/dns.c
> @@ -819,7 +819,7 @@ int dns_init_resolvers(void)
>}
>
>/* "connect" the UDP socket to the name server IP */
> - if (connect(fd, (struct
> sockaddr*)&curnameserver->addr, sizeof(curnameserver->addr)) == -1) {
> + if (connect(fd, (struct
> sockaddr*)&curnameserver->addr, get_addr_len(&curnameserver->addr)) == -1) {
>Alert("Starting [%s/%s] nameserver:
> can't connect socket.\n", curr_resolvers->id,
>curnameserver->id);
>close(fd);
>
>
___
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: samba42-4.2.3_1
Hi Timur, Can you upgrade samba ports please? Again a lot of fixes. Thanks, Dutchman ___ 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"
Error Building devel/cmake
Stuck with an error while building devel/cmake from ports. It always stops at : None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) [100%] Built target documentation ===> Staging for cmake-3.3.1 ===> Generating temporary packing list [ 8%] Built target cmsys [ 11%] Built target cmsys_c [ 11%] Built target cmcompress [ 61%] Built target CMakeLib [ 69%] Built target CPackLib [ 89%] Built target CTestLib [ 95%] Built target ccmake [ 97%] Built target cmake [ 98%] Built target cpack [ 99%] Built target ctest [100%] sphinx-build man: see Utilities/Sphinx/build-man.log /usr/ports/devel/cmake/work/cmake-3.3.1/Help/index.rst:16: WARNING: toctree contains reference to nonexisting document u'manual/cmake-gui.1' None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) None:None: WARNING: cmake:manual reference target not found: cmake-gui(1) [100%] Built target documentation Installing the project stripped... *** Signal 11 Stop. make[2]: stopped in /usr/ports/devel/cmake/work/cmake-3.3.1 *** Error code 1 Stop. make[1]: stopped in /usr/ports/devel/cmake *** Error code 1 Stop. make: stopped in /usr/ports/devel/cmake ===>>> make stage failed for devel/cmake ===>>> Aborting update ===>>> You can restart from the point of failure with this command line: portmaster devel/cmake devel/cmake-modules It was suggested in the freebsd forum that an issue in py27-sphinx was causing the problem. I rebuilt that as well but same error. I also tried make rmconfig. No luck. I am using 10.1 RELEASE: FreeBSD unixmaster 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 22:51:51 UTC 2014 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386 Any help is welcome. ___ 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: rc script problem - pidfile not being recognised
On Sat, 12 Sep 2015 08:02:11 -0700 (PDT) Roger Marquis wrote: > RW via freebsd-ports wrote: > > You'd rather an rc script fails at run-time and shuts down the wrong > > daemon than fail when the script is being developed? > > It's not so much where the script fails than that it fails in the > first place. Neither a pidfile nor a command_interpreter needs to be > required for an rc scripts to work. These are nice features but > making them mandatory is at best a sort of premature optimization. It's not mandatory; you only need to define it if you want to be able to stop an interpreted daemon using the default method. If you have some other way of shutting down a daemon without knowing its name and PID then you can just supply a stop function to do it. > The freebsd rc script environment is already far too OS-specific and > un-editable, often containing no readable shell code at all. That's not been my experience. Occasionally it might a bit harder to customise the script, but that's outweighed by all the times an override can be made cleanly in rc.conf, without having to modify an installed script. I've found that practically all customizations can be done through rc.conf, and the rest usually involve editing an existing stop/start function. And rcng make it easy to keep multiple copies of the same rc file, you can keep separate config and switch between them from rc.conf. > What if > your interpreter changes from say python2.7 to python for example? > Does that mean you have to reinstall all the associated packages or > edit their rc scripts? If the interpreter changes from python2.7 to python, you'd have to change the shebangs anyway. ___ 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"
Really? Port conflicting with itself?
> Compressing man pages (compress-man) > Running Q/A tests (stage-qa) ===> Installing for perl5-5.16.3_23 ===> Checking if perl5 already installed ===> Registering installation for perl5-5.16.3_23 as automatic Installing perl5-5.16.3_23... pkg-static: perl5-5.16.3_23 conflicts with perl5.16-5.16.3_23 (installs files into the same place). Problematic file: /usr/local/share/licenses/perl5-5.16.3_23/catalog.mk *** Error code 70 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: l...@lerctr.org US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961 ___ 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: Really? Port conflicting with itself?
On Mon, Sep 14, 2015 at 01:20:11PM -0500, Larry Rosenman wrote: > > Compressing man pages (compress-man) > > Running Q/A tests (stage-qa) > ===> Installing for perl5-5.16.3_23 > ===> Checking if perl5 already installed > ===> Registering installation for perl5-5.16.3_23 as automatic > Installing perl5-5.16.3_23... > pkg-static: perl5-5.16.3_23 conflicts with perl5.16-5.16.3_23 (installs > files into the same place). Problematic file: > /usr/local/share/licenses/perl5-5.16.3_23/catalog.mk > *** Error code 70 They are not the same port: not perl5 vs perl5.16 you probably haven't read UPDATING. Best regards, Bapt pgpwd1aOW8cg5.pgp Description: PGP signature
Re: Error Building devel/cmake
Hallo !
If you not want to install cmake-gui, comment out line 63 in the Makefile:
63 #${RM} ${WRKSRC}/Help/manual/cmake-gui.1.rst
(But now you can't install cmake-gui this will conflicting the manpage).
Or you compile it with options DOCS and MANPAGES set to off.
greetings
Walter Schwarzenfeld
___
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: Error Building devel/cmake
On 14.09.2015 20:27, Walter Schwarzenfeld wrote:
Hallo !
If you not want to install cmake-gui, comment out line 63 in the
Makefile:
63 #${RM} ${WRKSRC}/Help/manual/cmake-gui.1.rst
(But now you can't install cmake-gui this will conflicting the manpage).
Or you compile it with options DOCS and MANPAGES set to off.
greetings
Walter Schwarzenfeld
___
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"
If you not want to install cmake-gui, comment out line 63 in the Makefile:
63 #${RM} ${WRKSRC}/Help/manual/cmake-gui.1.rst
(But now you can't install cmake-gui this will conflicting the manpage).
Or you compile it with options DOCS and MANPAGES set to off.
___
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: Error Building devel/cmake
Amit Sengupta writes: > [100%] Built target documentation > Installing the project stripped... > *** Signal 11 Something has crashed, but it's not clear what. Can you add --verbose to CONFIGURE_ARGS in devel/cmake/Makefile and rebuild? Do you get any core dumps with this crash? ___ 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"
Please make Bug#201540 (tor update to 0.2.6.10 with maintainer timeout) a priority because it fixes the broken 0.2.6.9
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201540 See this for reference: https://trac.torproject.org/projects/tor/ticket/17059 Yuri ___ 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"
Odd pkg upgrade behaviour with gdk-pixbuf2
Upon attempting to pkg upgrade chromium I saw that it wanted to install the deprecated ghostscript9-nox11 (ref: ports/UPDATING 20150822). Investigation showed that the ghostscript "dependency" was stemming from upgrading of gdk-pixbuf2. I then proceeded to allow pkg upgrade to follow its own trajectory, with multiple (failed) attempts to upgrade the chromium/gdk-pixbuf2 ports; on each iteration it worked its way through various ghostscript packages until it (the "phantom" ghostscript dependency) was finally resolved out: # pkg upgrade chromium Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ghostscript9-nox11: 9.06_11 Installed packages to be UPGRADED: chromium: 44.0.2403.155 -> 45.0.2454.85 gdk-pixbuf2: 2.31.6 -> 2.31.7 The process will require 41 MiB more space. 48 MiB to be downloaded. Proceed with this action? [y/N]: y Fetching chromium-45.0.2454.85.txz: 100% 37 MiB 363.6kB/s01:47 Fetching gdk-pixbuf2-2.31.7.txz: 100% 483 KiB 495.0kB/s00:01 Fetching ghostscript9-nox11-9.06_11.txz: 100% 11 MiB 364.2kB/s 00:31 Checking integrity... done (1 conflicting) Checking integrity... done (0 conflicting) Conflicts with the existing packages have been found. One more solver iteration is needed to resolve them. The following 3 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ghostscript9-agpl-nox11: 9.15_2 Installed packages to be UPGRADED: gdk-pixbuf2: 2.31.6 -> 2.31.7 chromium: 44.0.2403.155 -> 45.0.2454.85 The process will require 48 MiB more space. 11 MiB to be downloaded. Proceed with this action? [y/N]: y Fetching ghostscript9-agpl-nox11-9.15_2.txz: 100% 11 MiB 366.0kB/s 00:32 [1/3] Upgrading gdk-pixbuf2 from 2.31.6 to 2.31.7... [1/3] Extracting gdk-pixbuf2-2.31.7: 100% [2/3] Upgrading chromium from 44.0.2403.155 to 45.0.2454.85... [2/3] Extracting chromium-45.0.2454.85: 100% [3/3] Installing ghostscript9-agpl-nox11-9.15_2... pkg: ghostscript9-agpl-nox11-9.15_2 conflicts with ghostscript9-base -9.06_11 (installs files into the same place). Problematic file: /usr/local/bin/dvipdf # pkg upgrade gdk-pixbuf2 Updating FreeBSD repository catalogue... FreeBSD repository is up-to-date. All repositories are up-to-date. Checking integrity... done (1 conflicting) Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ghostscript9-agpl: 9.15_2 Installed packages to be UPGRADED: gdk-pixbuf2: 2.31.6 -> 2.31.7 The process will require 46 MiB more space. 11 MiB to be downloaded. Proceed with this action? [y/N]: y Fetching ghostscript9-agpl-9.15_2.txz: 100% 11 MiB 356.3kB/s00:33 [1/2] Upgrading gdk-pixbuf2 from 2.31.6 to 2.31.7... pkg: unlinkat(usr/local/lib/libgdk_pixbuf-2.0.so.0.3100.6): No such file or directory pkg: unlinkat(usr/local/lib/libgdk_pixbuf_xlib-2.0.so.0.3100.6): No such file or directory pkg: unlinkat(usr/local/share/licenses/gdk-pixbuf2-2.31.6/LGPL20): No such file or directory pkg: unlinkat(usr/local/share/licenses/gdk-pixbuf2-2.31.6/LICENSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/gdk-pixbuf2-2.31.6/catalog.mk): No such file or directory [1/2] Extracting gdk-pixbuf2-2.31.7: 100% [2/2] Installing ghostscript9-agpl-9.15_2... pkg: ghostscript9-agpl-9.15_2 conflicts with ghostscript9-base-9.06_11 (installs files into the same place). Problematic file: /usr/local/bin/dvipdf # pkg upgrade gdk-pixbuf2 Updating FreeBSD repository catalogue... Fetching meta.txz: 100%944 B 0.9kB/s00:01 Fetching packagesite.txz: 100%5 MiB 337.1kB/s00:16 Processing entries: 100% FreeBSD repository update completed. 24278 packages processed. Checking integrity... done (1 conflicting) Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): New packages to be INSTALLED: ghostscript9: 9.06_11 Installed packages to be UPGRADED: gdk-pixbuf2: 2.31.6 -> 2.31.7 The process will require 39 MiB more space. 11 MiB to be downloaded. Proceed with this action? [y/N]: y Fetching ghostscript9-9.06_11.txz: 100% 11 MiB 365.2kB/s00:31 [1/2] Upgrading gdk-pixbuf2 from 2.31.6 to 2.31.7... pkg: unlinkat(usr/local/lib/libgdk_pixbuf-2.0.so.0.3100.6): No such file or directory pkg: unlinkat(usr/local/lib/libgdk_pixbuf_xlib-2.0.so.0.3100.6): No such file or directory pkg: unlinkat(usr/local/share/licenses/gdk-pixbuf2-2.31.6/LGPL20): No such file or directory pkg: unlinkat(usr/local/share/licenses/gdk-pixbuf2-2.31.6/LICENSE): No such file or directory pkg: unlinkat(usr/local/share/licenses/gdk-pixbuf2-2.31.6/catalog.mk): No such file or directory [1/2] Extracting gdk-pixbuf2-2.31.7: 100% [2/2] Installing ghostscript9-9.06_11... pkg: ghostscript9-9.06_11 c
Re: rc script problem - pidfile not being recognised
On 2015-09-14 13:32, RW via freebsd-ports wrote: On Sat, 12 Sep 2015 08:02:11 -0700 (PDT) Roger Marquis wrote: RW via freebsd-ports wrote: > You'd rather an rc script fails at run-time and shuts down the wrong > daemon than fail when the script is being developed? It's not so much where the script fails than that it fails in the first place. Neither a pidfile nor a command_interpreter needs to be required for an rc scripts to work. These are nice features but making them mandatory is at best a sort of premature optimization. It's not mandatory; you only need to define it if you want to be able to stop an interpreted daemon using the default method. If you have some other way of shutting down a daemon without knowing its name and PID then you can just supply a stop function to do it. One easy fix would be to have stoprc first check the entire process command and then shift it by one and check again... Then it would work for both binaries and scripts without a special variable for scripts. Jim Trigg ___ 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"
using openssl from ports with database/mysql56-server
Alex,
There are advantages to using openssl with mysql (such as newer crypto
algorithms which perform better relative to strength) rather than the
default yassl.
To do so I made a patch to the Makefile in mysql56-server and added a
patch file as files/patch-cmake_ssl.cmake to fix a bug in the file
cmake/ssl.cmake.
The Makefile changes allows four options, SSL_NONE, SSL_BUILTIN,
SSL_OPENSSL_BASE, and SSL_OPENSSL_PORT. SSL_OPENSSL_BASE does not
work at the moment so maybe it could be left out for now or included
with a BROKEN statement added until it works. SSL_OPENSSL_PORT works
fine. The default is SSL_BUILTIN, which keeps things as they were,
using the builtin yassl instead of openssl.
btw- Maybe change the literal /usr/local to ${LOCALBASE} in the first
file. The change to ssl.cmake should be passed upstream as a mysql
bug. The bug is ssl.cmake always picks /usr/* rather than
/usr/local/* even if you specify -DWITH_SSL=/usr/local if openssl is
installed in both placed (FreeBSD base and ports both installed).
There are two files below separate with lines that start with "-"
(at least 5 dashes) so this should email fine and split fine. There
is one long line in the first patch file that might suffer a hostile
line break by some RFC822 pedantic mail agent.
Would you please as the maintainer of database/mysql56-server (or
someone) consider taking this change. TIA.
Curtis
-- patch for database/mysql56-server/Makefile --
--- Makefile.orig 2015-09-14 02:12:36.0 -0400
+++ Makefile2015-09-14 23:26:30.361375000 -0400
@@ -14,6 +14,18 @@
SLAVEDIRS= databases/mysql56-client
USES= cmake shebangfix
+NO_OPTIONS_SORT=yes
+
+OPTIONS_SINGLE=SSL_TYPE
+OPTIONS_SINGLE_SSL_TYPE= SSL_NONE SSL_BUILTIN \
+ SSL_OPENSSL_BASE SSL_OPENSSL_PORT
+OPTIONS_DEFAULT= SSL_BUILTIN
+
+SSL_NONE_DESC= No SSL (not recommended)
+SSL_BUILTIN_DESC= Built in SSL (uses yassl)
+SSL_OPENSSL_BASE_DESC= OpenSSL from FreeBSD base
+SSL_OPENSSL_PORT_DESC= OpenSSL from ports
+
CMAKE_ARGS+= -DINSTALL_DOCDIR="share/doc/mysql" \
-DINSTALL_DOCREADMEDIR="share/doc/mysql" \
-DINSTALL_INCLUDEDIR="include/mysql" \
@@ -34,6 +46,23 @@
SHEBANG_FILES= scripts/*.pl* scripts/*.sh
+.include
+
+# as of 5.6 the cmake default is "bundled"
+.if ${PORT_OPTIONS:MSSL_NONE}
+CMAKE_ARGS+= -DWITH_SSL=none
+.endif
+.if ${PORT_OPTIONS:MSSL_OPENSSL_BASE}
+CMAKE_ARGS+= -DWITH_SSL=/usr
+WITH_OPENSSL_BASE= yes
+USE_OPENSSL= yes
+.endif
+.if ${PORT_OPTIONS:MSSL_OPENSSL_PORT}
+CMAKE_ARGS+= -DWITH_SSL=${LOCALBASE}
+WITH_OPENSSL_PORT= yes
+USE_OPENSSL= yes
+.endif
+
.ifdef USE_MYSQL
.error You have `USE_MYSQL' variable defined either in environment or in
make(1) arguments. Please undefine and try again.
.endif
- database/mysql56-server/files/patch-cmake_ssl.cmake -
--- cmake/ssl.cmake.orig2015-07-14 17:34:24.0 -0400
+++ cmake/ssl.cmake 2015-09-15 01:17:07.433582000 -0400
@@ -123,15 +123,24 @@
# First search in WITH_SSL_PATH.
FIND_PATH(OPENSSL_ROOT_DIR
NAMES include/openssl/ssl.h
- NO_CMAKE_PATH
- NO_CMAKE_ENVIRONMENT_PATH
HINTS ${WITH_SSL_PATH}
+ NO_CMAKE_PATH NO_CMAKE_ENVIRONMENT_PATH
+ NO_SYSTEM_ENVIRONMENT_PATH NO_CMAKE_SYSTEM_PATH
)
# Then search in standard places (if not found above).
FIND_PATH(OPENSSL_ROOT_DIR
NAMES include/openssl/ssl.h
)
+MESSAGE(STATUS "WITH_SSL_PATH = ${WITH_SSL_PATH}")
+MESSAGE(STATUS "OPENSSL_ROOT_DIR = ${OPENSSL_ROOT_DIR}")
+
+FIND_PATH(OPENSSL_INCLUDE_DIR
+ NAMES openssl/ssl.h
+ HINTS ${OPENSSL_ROOT_DIR}/include
+ NO_CMAKE_PATH NO_CMAKE_ENVIRONMENT_PATH
+ NO_SYSTEM_ENVIRONMENT_PATH NO_CMAKE_SYSTEM_PATH
+)
FIND_PATH(OPENSSL_INCLUDE_DIR
NAMES openssl/ssl.h
HINTS ${OPENSSL_ROOT_DIR}/include
@@ -153,6 +162,18 @@
ENDIF()
FIND_LIBRARY(OPENSSL_LIBRARY
NAMES ssl ssleay32 ssleay32MD
+ HINTS ${OPENSSL_ROOT_DIR}/lib
+NO_CMAKE_PATH NO_CMAKE_ENVIRONMENT_PATH
+NO_SYSTEM_ENVIRONMENT_PATH NO_CMAKE_SYSTEM_PATH
+)
+FIND_LIBRARY(CRYPTO_LIBRARY
+ NAMES crypto libeay32
+ HINTS ${OPENSSL_ROOT_DIR}/lib
+NO_CMAKE_PATH NO_CMAKE_ENVIRONMENT_PATH
+NO_SYSTEM_ENVIRONMENT_PATH NO_CMAKE_SYSTEM_PATH
+)
+FIND_LIBRARY(OPENSSL_LIBRARY
+ NAMES ssl ssleay32 ssleay32MD
HINTS ${OPENSSL_ROOT_DIR}/lib)
FIND_LIBRARY(CRYPTO_LIBRARY
NAMES crypto libeay32
- END -
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To u
Re: Really? Port conflicting with itself?
+--On 14 septembre 2015 13:20:11 -0500 Larry Rosenman wrote: | > Compressing man pages (compress-man) | > Running Q/A tests (stage-qa) | ===> Installing for perl5-5.16.3_23 | ===> Checking if perl5 already installed | ===> Registering installation for perl5-5.16.3_23 as automatic | Installing perl5-5.16.3_23... | pkg-static: perl5-5.16.3_23 conflicts with perl5.16-5.16.3_23 (installs | files into the same place). Problematic file: | /usr/local/share/licenses/perl5-5.16.3_23/catalog.mk | *** Error code 70 Mmmm, is that you installing a port manually ? You upgrading a Perl port with some tool ? You upgrading Perl with some tool ? -- Mathieu Arnold pgpIJsX7ffqmA.pgp Description: PGP signature
