Re: FreeBSD Port: phpipam-1.0
Hi! > Any chance this port will be getting update to the > latest and greatest (1.2.1)? A suggested patch for this upgrade can be found in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211151 Can you run-test if it works for you ? -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ 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"
Re: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Saturday, July 16, 2016 00:10 SGT, Don Lewis wrote: > On 15 Jul, Euan Thoms wrote: > > > > On Friday, July 15, 2016 15:26 SGT, Kubilay Kocak > > wrote: > > > >> On 15/07/2016 5:17 PM, Martin Waschbüsch wrote: > >> > > >> >> Am 14.07.2016 um 23:29 schrieb Euan Thoms : > >> >> > >> >> > >> >> On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld > >> >> wrote: > >> >> > >> >>> I think this statements should be only warnings. Cause not all > >> >>> of these statements are right and each maintianer should decide > >> >>> which "USES" or "LIB_DEPENDS" are necessairely and which not. > >> >> > >> >> Well, I don't know enough to comment about whether it should be > >> >> classed as a warning or an error. But there's definetely a bug in > >> >> the ports Mk system, since adding USES+=iconv does not remove the > >> >> error. I don't think I even need iconv as a dependency, it should > >> >> be included lower down in the dependency tree. > >> > > >> > I am not sure about this. At the very least, sope-core does use > >> > iconv in its NGExtensions (e.g. NSString+Encoding.m). Can we really > >> > assume some lower dependency package already pulls iconv in? > >> > >> If something in a port links to libiconv (or anything else), then > >> the dependency should be registered in that port > >> > > > > OK, thanks guys. I will add libiconv as a LIB_DEPENDS. But I still > > think there may be a bug. The make error tells me to use USES+=iconv > > and it doesn't work, I still get the same error about libiconv not > > being specified as a dependancy. > > It looks like USES=iconv doesn't add the dependency on newer FreeBSD > versions that have basic iconv support in the base system. If you set > USES=iconv:wchar_t or USES=iconv:translit, then it will unconditionally > add the dependency. > > If you don't use the WCHAR_T or //TRANSLIT extensions, it may not be > necessary to link with -liconv, but it is possible that the port does > this automatically if it finds that libiconv is installed by another > dependency. > It seems adding "libiconv.so:converters/libiconv" to LIB_DEPENDS clears all errors and warnings. This is what I will use unless anyone can tell me why it's not recommended. Thanks everyone involved, for your help. -- 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Friday, July 15, 2016 14:27 SGT, mokhi wrote: > > I'll look into this as soon as I can > Okay :) thanks > As I'm maintainer of mysql57, someone mailed me logs of that problem, > AFAIK There's no problem for mysql56 but it happens when 57 is found > instead of 56 > > Thanks and regards, Mokhi. Mokhi, a bit off topic but I'm just installing the mysql57-client port and the mysql-boost tarball fails on the first few mirrors, and even when one works (below) it's very slow download. Hard to believe a project like MySQL has such slow mirrors. This server is located in Singapore, but the speeds should not be explained by distance or route. ftp://ftp.fi.muni.cz/pub/mysql/Downloads/MySQL-5.7/mysql-boost-5.7.13.tar.gz -- 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Friday, July 15, 2016 14:27 SGT, mokhi wrote: > > I'll look into this as soon as I can > Okay :) thanks > As I'm maintainer of mysql57, someone mailed me logs of that problem, > AFAIK There's no problem for mysql56 but it happens when 57 is found > instead of 56 > > Thanks and regards, Mokhi. Now that's interesting. I'm glad you mentioned that, it could save me a lot of time. Coincidentally, just going through my emails, I read a headline for BSD Magazine article about problems with MySQL 5.7 on FreeBSD, Since I still haven't got round to subscribing I can't read the article yet. I am not up on the issue, is there anywhere I can read up on the issue? -- 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Saturday, July 16, 2016 00:10 SGT, Don Lewis wrote: > On 15 Jul, Euan Thoms wrote: > > > > On Friday, July 15, 2016 15:26 SGT, Kubilay Kocak > > wrote: > > > >> On 15/07/2016 5:17 PM, Martin Waschbüsch wrote: > >> > > >> >> Am 14.07.2016 um 23:29 schrieb Euan Thoms : > >> >> > >> >> > >> >> On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld > >> >> wrote: > >> >> > >> >>> I think this statements should be only warnings. Cause not all > >> >>> of these statements are right and each maintianer should decide > >> >>> which "USES" or "LIB_DEPENDS" are necessairely and which not. > >> >> > >> >> Well, I don't know enough to comment about whether it should be > >> >> classed as a warning or an error. But there's definetely a bug in > >> >> the ports Mk system, since adding USES+=iconv does not remove the > >> >> error. I don't think I even need iconv as a dependency, it should > >> >> be included lower down in the dependency tree. > >> > > >> > I am not sure about this. At the very least, sope-core does use > >> > iconv in its NGExtensions (e.g. NSString+Encoding.m). Can we really > >> > assume some lower dependency package already pulls iconv in? > >> > >> If something in a port links to libiconv (or anything else), then > >> the dependency should be registered in that port > >> > > > > OK, thanks guys. I will add libiconv as a LIB_DEPENDS. But I still > > think there may be a bug. The make error tells me to use USES+=iconv > > and it doesn't work, I still get the same error about libiconv not > > being specified as a dependancy. > > It looks like USES=iconv doesn't add the dependency on newer FreeBSD > versions that have basic iconv support in the base system. If you set > USES=iconv:wchar_t or USES=iconv:translit, then it will unconditionally > add the dependency. > > If you don't use the WCHAR_T or //TRANSLIT extensions, it may not be > necessary to link with -liconv, but it is possible that the port does > this automatically if it finds that libiconv is installed by another > dependency. > Aha, in that case perhaps ignore my last email. This starts to make more sense now. although the stage-qa error message is misleading. Is this case, would I not be better adding a LIB_DEPENDS instead of USES=iconv.wchar_t or USES=iconv:translit? I don't even know where to find out which one I need. A bit off tpic, but personally I prefer to just use the LIB_DEPENDS for a straight dependency. Keeping track of which macros to use can be more difficult than the time they save. I've only been porting for about a year, yet the ports system seems to be going through a lot of changes in this time. All good changes I'm sure. As a user I do find installing and upgrading easier than I did when I strated using ports about 5 years ago. I'm just about to start working on the port again now. -- 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Saturday, July 16, 2016 00:11 SGT, Don Lewis wrote: > On 15 Jul, Euan Thoms wrote: > > > > On Friday, July 15, 2016 16:43 SGT, Walter Schwarzenfeld > > wrote: > > > >> Also there are some ports who had USES=readline and stage-qa states > >> You have to add USES+=readline. > >> Here is also the statement wrong. > > > > That's interesting. When I said I did add USES+=iconv, actually I just > > added iconv to the existing USES= declaration. I will try USES+=iconv > > next time I work on the port. > > They should be equivalent. Yes, but should and is are not the same thing. -- 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"
FreeBSD Port: phpipam-1.0
Hi Jake, Any chance this port will be getting update to the latest and greatest (1.2.1)? Thank you, Brandon McCorkle Network Administrator Department of Technology [Arch Email] City of Gahanna 200 S. Hamilton Rd. Gahanna, Ohio 43230 614.342.4071 614.342.4171 (fax) brandon.mccor...@gahanna.gov ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
No, that what a missunderstood. There are some ports have USES=readline in the Makefile. But the warning " /You have to add USES+=readline" appears. (the warning uses the "+", but that was not what I meant)./ ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On 15 Jul, Euan Thoms wrote: > > On Friday, July 15, 2016 16:43 SGT, Walter Schwarzenfeld > wrote: > >> Also there are some ports who had USES=readline and stage-qa states >> You have to add USES+=readline. >> Here is also the statement wrong. > > That's interesting. When I said I did add USES+=iconv, actually I just > added iconv to the existing USES= declaration. I will try USES+=iconv > next time I work on the port. They should be equivalent. ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On 15 Jul, Euan Thoms wrote: > > On Friday, July 15, 2016 15:26 SGT, Kubilay Kocak > wrote: > >> On 15/07/2016 5:17 PM, Martin Waschbüsch wrote: >> > >> >> Am 14.07.2016 um 23:29 schrieb Euan Thoms : >> >> >> >> >> >> On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld >> >> wrote: >> >> >> >>> I think this statements should be only warnings. Cause not all >> >>> of these statements are right and each maintianer should decide >> >>> which "USES" or "LIB_DEPENDS" are necessairely and which not. >> >> >> >> Well, I don't know enough to comment about whether it should be >> >> classed as a warning or an error. But there's definetely a bug in >> >> the ports Mk system, since adding USES+=iconv does not remove the >> >> error. I don't think I even need iconv as a dependency, it should >> >> be included lower down in the dependency tree. >> > >> > I am not sure about this. At the very least, sope-core does use >> > iconv in its NGExtensions (e.g. NSString+Encoding.m). Can we really >> > assume some lower dependency package already pulls iconv in? >> >> If something in a port links to libiconv (or anything else), then >> the dependency should be registered in that port >> > > OK, thanks guys. I will add libiconv as a LIB_DEPENDS. But I still > think there may be a bug. The make error tells me to use USES+=iconv > and it doesn't work, I still get the same error about libiconv not > being specified as a dependancy. It looks like USES=iconv doesn't add the dependency on newer FreeBSD versions that have basic iconv support in the base system. If you set USES=iconv:wchar_t or USES=iconv:translit, then it will unconditionally add the dependency. If you don't use the WCHAR_T or //TRANSLIT extensions, it may not be necessary to link with -liconv, but it is possible that the port does this automatically if it finds that libiconv is installed by another dependency. ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Friday, July 15, 2016 16:43 SGT, Walter Schwarzenfeld wrote: > Also there are some ports who had USES=readline and stage-qa states You > have to add USES+=readline. > Here is also the statement wrong. That's interesting. When I said I did add USES+=iconv, actually I just added iconv to the existing USES= declaration. I will try USES+=iconv next time I work on the port. -- 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On Friday, July 15, 2016 15:26 SGT, Kubilay Kocak wrote: > On 15/07/2016 5:17 PM, Martin Waschbüsch wrote: > > > >> Am 14.07.2016 um 23:29 schrieb Euan Thoms : > >> > >> > >> On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld > >> wrote: > >> > >>> I think this statements should be only warnings. Cause not all > >>> of these statements are right and each maintianer should decide > >>> which "USES" or "LIB_DEPENDS" are necessairely and which not. > >> > >> Well, I don't know enough to comment about whether it should be > >> classed as a warning or an error. But there's definetely a bug in > >> the ports Mk system, since adding USES+=iconv does not remove the > >> error. I don't think I even need iconv as a dependency, it should > >> be included lower down in the dependency tree. > > > > I am not sure about this. At the very least, sope-core does use iconv > > in its NGExtensions (e.g. NSString+Encoding.m). Can we really assume > > some lower dependency package already pulls iconv in? > > If something in a port links to libiconv (or anything else), then > the dependency should be registered in that port > OK, thanks guys. I will add libiconv as a LIB_DEPENDS. But I still think there may be a bug. The make error tells me to use USES+=iconv and it doesn't work, I still get the same error about libiconv not being specified as a dependancy. -- 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: Wxlua / Zbstudio
This is my script to build: https://github.com/korekontakt/ZeroBraneStudio/blob/master/build/build-freebsd.sh The git is forked from https://github.com/pkulchenko/ZeroBraneStudio by adding some flags from https://github.com/freebsd/freebsd-ports/blob/master/x11-toolkits/wxgtk30/Makefile To build all: ./build-freebsd.sh wxwidgets lua 5.1 luasocket luasec wxlua wxlua was updated with Lua 5.2.2, 5.3.3 and Lua JIT 2.1.0-beta2 https://github.com/korekontakt/wxlua wxlua was forked from https://github.com/pkulchenko/wxlua, which was forked from https://github.com/LuaDist/wxlua For wxwidgets, these two flags --with-libtiff=builtin --with-expat=sys must be builtin or sys. If they're set to no, then they'll get errors. I don't know the difference of builtin and sys. For FreeBSD's Makefile, it uses sys but pkulchenko uses builtin on his build-linux.sh. On Fri, Jul 15, 2016 at 1:33 AM, Torsten Zuehlsdorff < mailingli...@toco-domains.de> wrote: > On 14.07.2016 12:30, Raymond Cheung wrote: > >> I tried to include lua 5.3 src to wxlua but still got the segmentation >> fault. >> >> Also, clang can't build wxlua even I add -I/usr/local/include. It can be >> easily to build with GCC. However, libwx.so can't be loaded. >> On Jul 13, 2016 18:04, "Raymond Cheung" wrote: >> > > How did you build it with GCC? I'm failing around 21% with: > > [ 22%] Linking CXX shared library ../../lib/Release/ > libwxlua-wx30gtk2u-2.8.12.3.so > /usr/local/lib: file not recognized: File format not recognized > collect2: error: ld returned 1 exit status > *** Error code 1 > > Attached my current port as shar for x11-toolkits/wxlua. Just extract it > and do a "make". > > Greetings, > Torsten > ___ 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"
binary packages and CPU-features
Hello! What is the general approach to porting software, which uses advanced CPU-features (like SSE), but has no run-time detection of them? I just added graphics/lepton, for example, which has some functions implemented with AVX2 intrinsics -- but whether or not to use them is determined at compile-time... The original code also required SSE4, but I managed to patch it to lower the requirements to SSSE3. Typically, pre-built packages target the lowest, but this particular program will not build without at least SSSE3 available at all. Should there be three separate packages: lepton-avx2, lepton-ssse3, and lepton-sse4? Maybe, our package-building infrastructure should automatically produce different packages from ports expressing such a desire by declaring, for example: CPUSPECIFIC=avx2 ssse3 sse4 CPUSPECIFIC_AVX2= -mavx2 CPUSPECIFIC_SSSE3= -mssse3 CPUSPECIFIC_SSE4= -msse4.1 Should I simply set NO_PACKAGE -- to avoid a situation when a prebuilt binary will not even start for some users (such as on older Opterons)? -mi -mi ___ 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"
Failure to build Samba43
[3585/3876] Linking default/source3/client/smbclient
runner cc default/source3/client/client_162.o
default/source3/client/clitar_162.o
default/source3/client/dnsbrowse_162.o
default/libcli/smbreadline/smbreadline_1.o -o
/usr/ports/net/samba43/work/samba-4.3.11/bin/default/source3/client/smbclient
-fstack-protector -pie -Wl,-z,relro,-z,now -lpthread -Wl,-no-undefined
-Wl,--export-dynamic -Wl,--as-needed
-Wl,-rpath,/usr/ports/net/samba43/work/samba-4.3.11/bin/shared
-Wl,-rpath,/usr/ports/net/samba43/work/samba-4.3.11/bin/shared/private
-Ldefault/libds/common -Ldefault/auth -Ldefault/source4/lib/socket
-Ldefault/libcli/nbt -Ldefault/lib/ldb-samba -Ldefault/nsswitch
-Ldefault/source4/auth/kerberos -Ldefault/source4/dsdb
-Ldefault/source4/libcli/ldap -Ldefault/source4/lib/events
-Ldefault/libcli/registry -Ldefault/lib/tdb_wrap
-Ldefault/source4/librpc -Ldefault/lib/param -Ldefault/auth/credentials
-Ldefault/nsswitch/libwbclient -Ldefault/auth/gensec
-Ldefault/lib/krb5_wrap -Ldefault/libcli/auth -Ldefault/libcli/cldap
-Ldefault/libcli/ldap -Ldefault/lib/addns
-Ldefault/source4/heimdal_build -Ldefault/lib -Ldefault/librpc
-Ldefault/libcli/smb -Ldefault/lib/dbwrap -Ldefault/lib/socket
-Ldefault/libcli/util -Ldefault/libcli/security -Ldefault/source3
-Ldefault/lib/replace -Ldefault/lib/util -L/usr/local/lib -Wl,-Bdynamic
-ltalloc-report-samba4 -ltevent-util -lreplace-samba4
-lmessages-dgm-samba4 -lsamba-security-samba4 -lerrors-samba4
-lsamba3-util-samba4 -lsys-rw-samba4 -lutil-tdb-samba4
-linterfaces-samba4 -lpopt-samba3-samba4 -lsamba-util
-lsocket-blocking-samba4 -lmessages-util-samba4 -llibsmb-samba4
-lmsrpc3-samba4 -lserver-id-db-samba4 -ldbwrap-samba4 -liov-buf-samba4
-lsmbconf -lcli-smb-common-samba4 -lsamba-cluster-support-samba4
-ldcerpc-samba-samba4 -lndr-standard -lmsghdr-samba4
-lsamba-sockets-samba4 -lndr -lsamba-debug-samba4 -lutil-cmdline-samba4
-ltime-basic-samba4 -lutil-setid-samba4 -lgenrand-samba4 -lkrb5-samba4
-laddns-samba4 -lgssapi-samba4 -lcli-ldap-common-samba4
-lcli-cldap-samba4 -lcliauth-samba4 -lkrb5samba-samba4 -lgse-samba4
-lgensec -lwbclient -lsamba-credentials -lndr-samba-samba4
-lsamba-hostconfig -lndr-nbt -ldcerpc-binding -lndr-samba4
-ltdb-wrap-samba4 -lsmbregistry-samba4 -lCHARSET3-samba4
-lutil-reg-samba4 -lsmb-transport-samba4 -lroken-samba4 -levents-samba4
-lsecrets3-samba4 -lheimbase-samba4 -lcom_err-samba4 -lasn1-samba4
-lhx509-samba4 -lhcrypto-samba4 -lwind-samba4 -lasn1util-samba4
-lcli-ldap-samba4 -lsamba-modules-samba4 -lsamdb -lauthkrb5-samba4
-lwinbind-client-samba4 -lsamdb-common-samba4 -lldbsamba-samba4
-lndr-krb5pac -lserver-role-samba4 -lsmbd-shim-samba4 -lcli-nbt-samba4
-lnetif-samba4 -lauth-sam-reply-samba4 -lflag-mapping-samba4 -lutil -lz
-lgnutls -lldb -ltalloc -lldap -llber -liconv -lmd -lrt -lexecinfo
-lncurses -ltdb -lpopt -larchive -lcrypt -ltevent -lreadline
//usr/local/lib/libssl.so.8: undefined reference to
`BIO_dgram_sctp_msg_waiting'
//usr/local/lib/libssl.so.8: undefined reference to `BIO_dgram_is_sctp'
//usr/local/lib/libssl.so.8: undefined reference to
`BIO_dgram_sctp_wait_for_dry'
cc: error: linker command failed with exit code 1 (use -v to see invocation)
Waf: Leaving directory `/usr/ports/net/samba43/work/samba-4.3.11/bin'
Build failed: -> task failed (err #1):
{task: cc_link
client_162.o,clitar_162.o,dnsbrowse_162.o,smbreadline_1.o -> smbclient}
===> Compilation failed unexpectedly.
This is with the most-recent port openssl updates installed as well and
DEFAULT_VERSIONS+=ssl=openssl
in /etc/make.conf
--
Karl Denninger
k...@denninger.net
/The Market Ticker/
/[S/MIME encrypted email preferred]/
smime.p7s
Description: S/MIME Cryptographic Signature
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 +-+ archivers/ppmd-7z | 9.04| 16.02 +-+ x11-clocks/buici-clock | 0.4.9.2 | 0.4.9.3 +-+ 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"
Re: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On 07/15/16 09:37, Walter Schwarzenfeld wrote: > It is a bug the statement is wrong. > The error message disappiear if you add to LIB_DEPENDS > libiconv.so:converters/libiconv. > > Btw. > it says > Error: /usr/local/GNUstep/Local/Library/Libraries/libNGStreams.so.4.9.57 > is linked to /usr/local/lib/libssl.so.38 from security/libressl but it > is not declared as a dependency > Warning: you need USES=ssl > Error: /usr/local/GNUstep/Local/Library/Libraries/libNGStreams.so.4.9.57 > is linked to /usr/local/lib/libcrypto.so.37 from security/libressl but > it is not declared as a dependency > Warning: you need USES=ssl > > > if I add ssl to USES > it states > you may not need USES+=ssl. > > I am not happy with the "new" stage-qa messages. I agree that this is annoying, and I wish there was some way to tell stage-qa that the library dependencies are in fact OK. The problem here is the heuristic used to determine whether there are any missing library dependencies. This simply uses readelf(1) to find out what's required by the dynamic loader for all of the binaries included in the port. If it finds that an application 'foo' requires a shared library libbar it will tell you 'you need USES+=bar' Much of the time this is correct, and a handy sanity check. However, what seems to happen fairly often is that foo only has a direct dependency on libbaz and libbaz is what links against libbar. foo doesn't know anything about functions and objects provided by libbar or use any of them itself, except through the interface provided by libbaz, so foo's dependency on libbar is entirely indirect. In this situation I can't see why the port foo should list an explicit dependency on libbar; the one it inherits through libbaz seems to me to express the linkage between foo and libbar in an entirely satisfactory way. You should only get the 'you may not need USES+=foo' message when you've added the dependency in the ports Makefile, but none of the resulting binaries link against libfoo. I don't see how you are getting the results you describe there. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
USES? ssl:libressl the question mark is a typo, should be USES= ssl:libressl ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
=> you may not need USES+=ssl. And this message disappeared if I set USES? ssl:libressl. This should not needed if I had DEFAULT_VERSIONS=ssl=libressl in /etc/make.conf. (I think only USES=ssl should be enough). ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
Also there are some ports who had USES=readline and stage-qa states You have to add USES+=readline. Here is also the statement wrong. ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
It is a bug the statement is wrong. The error message disappiear if you add to LIB_DEPENDS libiconv.so:converters/libiconv. Btw. it says Error: /usr/local/GNUstep/Local/Library/Libraries/libNGStreams.so.4.9.57 is linked to /usr/local/lib/libssl.so.38 from security/libressl but it is not declared as a dependency Warning: you need USES=ssl Error: /usr/local/GNUstep/Local/Library/Libraries/libNGStreams.so.4.9.57 is linked to /usr/local/lib/libcrypto.so.37 from security/libressl but it is not declared as a dependency Warning: you need USES=ssl if I add ssl to USES it states you may not need USES+=ssl. I am not happy with the "new" stage-qa messages. ___ 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"
Get Online Presence.
Hello Good Day, Want more clients and customers? We will help them find you by putting you on the Top 10 page of Google. If yes, please let us know your domain name which you want to optimize. We will run analysis on your website and no cost and send full report with all the points and where your website is missing. Email us back to get a full proposal. Thanks & Regards, Shivam Business Development Manager ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
On 15/07/2016 5:17 PM, Martin Waschbüsch wrote: > >> Am 14.07.2016 um 23:29 schrieb Euan Thoms : >> >> >> On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld >> wrote: >> >>> I think this statements should be only warnings. Cause not all >>> of these statements are right and each maintianer should decide >>> which "USES" or "LIB_DEPENDS" are necessairely and which not. >> >> Well, I don't know enough to comment about whether it should be >> classed as a warning or an error. But there's definetely a bug in >> the ports Mk system, since adding USES+=iconv does not remove the >> error. I don't think I even need iconv as a dependency, it should >> be included lower down in the dependency tree. > > I am not sure about this. At the very least, sope-core does use iconv > in its NGExtensions (e.g. NSString+Encoding.m). Can we really assume > some lower dependency package already pulls iconv in? If something in a port links to libiconv (or anything else), then the dependency should be registered in that port ___ 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: devel/sope: make (stage-qa) now fails with DEVELOPER=yes complaining about iconv dependency
> Am 14.07.2016 um 23:29 schrieb Euan Thoms : > > > On Friday, July 15, 2016 01:11 SGT, Walter Schwarzenfeld > wrote: > >> I think this statements should be only warnings. Cause not all of these >> statements are right and each maintianer should decide which "USES" or >> "LIB_DEPENDS" are necessairely and which not. > > Well, I don't know enough to comment about whether it should be classed as a > warning or an error. But there's definetely a bug in the ports Mk system, > since adding USES+=iconv does not remove the error. I don't think I even need > iconv as a dependency, it should be included lower down in the dependency > tree. I am not sure about this. At the very least, sope-core does use iconv in its NGExtensions (e.g. NSString+Encoding.m). Can we really assume some lower dependency package already pulls iconv in? ___ 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"
