I am building ports from sources, and upgrading www/firefox I was discouraged to see that it pulls and installs devel/llvm90 also. May be a waste of your time, but I am wondering, what pulls devel/llvm90?
And in what files in /usr/ports/www/firefox/ it is mentioned?devel/llvm90 is a build dependenciy
For I was searching mentioning llvm90 (or just llvm) in ports' directory, but found nothing, so I deinstalled llvm90 and it was rebuild again.I dont know where its written but the switch to devel/llvm90 is mentioned here: https://svnweb.freebsd.org/ports/head/www/firefox/Makefile?annotate=512440
For many recurring and more complex dependency scenarios, ports don't set dependencies directly but rely un the port system'sFor I was searching mentioning llvm90 (or just llvm) in ports' directory, but found nothing, so I deinstalled llvm90 and it was rebuild again.
USES
framework. Without looking into this particular port, llvm90 is probably pulled in by a USES=compiler
with according options -- see also /usr/ports/Mk/Uses/compiler.mk.And mesa requires llvm80 (although the system stable-11 has 80, and stable-12 has 90).
% touch test.c
% clang90 --target=amdgcn-amd-amdhsa-opencl ./test.c -o /dev/null
% clang --target=amdgcn-amd-amdhsa-opencl ./test.c -o /dev/null
error: unable to create target: 'No available targets are compatible with triple "amdgcn-amd-amdhsa-opencl"'
1 error generated.
After having a look, it's probably allvm90 is probably pulled in by a USES=compiler with according options
USE_GECKO
(see bsd.gecko.mk). LLVM_DEFAULT
is currently set to 90 in bsd.default-versions.mk, so unless you override that in your make.conf, that's the version pulled in by gecko.I suppose, I found it, it is in /usr/ports/Mk/bsd.gecko.mk.For many recurring and more complex dependency scenarios, ports don't set dependencies directly but rely un the port system'sUSES
framework. Without looking into this particular port, llvm90 is probably pulled in by aUSES=compiler
with according options -- see also /usr/ports/Mk/Uses/compiler.mk.