bsd.port.mk reduce error to warning for UNAME_r OSVERSION mismatch
bsd.port.mk test below is too agressive, let's have it just Warn, not Fail. Also prefix text "Error: " or "Warning: " make it obvious which is happening. It seems likely people may have different opinions if it should just Warn or Error, so kets add an environent switch to stear that decision. Which way the default setting of switch should be, I won't suggest (in hope of enhancing chance of agreement to add the switch :-) Whoever adds the switch could decide ? Background: current fails to make my /usr/ports/graphics/libspiro I contacted cc'd MAINTAINER= who wrote me "my poudriere is running on 10" I dont run poudriere, but have a native 10 partition so simply did a chroot ... I ran: cd /s2; head -1 /etc/motd # FreeBSD 10.1-RELEASE (LAPR.small) #0: Sat Feb 28 16:29:20 CET 2015 cd /usr/ports/graphics/libspiro make clean make: "/usr/ports/Mk/bsd.port.mk" line 1214: UNAME_r (11.0-CURRENT) and OSVERSION (1001000) do not agree on major version number. make make: "/usr/ports/Mk/bsd.port.mk" line 1214: UNAME_r (11.0-CURRENT) and OSVERSION (1001000) do not agree on major version number. Same forced error can be seen on current lines 1197 & 1199. After I patched out the failing bsd.port.mk error I could continue my test of the port & see the port build with 10 src & ports on an 11 kernel. Cheers, Julian -- Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com Indent previous with "> ". Reply Below as a play script. Send plain text, Not quoted-printable, HTML, or base64. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gnome@ is swamped in @freebsd robot noise, deterring human activity.
> From: Ben Woods > Date: Wed, 17 Jun 2015 06:33:49 +0800 > To: FreeBSD ports , freebsd-gn...@freebsd.org > Subject: Update editors/abiword > The maintainer timeout has long since passed, and I have not been able to > get any feedback from freebsd-gnome@. gnome@freebsd feedback is unlikely, it's dieing from @freebsd robot noise ! http://lists.freebsd.org/pipermail/freebsd-gnome/2015-May/author.html http://lists.freebsd.org/pipermail/freebsd-gnome/2015-June/author.html robots are: bugzilla-noreply pkg-fallout portscout linimon (aka broken ports robot) real mails from humans are rare! 2 in May, 5 in June so far. + spam. Compare traffic with 10 years back: http://lists.freebsd.org/pipermail/freebsd-gnome/2005-June/author.html Lots of humans used gnome@ to co-operate back then. Robot owners should reduce frequency of robot excretions, which swamp gnome@, contravening list definition: http://lists.freebsd.org/mailman/listinfo/freebsd-gnome This is a forum for discussions related to bring the GNOME environment to FreeBSD. This is not cc'd to: gnome@ so usual balance of traffic in archive remains. Cheers, Julian -- Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com Indent previous with "> ". Reply Below as a play script. Send plain text, Not quoted-printable, HTML, or base64. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Update "cairomm" and "cairo" ports
Does anyone know if the "cairomm" and "cairo" ports are going to be updated? There are newer versions available. The cairo 1.14.2 (10-Mar-2015) release is available; as well as cairomm 1.11.2 (11-Feb-2014). Thanks! -- Carmel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Problem building maildrop with exim as MTA
On Wed, 10 Jun 2015, Carmel NY wrote: > I have a question regarding "backscatter". Why are you accepting mail > for non existent clients? Is this the same "Carmel NY" who once took offence to my simple signature, saying that it wasn't compliant or something? I'm sure that I can find that in my mail somewhere... -- Dave ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bsd.port.mk reduce error to warning for UNAME_r OSVERSION mismatch
On 2015-06-16 17:06, Julian H. Stacey wrote: > bsd.port.mk test below is too agressive, let's have it just Warn, not Fail. > Also prefix text "Error: " or "Warning: " make it obvious which is happening. > > It seems likely people may have different opinions if it should > just Warn or Error, so kets add an environent switch to stear that decision. > Which way the default setting of switch should be, I won't suggest > (in hope of enhancing chance of agreement to add the switch :-) > Whoever adds the switch could decide ? > > Background: > current fails to make my /usr/ports/graphics/libspiro > I contacted cc'd MAINTAINER= who wrote me > "my poudriere is running on 10" > I dont run poudriere, but have a native 10 partition > so simply did a chroot ... > I ran: > cd /s2; head -1 /etc/motd > # FreeBSD 10.1-RELEASE (LAPR.small) #0: Sat Feb 28 16:29:20 CET 2015 > cd /usr/ports/graphics/libspiro > make clean > make: "/usr/ports/Mk/bsd.port.mk" line 1214: UNAME_r (11.0-CURRENT) and > OSVERSION (1001000) do not agree on major version number. > make > make: "/usr/ports/Mk/bsd.port.mk" line 1214: UNAME_r (11.0-CURRENT) and > OSVERSION (1001000) do not agree on major version number. > > Same forced error can be seen on current lines 1197 & 1199. > > After I patched out the failing bsd.port.mk error I could continue my test > of the port & see the port build with 10 src & ports on an 11 kernel. > Patching bsd.port.mk is not the way to go, set the following environment vars before starting a build inside the jail - UNAME_r=10.1-RELEASE-p10 - UNAME_v=FreeBSD 10.1-RELEASE-p10 - OSVERSION=1001000 For example in the login.conf of the jail default:\ :setenv=UNAME_r=10.1-RELEASE-p10,UNAME_v=FreeBSD 10.1-RELEASE-p10,OSVERSION=1001000:\ ... -- olli ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
cmake:
When building latest devel/cmake on 10.1-RELEASE-p13 (amd64) # portmaster --no-confirm --no-term-title -D -G cmake there is an error about missing library /usr/local/lib/libjsoncpp.so ... ===> Installing for cmake-3.2.3 ===> Checking if cmake already installed ===> Registering installation for cmake-3.2.3 as automatic (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/ccmake - required shared library /usr/local/lib/libjsoncpp.so not found (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/cmake - required shared library /usr/local/lib/libjsoncpp.so not found (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/cpack - required shared library /usr/local/lib/libjsoncpp.so not found (cmake-3.2.3) /usr/ports/devel/cmake/work/stage//usr/local/bin/ctest - required shared library /usr/local/lib/libjsoncpp.so not found Installing cmake-3.2.3... ===>>> Re-installation of cmake-3.2.3 succeeded ===>>> The following actions were performed: Re-installation of cmake-modules-3.2.3 Re-installation of cmake-3.2.3 However: # ls -l /usr/local/lib/libjsoncpp* -rw-r--r-- 1 root wheel 535316 Jun 17 20:22 /usr/local/lib/libjsoncpp.a lrwxr-xr-x 1 root wheel 15 Jun 17 20:22 /usr/local/lib/libjsoncpp.so -> libjsoncpp.so.0 -r--r--r-- 1 root wheel 348376 Jun 17 20:22 /usr/local/lib/libjsoncpp.so.0 Build finished just fine but during installation registration of shared libraries failed. This can be verified with pkg: # pkg check -Bnv cmake [1/1] Checking cmake-3.2.3: shared libraries...(cmake-3.2.3) /usr/local/bin/ccmake - required shared library /usr/local/lib/libjsoncpp.so not found (cmake-3.2.3) /usr/local/bin/cmake - required shared library /usr/local/lib/libjsoncpp.so not found (cmake-3.2.3) /usr/local/bin/cpack - required shared library /usr/local/lib/libjsoncpp.so not found (cmake-3.2.3) /usr/local/bin/ctest - required shared library /usr/local/lib/libjsoncpp.so not found done Is this a known issue or should I create a PR? Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
