Trouble compiling bind916
While trying to compile bind 916 on a Raspberry Pi 3 running FreeBSD pelorus.zefox.org 13.0-ALPHA2 FreeBSD 13.0-ALPHA2 #1 stable/13-c256213-g03d837b565a: Sat Jan 30 15:07:58 PST 2021 b...@pelorus.zefox.org:/usr/obj/usr/freebsd-src/arm64.aarch64/sys/GENERIC-MMCCAM arm64 the effort stopped with [1]Exit 1make -DBATCH > make.log root@pelorus:/usr/ports/dns/bind916 # tail *.log ===> fstrm-0.6.0 depends on shared library: libevent.so - found (/usr/local/lib/libevent.so) ===> Configuring for fstrm-0.6.0 *** Error code 127 Stop. make[1]: stopped in /usr/ports/devel/fstrm The punchline seems to be root@pelorus:/usr/ports/dns/bind916 # cd /usr/ports/devel/fstrm root@pelorus:/usr/ports/devel/fstrm # make -DBATCH > make.log & [1] 1626 root@pelorus:/usr/ports/devel/fstrm # exec: /usr/local/bin/autoreconf-2.69: not found [1]Exit 1make -DBATCH > make.log but: root@pelorus:/usr/ports/devel/fstrm # whereis autoreconf autoreconf: /usr/local/bin/autoreconf root@pelorus:/usr/ports/devel/fstrm # Is there a fix or workaround? /usr/ports is at Revision: 563453 Thanks for reading, bob prohaska ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gstreamer1-plugins-opencv
...doesn't built on FreeBSD 12.2-RELEASE-p3 after update of opencv: opencv_1.0_la-gstopencvutils.lo -MD -MP -MF .deps/libgstopencv_1.0_la-gstopencvutils.Tpo -c gstopencvutils.cpp -fPIC -DPIC -o .libs/libgstopencv_1.0_la-gstopencvutils.o gstopencvutils.cpp:28:10: fatal error: 'opencv2/core.hpp' file not found #include ^~ 1 error generated. gmake[1]: *** [Makefile:866: libgstopencv_1.0_la-gstopencvutils.lo] Error 1 gmake[1]: Leaving directory '/usr/ports/graphics/gstreamer1-plugins-opencv/work/gst-plugins-bad-1.16.2/gst-libs/gst/opencv' *** Error code 2 Stop. make: stopped in /usr/ports/graphics/gstreamer1-plugins-opencv ===>>> make build failed for graphics/gstreamer1-plugins-opencv ===>>> Aborting update Thank you. -- “Those who can make you believe absurdities can make you commit atrocities.” --Voltaire ___ 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: Warning: Major OS version upgrade detected
Xavier Humbert xavier at groumpf.org wrote on Sat Jan 30 22:02:51 UTC 2021 : > I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE > > Now, when I run any ports/pkg command - I use only ports-, I got > > > pkg-static: Warning: Major OS version upgrade detected. Running "pkg > > bootstrap -f" recommended > No a big deal, I thought, but : > > > [root at numenor ~]# pkg bootstrap -f > > The package management tool is not yet installed on your system. > > Do you want to fetch and install it now? [y/N]: y > > Bootstrapping pkg from > > pkg+http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest, please wait... > > Verifying signature with trusted certificate > > pkg.freebsd.org.2013102301... done > > pkg-static: Warning: Major OS version upgrade detected. Running "pkg > > bootstrap -f" recommended > > Installing pkg-1.16.2... > > pkg-static: wrong architecture: FreeBSD:13:amd64 instead of > > *FreeBSD:14:amd64* > > package pkg is already installed, forced install > > Extracting pkg-1.16.2: 100% > > [root at numenor ~]# pkg check -Bd > > pkg: Warning: Major OS version upgrade detected. Running "pkg > > bootstrap -f" recommended > > The message is still there. I never had 14-CURRENT on this system. > > Reinstalled ports-mgmt/pkg from source, didn't help > I stayed on main but how to follow from main to stable/N is of interest. So I'll watch to see what you learn. (I only just finished updating everything to 14, including all my from-source ports builds, but skipping powerpc and powerpc64.) It would be interesting to know the commit-id of the last main branch commit that you had. This might be essential to someone being able to figure out what happened. author Glen Barber 2021-01-22 00:06:26 + committer Glen Barber 2021-01-22 00:08:57 + commit bfd15705156b0436cfe79aea11868dcc0c6e078a (patch) Create the stable/13 branch author Glen Barber 2021-01-22 00:10:07 + committer Glen Barber 2021-01-22 00:10:07 + commit a53ce3fc4938e37d5ec89304846203d2083c61a2 (patch) Bump CURRENT to 14.0 There is not much time (minutes) after stable/13 was created before main switched to 14. The 30,000+ package builds did not start for more than a day after that for main and for stable/13 (and each takes more than 2 days to build): main-amd64 default build start: Sat, 23 Jan 2021 01:25:15 GMT 13stable-amd64 quarterly build start: Sun, 24 Jan 2021 01:33:13 GMT 13stable-amd64 default build start: Sun, 24 Jan 2021 01:34:10 GMT So it would seem unlikely you could have picked up a pkg that was built for/from stable/13 or main as 14-CURRENT on Jan-22nd or soon after. This leaves me curious about what to avoid at such transitions. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) ___ 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"
Warning: Major OS version upgrade detected
Hi, I was running 13-CURRENT, and as of 01/22 I switched to 13-STABLE Now, when I run any ports/pkg command - I use only ports-, I got pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended No a big deal, I thought, but : [root@numenor ~]# pkg bootstrap -f The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:13:amd64/latest, please wait... Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Installing pkg-1.16.2... pkg-static: wrong architecture: FreeBSD:13:amd64 instead of *FreeBSD:14:amd64* package pkg is already installed, forced install Extracting pkg-1.16.2: 100% [root@numenor ~]# pkg check -Bd pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended The message is still there. I never had 14-CURRENT on this system. Reinstalled ports-mgmt/pkg from source, didn't help Any help ? Thanks, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Senior Engineer ___ 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 +-+ net-p2p/eiskaltdcpp-cli | 2.2.10 | v2.4.1 +-+ net-p2p/eiskaltdcpp-daemon | 2.2.10 | v2.4.1 +-+ net-p2p/eiskaltdcpp-data| 2.2.10 | v2.4.1 +-+ net-p2p/eiskaltdcpp-gtk | 2.2.10 | v2.4.1 +-+ 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 Reported by:portscout! ___ 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"
