When I put 'MK_PROFILE=no' in /etc/make.conf, the devel/libublio port don't build libublio_p.a, but searchs for it on make install or make package and fails, because PROFLIB variable is set for "", not "@comment ". Putting "NO_PROFILE=true" into /etc/make.conf instead makes it work, but make warns me "use MK_PROFILE=no instead."....
Some other ports have same problem also. converters/iconv, devel/libs11n, ...
Is this perhaps a framework issue, or regression, rather than a problem of individual ports?
(In reply to Matthias Andree from comment #2) I think it has caused by lack of unified method of handling profile library which can be provided by ports in framework. Some port check NO_PROFILE variable in its port Makefile, others ask user to build proflib or not via make config, others set MAKE_ENV+= NO_PROFILE=yes in its port Makefile, but none checks MK_PROFILE variable. (I did egrep the ports tree with pattern '_p\.a$', 'PROFILE'.)
A commit references this bug: Author: mandree Date: Sat Jul 13 09:07:15 UTC 2019 New revision: 506527 URL: https://svnweb.freebsd.org/changeset/ports/506527 Log: Fix build with MK_PROFILE=no in make.conf PR: 214607 Submitted by: Yasuhito FUTATSUKI Changes: head/devel/libublio/Makefile
A commit references this bug: Author: mandree Date: Sat Jul 13 09:09:33 UTC 2019 New revision: 506528 URL: https://svnweb.freebsd.org/changeset/ports/506528 Log: Fix build with MK_PROFILE=no in make.conf MFH: r506527 Invoking blanket approval for fixing a broken build. PR: 214607 Submitted by: Yasuhito FUTATSUKI Approved by: ports-secteam (blanket) Changes: _U branches/2019Q3/ branches/2019Q3/devel/libublio/Makefile