Not sure, what is wrong, but my attempts to (re)build the port are failing at configure-stage: # make ===> qt5-buildtools-5.9.4 depends on package: pkgconf>=1.3.0_1 - found ===> qt5-buildtools-5.9.4 depends on file: /opt/lib/qt5/bin/qmake - found ===> qt5-buildtools-5.9.4 depends on package: perl5>=5.26<5.27 - found ===> qt5-buildtools-5.9.4 depends on file: /opt/bin/ccache - found ===> Configuring for qt5-buildtools-5.9.4 /bin/mkdir -p /var/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.9.4 echo 'CMAKE_MODULE_TESTS = -' > /var/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.9.4/.qmake.cache echo 'QMAKE_LIBDIR_FLAGS = -L/var/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.9.4/lib' >> /var/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.9.4/.qmake.cache ***Unknown option -- Usage: /var/ports/devel/qt5-buildtools/work/qtbase-opensource-src-5.9.4/bin/qmake [mode] [options] [files] QMake has two modes, one mode for generating project files based on some heuristics, and the other for generating makefiles. Normally you shouldn't need to specify a mode, as makefile generation is the default mode for qmake, but you may use this to test qmake on an existing project Mode: -project Put qmake into project file generation mode In this mode qmake interprets files as files to [....] The only obvious "deviation from norm" on my system is that LOCALBASE (and, consequently, PREFIX) are set to "/opt" rather than "/usr/local". Please, advise.
Hi Mikhail I don't even get to qt5-buildtools with PREFIX=LOCALBASE:=/opt mfg Tobias
(In reply to Tobias C. Berner from comment #1) > I don't even get to qt5-buildtools with PREFIX=LOCALBASE:=/opt At the end of December, when I was setting this new machine up for the first time, I had no problem building the entire KDE and other ports with LOCALBASE set to /opt. Now I can't upgrade this and that... Something must've rotted in a fairly short time.
After forcibly rebuilding qt5-qmake, I was able to build this port...