Many ports newly report 'fstat' and refuse to run, and as many don't build until I get around to a buildworld cycle, the workaround is to run v11 pkg pkg install -f ... on this v12 system, then lock the new port from being re-from-package or re-built .............................. Otoh, some like sqlite3 do build, but also have to be locked so they don't revert to packaging upstream, as in WHERE IS THE FILE some file somwhere makes locally built ports freebsd:..v11 ABI rather than the actual uname, v12.0-CURRENT. ......................... A... some one /usr/src/usr.bin or something, or a /lib/ equivalent, that can be reinstalled singly to omit the fstat error. B... another whole problem, why are ports v11 ABI when built on a ABI machine of v12 ....................
Hoping procedures for this type of breakage are documented in the future both for these and for other similar problems, such as in a new file /usr/src/PKG-UPDATING , and a companion /usr/ports/PKG-UPDATING or some such file more ad-hoc readable without a browser, as in the wiki... [ for instance the main browser here broke til I installed just within a few days ago, the v11 gnutls txz ... pkg install -f ... and then locked gnutls IIRC. ] ...................... _______________________________________________ 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"
