ports: pkg-static: "x86_64-unknown-freebsd" versus "x86_64-portbld-freebsd"

O. Hartmann ohartmann at walstatt.org
Sun Oct 15 16:37:58 UTC 2017


A port (lang/pocl), of which I am the official maintainer, fails to build with recent
12-CURRENT and recent 11-STABLE:

[...]
===>   Registering installation for pocl-0.14
pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-avx.bc:No
such file or directory pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-avx2.bc:No
such file or directory pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-avx512.bc:No
such file or directory pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-avx_fma4.bc:No
such file or directory pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-sse2.bc:No
such file or directory pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-sse41.bc:No
such file or directory pkg-static: Unable to access
file /usr/ports/lang/pocl/work/stage/usr/local/share/pocl/kernel-x86_64-unknown-freebsd12.0-ssse3.bc:No
such file or directory *** Error code 74

The reason seems that on recent systems, in the staging folders, the files in question
have been build as 

[...]
find ./ -name "*freebsd12.0-avx.bc" -print
./work/stage/usr/local/share/pocl/kernel-x86_64-portbld-freebsd12.0-avx.bc
./work/pocl-0.14/lib/kernel/host/kernel-x86_64-portbld-freebsd12.0-avx.bc

so it seems to me as "unknown" gets replaced by "portbld". Performing a

make makeplist

indicates also, that recent build system is taking the "portbld" instead of the
"unknown" (/usr/ports is at revision 452155, CURRENT is at FreeBSD 12.0-CURRENT #276
r324621 amd64 and so is the jail I test building lang/pocl within).

Can someone shed some light on this? It would be simple to patch via diff the new
pkg-plist file, but I fear the problem indicates something more deeper in some changes
for the Mk files.

Thanks in advance,
Oliver
-- 
O. Hartmann

Ich widerspreche der Nutzung oder Übermittlung meiner Daten für
Werbezwecke oder für die Markt- oder Meinungsforschung (§ 28 Abs. 4 BDSG).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 313 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20171015/a9f28a88/attachment.sig>


More information about the freebsd-ports mailing list