On 4 Oct 2023, at 14:46, Robert Huff <roberth...@rcn.com> wrote: > > > [I sent a version of this to ports@ ... had no response > ... trying here because there's now a large back log of ports > updates.] > > Hello: > On a system running: > > FreeBSD 14.0-CURRENT #0 main-f0a15aafcb > Mon Oct 31 08:19:54 EDT 2022 > amd64 > > with the ports tree updated nightly, I suddenly have a problen > building ports. > Sample case: > > root@> pd /usr/ports/www/chromium/ > root@> make clean > make[2]: "/usr/ports/Mk/Uses/objc.mk" line 57: String comparison operator > must be either == or != > make[2]: Fatal errors encountered -- cannot continue > ===> Cleaning for chromium-117.0.5938.132_1
My guess is that your ports tree is corrupted, or partially updated. The way ports works, the whole tree has to be atomically updated, and you cannot do partial checkouts or modifications (at least not without jumping through hoops, and knowing how to fix fallout). What does "cd /usr/ports && git status" say? -Dimitry
signature.asc
Description: Message signed with OpenPGP
