Re: curl and nginx no longer build on same host
On Tuesday, July 19, 2016 07:32 SGT, "Matthew D. Fuller" wrote: > On Tue, Jul 19, 2016 at 06:44:49AM +0800 I heard the voice of > Euan Thoms, and lo! it spake thus: > > > > Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know > > why I didn't try it before, perhaps since it is deprecated. > > > > So, I think we need to address some shortcoming in the new macro > > DEFAULT_VERSIONS+=ssl=openssl. > > That seems... odd. > > > DEFAULT_VERSIONS+=ssl=openssl > > will cause bsd.default-versions.mk to set the variable SSL_DEFAULT to > the value 'openssl'. > > Contrarily, > > > WITH_OPENSSL_PORT=yes > > will cause bsd.default-versions.mk to set the variable SSL_DEFAULT to > the value 'openssl' (unless you've got OPENSSL_PORT defined, in which > case it's set to whatever that is) and spit out a warning. > > So, unless you're setting OPENSSL_PORT, they're doing exactly the same > thing (modulo the warning). If you are (e.g., from using libressl > instead), you need to set THAT instead of 'openssl' in the > DEFAULT_VERSIONS line. > I'm not setting anything else in make.conf, the jail is otherwise vanilla, no hacks etc. In both cases I'm only using openssl, no libressl. I just noticed that after running make using WITH_OPENSSL_PORT=yes , it builds fine. Then turning the make.conf back to using DEFAULT_VERSIONS+=ssl=openssl instead of WITH_OPENSSL_PORT=yes, it now builds OK. So I did a "make config" and GSSAPI_NONE is now set. After further examiniation, it seems that coincidentally I must have done a "make rmconfig" before using WITH_OPENSSL_PORT=yes. The "make rmconfig" removes my /var/db/ports/ftp_curl/options and then the next time "make" is run the macros in make.conf set GSSAPI_NONE. So, the problem I had was that my existing installation (in a jail) had options set that the make.conf macros were not clobbering. If I had set those make.conf options/macros in the first place, I would not have the said problem. But, the macro did not exist when I did the initial installation, neither was replacing openssl from base a thing. Worth noting that I'm pretty sure I never changed any options in ftp/curl on the initial install (or previous updates via portmaster either). So just the fact that I hit enter on the ftp/curl ncurses options screen meant that in future, setting the openssl macros would not take the desired effect. Tricky one to solve I guess, I wouldn't want a macro clobbering my custom options config either. -- Regards, Euan Thoms ___ 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: curl and nginx no longer build on same host
On Tue, Jul 19, 2016 at 06:44:49AM +0800 I heard the voice of Euan Thoms, and lo! it spake thus: > > Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know > why I didn't try it before, perhaps since it is deprecated. > > So, I think we need to address some shortcoming in the new macro > DEFAULT_VERSIONS+=ssl=openssl. That seems... odd. > DEFAULT_VERSIONS+=ssl=openssl will cause bsd.default-versions.mk to set the variable SSL_DEFAULT to the value 'openssl'. Contrarily, > WITH_OPENSSL_PORT=yes will cause bsd.default-versions.mk to set the variable SSL_DEFAULT to the value 'openssl' (unless you've got OPENSSL_PORT defined, in which case it's set to whatever that is) and spit out a warning. So, unless you're setting OPENSSL_PORT, they're doing exactly the same thing (modulo the warning). If you are (e.g., from using libressl instead), you need to set THAT instead of 'openssl' in the DEFAULT_VERSIONS line. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ 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: curl and nginx no longer build on same host
Hello, > On Jul 18, 2016, at 6:44 PM, Euan Thoms wrote: > > >> On Tuesday, July 19, 2016 05:11 SGT, Jim Ohlstein wrote: >> >> Hello, >> >>> On Jul 18, 2016, at 4:37 PM, Euan Thoms wrote: > > >>> OK, I'm clear about the make.conf options and what they mean. But I still >>> have a problem in that even if I use DEFAULT_VERSIONS+=ssl=openssl, >>> ftp/curl will not build, certainly not with portmaster and I think I tried >>> building it manually from inside it's ports directory. >>> >>> /usr/ports/ftp/curl]# make >>> ===> curl-7.49.1 GSSAPI_BASE is not compatible with OpenSSL from ports. Use >>> other GSSAPI options or OpenSSL from base system. >>> *** Error code 1 >>> >>> Stop. >>> make: stopped in /usr/ports/ftp/curl >>> >>> >>> So basically, I'd have to change one of the GSSAPI options in ftp/curl. >>> Except I haven't got a clue on the ramifications of this. Do I need GSSAPI? >>> If so, should I use Heimdal or MIT? >>> >>> So you see my point, it's not friendly on new FreeBSD users. I'm a fairly >>> experienced FreeBSD sys-adimin and I don't know what to do in this case. >>> >>> At least I now know that there is a good reason to not have on port built >>> against base openssl and another built against ports openssl. >> >> So basically they've deprecated a useful option without replicating the >> functionality. Bravo! >> >> Fortunately, it still works as intended. > > > Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know why I > didn't try it before, perhaps since it is deprecated. > > So, I think we need to address some shortcoming in the new macro > DEFAULT_VERSIONS+=ssl=openssl. > > Perhaps I should create a new thread, with a more appropriate subject line? > Any suggestions? That's evidently above my pay grade. I recall recently there was a discussion of building all ports against the openssl port. It got lengthy and I stopped reading it. That's what that function does. Deprecating that function without forcing use of the openssl port was not wise IMMHO, but again, my opinion apparently doesn't matter. -- Jim ___ 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: curl and nginx no longer build on same host
On Tuesday, July 19, 2016 05:11 SGT, Jim Ohlstein wrote: > Hello, > > > On Jul 18, 2016, at 4:37 PM, Euan Thoms wrote: > > > > OK, I'm clear about the make.conf options and what they mean. But I still > > have a problem in that even if I use DEFAULT_VERSIONS+=ssl=openssl, > > ftp/curl will not build, certainly not with portmaster and I think I tried > > building it manually from inside it's ports directory. > > > > /usr/ports/ftp/curl]# make > > ===> curl-7.49.1 GSSAPI_BASE is not compatible with OpenSSL from ports. Use > > other GSSAPI options or OpenSSL from base system. > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/ftp/curl > > > > > > So basically, I'd have to change one of the GSSAPI options in ftp/curl. > > Except I haven't got a clue on the ramifications of this. Do I need GSSAPI? > > If so, should I use Heimdal or MIT? > > > > So you see my point, it's not friendly on new FreeBSD users. I'm a fairly > > experienced FreeBSD sys-adimin and I don't know what to do in this case. > > > > At least I now know that there is a good reason to not have on port built > > against base openssl and another built against ports openssl. > > So basically they've deprecated a useful option without replicating the > functionality. Bravo! > > Fortunately, it still works as intended. > Aha, I got ftp/curl to build using WITH_OPENSSL_PORT=yes. Don't know why I didn't try it before, perhaps since it is deprecated. So, I think we need to address some shortcoming in the new macro DEFAULT_VERSIONS+=ssl=openssl. Perhaps I should create a new thread, with a more appropriate subject line? Any suggestions? -- Regards, Euan Thoms ___ 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: curl and nginx no longer build on same host
Hello, > On Jul 18, 2016, at 4:37 PM, Euan Thoms wrote: > > >> On Tuesday, July 19, 2016 04:03 SGT, Kevin Oberman >> wrote: >> >>> On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote: >>> >>> >>> On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote: > >>> >>> OK, I understand. And I'm glad we're heading somewhere where we will have >>> more consistency. I just feel that we shouldn't need anything in >>> /etc/make.conf unless we are exerting some extra control and using > >>> non-default options. I've managed to get away without anything in >>> /etc/make.conf on all my jails, collectively they install quite a range of >>> software types. >>> >>> Are you sure that WITH_OPENSSL_PORT isn't deprecated. I got some warnings >>> to that effect. So I've been using USES+=ssl=openssl instead. Perhaps >>> that's part of the problem, maybe the ftp/curl port is still using the >>> older make.conf flag. I'll try it next time I update. >>> >>> Thanks Jim. > >> >> Yes and no. WITH_OPENSSL_PORT in make,conf has been deprecated. It should >> still work, but you should update to the new syntax. If you do use it, you >> should see the following: >> "Using WITH_OPENSSL_PORT in make.conf is deprecated, replace it with >> DEFAULT_VERSIONS+=ssl=openssl in your make.conf" >> >> To avoid conflicting SSL libraries in different ports, it is bast to put >> the "DEFAULT_VERSIONS+=ssl=openssl" in /etc/make.conf. If you use base >> OpsnSSL in some ports that create shareable libraries and the ports version >> in others, you will eventually hit an executable, possibly from a third >> port, that is linked to both and those programs will not run. > > OK, I'm clear about the make.conf options and what they mean. But I still > have a problem in that even if I use DEFAULT_VERSIONS+=ssl=openssl, ftp/curl > will not build, certainly not with portmaster and I think I tried building it > manually from inside it's ports directory. > > /usr/ports/ftp/curl]# make > ===> curl-7.49.1 GSSAPI_BASE is not compatible with OpenSSL from ports. Use > other GSSAPI options or OpenSSL from base system. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/ftp/curl > > > So basically, I'd have to change one of the GSSAPI options in ftp/curl. > Except I haven't got a clue on the ramifications of this. Do I need GSSAPI? > If so, should I use Heimdal or MIT? > > So you see my point, it's not friendly on new FreeBSD users. I'm a fairly > experienced FreeBSD sys-adimin and I don't know what to do in this case. > > At least I now know that there is a good reason to not have on port built > against base openssl and another built against ports openssl. So basically they've deprecated a useful option without replicating the functionality. Bravo! Fortunately, it still works as intended. -- Jim ___ 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: curl and nginx no longer build on same host
On Tuesday, July 19, 2016 04:03 SGT, Kevin Oberman wrote: > On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote: > > > > > On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote: > > > > OK, I understand. And I'm glad we're heading somewhere where we will have > > more consistency. I just feel that we shouldn't need anything in > > /etc/make.conf unless we are exerting some extra control and using > > non-default options. I've managed to get away without anything in > > /etc/make.conf on all my jails, collectively they install quite a range of > > software types. > > > > Are you sure that WITH_OPENSSL_PORT isn't deprecated. I got some warnings > > to that effect. So I've been using USES+=ssl=openssl instead. Perhaps > > that's part of the problem, maybe the ftp/curl port is still using the > > older make.conf flag. I'll try it next time I update. > > > > Thanks Jim. > > > > Yes and no. WITH_OPENSSL_PORT in make,conf has been deprecated. It should > still work, but you should update to the new syntax. If you do use it, you > should see the following: > "Using WITH_OPENSSL_PORT in make.conf is deprecated, replace it with > DEFAULT_VERSIONS+=ssl=openssl in your make.conf" > > To avoid conflicting SSL libraries in different ports, it is bast to put > the "DEFAULT_VERSIONS+=ssl=openssl" in /etc/make.conf. If you use base > OpsnSSL in some ports that create shareable libraries and the ports version > in others, you will eventually hit an executable, possibly from a third > port, that is linked to both and those programs will not run. OK, I'm clear about the make.conf options and what they mean. But I still have a problem in that even if I use DEFAULT_VERSIONS+=ssl=openssl, ftp/curl will not build, certainly not with portmaster and I think I tried building it manually from inside it's ports directory. /usr/ports/ftp/curl]# make ===> curl-7.49.1 GSSAPI_BASE is not compatible with OpenSSL from ports. Use other GSSAPI options or OpenSSL from base system. *** Error code 1 Stop. make: stopped in /usr/ports/ftp/curl So basically, I'd have to change one of the GSSAPI options in ftp/curl. Except I haven't got a clue on the ramifications of this. Do I need GSSAPI? If so, should I use Heimdal or MIT? So you see my point, it's not friendly on new FreeBSD users. I'm a fairly experienced FreeBSD sys-adimin and I don't know what to do in this case. At least I now know that there is a good reason to not have on port built against base openssl and another built against ports openssl. -- Regards, Euan Thoms ___ 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: curl and nginx no longer build on same host
On Mon, Jul 18, 2016 at 12:45 PM, Euan Thoms wrote: > > On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote: > > > Hello, > > > > On 7/15/16 11:41 PM, Euan Thoms wrote: > > > > > > Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with > either. The bottom line is ftp/curl with default port options does not want > to build against openssl or libressl from ports. And it doesn't want to try > and use the base openssl either. > > > > > > Your point about the port options for http2 requiring the ports > version of openssl is valid. But this happens when the default options for > both ports are used. I could accept my manual workaround if I had changed > the default port options on either of the two ports. But default port > options should build together. > > > > > > I suppose this has only come about on this upgrade cycle because nginx > port now has http2 on by default? > > > > As of version 1.10.0 it appears http2 is selected by default. It has > > been the default in www/nginx-devel for some time. it is not the default > > for ftp/curl: > > > > OPTIONS_DEFAULT=CA_BUNDLE COOKIES OPENSSL PROXY RESOLV > > THREADED_RESOLVER TLS_SRP > > > > My /etc/make.conf has the following: > > > > WITH_OPENSSL_PORT=yes > > > > That will force ftp/curl (and all ports) to build against the openssl > > port. If I understand correctly, that is about to become the default > > behavior for all ports at some time in the not so distant future, or at > > least it has been proposed. > > > > OK, I understand. And I'm glad we're heading somewhere where we will have > more consistency. I just feel that we shouldn't need anything in > /etc/make.conf unless we are exerting some extra control and using > non-default options. I've managed to get away without anything in > /etc/make.conf on all my jails, collectively they install quite a range of > software types. > > Are you sure that WITH_OPENSSL_PORT isn't deprecated. I got some warnings > to that effect. So I've been using USES+=ssl=openssl instead. Perhaps > that's part of the problem, maybe the ftp/curl port is still using the > older make.conf flag. I'll try it next time I update. > > Thanks Jim. > > -- > Regards, Euan Thoms > Yes and no. WITH_OPENSSL_PORT in make,conf has been deprecated. It should still work, but you should update to the new syntax. If you do use it, you should see the following: "Using WITH_OPENSSL_PORT in make.conf is deprecated, replace it with DEFAULT_VERSIONS+=ssl=openssl in your make.conf" To avoid conflicting SSL libraries in different ports, it is bast to put the "DEFAULT_VERSIONS+=ssl=openssl" in /etc/make.conf. If you use base OpsnSSL in some ports that create shareable libraries and the ports version in others, you will eventually hit an executable, possibly from a third port, that is linked to both and those programs will not run. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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: curl and nginx no longer build on same host
On Saturday, July 16, 2016 20:43 SGT, Jim Ohlstein wrote: > Hello, > > On 7/15/16 11:41 PM, Euan Thoms wrote: > > > > Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with > > either. The bottom line is ftp/curl with default port options does not want > > to build against openssl or libressl from ports. And it doesn't want to try > > and use the base openssl either. > > > > Your point about the port options for http2 requiring the ports version of > > openssl is valid. But this happens when the default options for both ports > > are used. I could accept my manual workaround if I had changed the default > > port options on either of the two ports. But default port options should > > build together. > > > > I suppose this has only come about on this upgrade cycle because nginx port > > now has http2 on by default? > > As of version 1.10.0 it appears http2 is selected by default. It has > been the default in www/nginx-devel for some time. it is not the default > for ftp/curl: > > OPTIONS_DEFAULT=CA_BUNDLE COOKIES OPENSSL PROXY RESOLV > THREADED_RESOLVER TLS_SRP > > My /etc/make.conf has the following: > > WITH_OPENSSL_PORT=yes > > That will force ftp/curl (and all ports) to build against the openssl > port. If I understand correctly, that is about to become the default > behavior for all ports at some time in the not so distant future, or at > least it has been proposed. > OK, I understand. And I'm glad we're heading somewhere where we will have more consistency. I just feel that we shouldn't need anything in /etc/make.conf unless we are exerting some extra control and using non-default options. I've managed to get away without anything in /etc/make.conf on all my jails, collectively they install quite a range of software types. Are you sure that WITH_OPENSSL_PORT isn't deprecated. I got some warnings to that effect. So I've been using USES+=ssl=openssl instead. Perhaps that's part of the problem, maybe the ftp/curl port is still using the older make.conf flag. I'll try it next time I update. Thanks Jim. -- Regards, Euan Thoms ___ 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: curl and nginx no longer build on same host
Hello, On 7/15/16 11:41 PM, Euan Thoms wrote: On Saturday, July 16, 2016 10:21 SGT, Jim Ohlstein wrote: Hello, On Jul 15, 2016, at 10:03 PM, Euan Thoms wrote: Bump Can anyone else install or update ftp/curl after installing nginx? Yes, but I'm building packages using poudriere, not using portmaster. Good point, it may be a portmaster issue. Next time I update, I'll try to upgrade manually... eh, how do I do that again (scratches head). The only way I'm able to update now is to uninstall openssl and nginx, then update curl, then reinstall nginx (which pulls in openssl). This was not required on several previous update cycles. If memory serves me correctly, nginx and curl both require openssl from ports only if certain options are chosen (http2 being one), or at least that was the case in the past. You may have option(s) selected for one that requires the version from ports, and one that does not. Have you tried to force usage of openssl from ports in your /etc/make.conf? Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with either. The bottom line is ftp/curl with default port options does not want to build against openssl or libressl from ports. And it doesn't want to try and use the base openssl either. Your point about the port options for http2 requiring the ports version of openssl is valid. But this happens when the default options for both ports are used. I could accept my manual workaround if I had changed the default port options on either of the two ports. But default port options should build together. I suppose this has only come about on this upgrade cycle because nginx port now has http2 on by default? As of version 1.10.0 it appears http2 is selected by default. It has been the default in www/nginx-devel for some time. it is not the default for ftp/curl: OPTIONS_DEFAULT=CA_BUNDLE COOKIES OPENSSL PROXY RESOLV THREADED_RESOLVER TLS_SRP My /etc/make.conf has the following: WITH_OPENSSL_PORT=yes That will force ftp/curl (and all ports) to build against the openssl port. If I understand correctly, that is about to become the default behavior for all ports at some time in the not so distant future, or at least it has been proposed. On Thursday, July 14, 2016 23:30 SGT, "Euan Thoms" wrote: I just tried to update my www/sogo2 jail and I now have ports breakage. The first thing that happened is that "portmaster -Rad" failed on ftp/curl with the following message: """ ===> Cleaning for curl-7.49.1 You have a /usr/local/lib/libcrypto.so file installed, but the framework is unable to determine what port it comes from. Add DEFAULT_VERSIONS+=ssl= to your /etc/make.conf and try again. *** Error code 1 Stop. make[1]: stopped in /usr/ports/ftp/curl *** Error code 1 Stop. make: stopped in /usr/ports/ftp/curl ===>>> make build failed for ftp/curl ===>>> Aborting update ===>>> Update for curl-7.48.0_2 failed ===>>> Aborting update """ It seems that ftp/curl can't build with openssl or libressl installed from ports. And www/nginx will only build with openssl or libresll installed from ports. So basically nginx and curl can't co-exist on the same host/jail. My port options are almost all the defaults, and I don't want to set anything in /etc/make.conf, but even if I do set DEFAULT_VERSIONS+=ssl=ssl I can't get curl to build. I've been updating this jail regulary for a while now without any issue. This reminds me hair-pulling in the past with the Kerberos fork issues (MIT vs Heimdal). And I was finding ports management so easy these days, until today. Why can't curl just use openssl from base, despite the port version being installed? # uname -a FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue Jul 28 12:04:19 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Jim Ohlstein "Never argue with a fool, onlookers may not be able to tell the difference." - Mark Twain ___ 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: curl and nginx no longer build on same host
On Saturday, July 16, 2016 10:21 SGT, Jim Ohlstein wrote: > Hello, > > > On Jul 15, 2016, at 10:03 PM, Euan Thoms wrote: > > > > Bump > > > > Can anyone else install or update ftp/curl after installing nginx? > > Yes, but I'm building packages using poudriere, not using portmaster. Good point, it may be a portmaster issue. Next time I update, I'll try to upgrade manually... eh, how do I do that again (scratches head). > > > > > The only way I'm able to update now is to uninstall openssl and nginx, then > > update curl, then reinstall nginx (which pulls in openssl). This was not > > required on several previous update cycles. > > If memory serves me correctly, nginx and curl both require openssl from ports > only if certain options are chosen (http2 being one), or at least that was > the case in the past. > > You may have option(s) selected for one that requires the version from ports, > and one that does not. > > Have you tried to force usage of openssl from ports in your /etc/make.conf? > Yes. I've used ssl=openssl and ssl=libressl in make.conf, no luck with either. The bottom line is ftp/curl with default port options does not want to build against openssl or libressl from ports. And it doesn't want to try and use the base openssl either. Your point about the port options for http2 requiring the ports version of openssl is valid. But this happens when the default options for both ports are used. I could accept my manual workaround if I had changed the default port options on either of the two ports. But default port options should build together. I suppose this has only come about on this upgrade cycle because nginx port now has http2 on by default? > > > > > >> On Thursday, July 14, 2016 23:30 SGT, "Euan Thoms" > >> wrote: > >> > >> I just tried to update my www/sogo2 jail and I now have ports breakage. > >> > >> The first thing that happened is that "portmaster -Rad" failed on ftp/curl > >> with the following message: > >> > >> """ > >> ===> Cleaning for curl-7.49.1 > >> You have a /usr/local/lib/libcrypto.so file installed, but the framework > >> is unable > >> to determine what port it comes from. > >> Add DEFAULT_VERSIONS+=ssl= to your /etc/make.conf > >> and try again. > >> *** Error code 1 > >> > >> Stop. > >> make[1]: stopped in /usr/ports/ftp/curl > >> *** Error code 1 > >> > >> Stop. > >> make: stopped in /usr/ports/ftp/curl > >> > >> ===>>> make build failed for ftp/curl > >> ===>>> Aborting update > >> > >> ===>>> Update for curl-7.48.0_2 failed > >> ===>>> Aborting update > >> """ > >> > >> It seems that ftp/curl can't build with openssl or libressl installed from > >> ports. And www/nginx will only build with openssl or libresll installed > >> from ports. So basically nginx and curl can't co-exist on the same > >> host/jail. > >> > >> My port options are almost all the defaults, and I don't want to set > >> anything in /etc/make.conf, but even if I do set > >> DEFAULT_VERSIONS+=ssl=ssl I can't get curl to build. > >> > >> I've been updating this jail regulary for a while now without any issue. > >> This reminds me hair-pulling in the past with the Kerberos fork issues > >> (MIT vs Heimdal). And I was finding ports management so easy these days, > >> until today. > >> > >> Why can't curl just use openssl from base, despite the port version being > >> installed? > >> > >> > >> > >> # uname -a > >> FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: > >> Tue Jul 28 12:04:19 UTC 2015 > >> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > -- Regards, Euan Thoms ___ 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: curl and nginx no longer build on same host
Hello, > On Jul 15, 2016, at 10:03 PM, Euan Thoms wrote: > > Bump > > Can anyone else install or update ftp/curl after installing nginx? Yes, but I'm building packages using poudriere, not using portmaster. > > The only way I'm able to update now is to uninstall openssl and nginx, then > update curl, then reinstall nginx (which pulls in openssl). This was not > required on several previous update cycles. If memory serves me correctly, nginx and curl both require openssl from ports only if certain options are chosen (http2 being one), or at least that was the case in the past. You may have option(s) selected for one that requires the version from ports, and one that does not. Have you tried to force usage of openssl from ports in your /etc/make.conf? > > >> On Thursday, July 14, 2016 23:30 SGT, "Euan Thoms" >> wrote: >> >> I just tried to update my www/sogo2 jail and I now have ports breakage. >> >> The first thing that happened is that "portmaster -Rad" failed on ftp/curl >> with the following message: >> >> """ >> ===> Cleaning for curl-7.49.1 >> You have a /usr/local/lib/libcrypto.so file installed, but the framework is >> unable >> to determine what port it comes from. >> Add DEFAULT_VERSIONS+=ssl= to your /etc/make.conf and >> try again. >> *** Error code 1 >> >> Stop. >> make[1]: stopped in /usr/ports/ftp/curl >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/ftp/curl >> >> ===>>> make build failed for ftp/curl >> ===>>> Aborting update >> >> ===>>> Update for curl-7.48.0_2 failed >> ===>>> Aborting update >> """ >> >> It seems that ftp/curl can't build with openssl or libressl installed from >> ports. And www/nginx will only build with openssl or libresll installed from >> ports. So basically nginx and curl can't co-exist on the same host/jail. >> >> My port options are almost all the defaults, and I don't want to set >> anything in /etc/make.conf, but even if I do set >> DEFAULT_VERSIONS+=ssl=ssl I can't get curl to build. >> >> I've been updating this jail regulary for a while now without any issue. >> This reminds me hair-pulling in the past with the Kerberos fork issues (MIT >> vs Heimdal). And I was finding ports management so easy these days, until >> today. >> >> Why can't curl just use openssl from base, despite the port version being >> installed? >> >> >> >> # uname -a >> FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue >> Jul 28 12:04:19 UTC 2015 >> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Jim ___ 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: curl and nginx no longer build on same host
Bump Can anyone else install or update ftp/curl after installing nginx? The only way I'm able to update now is to uninstall openssl and nginx, then update curl, then reinstall nginx (which pulls in openssl). This was not required on several previous update cycles. On Thursday, July 14, 2016 23:30 SGT, "Euan Thoms" wrote: > I just tried to update my www/sogo2 jail and I now have ports breakage. > > The first thing that happened is that "portmaster -Rad" failed on ftp/curl > with the following message: > > """ > ===> Cleaning for curl-7.49.1 > You have a /usr/local/lib/libcrypto.so file installed, but the framework is > unable > to determine what port it comes from. > Add DEFAULT_VERSIONS+=ssl= to your /etc/make.conf and > try again. > *** Error code 1 > > Stop. > make[1]: stopped in /usr/ports/ftp/curl > *** Error code 1 > > Stop. > make: stopped in /usr/ports/ftp/curl > > ===>>> make build failed for ftp/curl > ===>>> Aborting update > > ===>>> Update for curl-7.48.0_2 failed > ===>>> Aborting update > """ > > It seems that ftp/curl can't build with openssl or libressl installed from > ports. And www/nginx will only build with openssl or libresll installed from > ports. So basically nginx and curl can't co-exist on the same host/jail. > > My port options are almost all the defaults, and I don't want to set anything > in /etc/make.conf, but even if I do set DEFAULT_VERSIONS+=ssl=ssl I > can't get curl to build. > > I've been updating this jail regulary for a while now without any issue. This > reminds me hair-pulling in the past with the Kerberos fork issues (MIT vs > Heimdal). And I was finding ports management so easy these days, until today. > > Why can't curl just use openssl from base, despite the port version being > installed? > > > > # uname -a > FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue > Jul 28 12:04:19 UTC 2015 > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > -- > Regards, Euan Thoms > > ___ > 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" -- Regards, Euan Thoms ___ 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"
curl and nginx no longer build on same host
I just tried to update my www/sogo2 jail and I now have ports breakage. The first thing that happened is that "portmaster -Rad" failed on ftp/curl with the following message: """ ===> Cleaning for curl-7.49.1 You have a /usr/local/lib/libcrypto.so file installed, but the framework is unable to determine what port it comes from. Add DEFAULT_VERSIONS+=ssl= to your /etc/make.conf and try again. *** Error code 1 Stop. make[1]: stopped in /usr/ports/ftp/curl *** Error code 1 Stop. make: stopped in /usr/ports/ftp/curl ===>>> make build failed for ftp/curl ===>>> Aborting update ===>>> Update for curl-7.48.0_2 failed ===>>> Aborting update """ It seems that ftp/curl can't build with openssl or libressl installed from ports. And www/nginx will only build with openssl or libresll installed from ports. So basically nginx and curl can't co-exist on the same host/jail. My port options are almost all the defaults, and I don't want to set anything in /etc/make.conf, but even if I do set DEFAULT_VERSIONS+=ssl=ssl I can't get curl to build. I've been updating this jail regulary for a while now without any issue. This reminds me hair-pulling in the past with the Kerberos fork issues (MIT vs Heimdal). And I was finding ports management so easy these days, until today. Why can't curl just use openssl from base, despite the port version being installed? # uname -a FreeBSD sogo.potensol.com 10.1-RELEASE-p16 FreeBSD 10.1-RELEASE-p16 #0: Tue Jul 28 12:04:19 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 -- Regards, Euan Thoms ___ 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"
