Markus Schatzl wrote:
On Mon, 12 23:23 , Marc Espie wrote:
As far as possible, avoid working on -current stuff using a system whose
uname still says 4.0. Even though we try to avoid it, *every release*
a few ports (mostly gnu stuff, of course) uses hardcoded release numbers
in the weirdest places, and we get breakages in the most stupid places.
I probably missed something, but I guess these errors don't
really result from not updating:
"/usr/ports/infrastructure/mk/modules.port.mk", line 31:
Malformed conditional ("" != "")
"/usr/ports/infrastructure/mk/modules.port.mk", line 31:
Malformed conditional ("" != "")
"/usr/ports/infrastructure/mk/modules.port.mk", line 54: if-less
endif
"/usr/ports/infrastructure/mk/modules.port.mk", line 54: Need an
operator
"/usr/ports/infrastructure/mk/bsd.port.mk", line 239: if-less
endif
"/usr/ports/infrastructure/mk/bsd.port.mk", line 239: Need an
operator
Fatal errors encountered -- cannot continue
I ran into the same thing. Once the system rebuilt I had to perform the
dreadful pkg_delete -q /var/db/pkg/* since the ports built on 4.0 would
not work on 4.1-beta.
This happens with every other port (e.g. transcode, bochs,
hpijs) I tried. Very simple ones with no real options like pftop
aren't affected. I had a fairly recent system (ports and src)
running on that machine while this happened.
Yesterday I updated everything (ports, src) to current, hoping
that it was just a short-term inconsistency somewhere in the
tree. But building the system anew didn't change the situation at
all.
I'd be grateful for any hints; I suspect that I'm overlooking
something here.
Thanks in advance,
/Markus
