Hi,

I am a new user of 15.0-CURRENT and just updated my source tree and 
noticed that there are now files to be built that have the ".pico" 
extension, as a ccache user, i was enjoying fast world/kernel builds but 
these files doesn't seem to get cached to me and my world builds are 
taking long time than ever. Is there a way to skip building these 
".pico" files? Thanks in advance and thanks for your efforts and work.

I am on this commit. 6014596899c

On 4/26/25 7:06 PM, Dimitry Andric wrote:
> Hi,
>
> In https://cgit.freebsd.org/src/commit/?id=2e47f35be5dc I committed a
> change to convert libllvm, libclang, and liblldb into private shared
> libraries. This means that tools like clang, lld, lldb, and more are now
> quite a bit smaller, as all the common functionality is located in those
> shared libraries.
>
> Note that these shared libraries are not the same as upstream's, and are
> _not_ ABI compatible, which is why they are installed as private shared
> libraries. If you need ABI compatibility and/or the llvm-config tools,
> please use one of the devel/llvm ports.
>
> This affects the following binaries in the base system (some of them
> only exist if they're enabled through various WITH_XXX options):
>
> - addr2line
> - ar
> - bugpoint
> - c++
> - c++filt
> - cc
> - clang
> - clang++
> - clang-cpp
> - clang-format
> - cpp
> - gcov
> - ld.lld
> - llc
> - lldb
> - lldb-server
> - lli
> - llvm-addr2line
> - llvm-ar
> - llvm-as
> - llvm-bcanalyzer
> - llvm-cov
> - llvm-cxxdump
> - llvm-cxxfilt
> - llvm-diff
> - llvm-dis
> - llvm-dwarfdump
> - llvm-dwarfutil
> - llvm-dwp
> - llvm-extract
> - llvm-link
> - llvm-lto
> - llvm-lto2
> - llvm-mc
> - llvm-mca
> - llvm-modextract
> - llvm-nm
> - llvm-objcopy
> - llvm-objdump
> - llvm-pdbutil
> - llvm-profdata
> - llvm-ranlib
> - llvm-readelf
> - llvm-readobj
> - llvm-rtdyld
> - llvm-size
> - llvm-strings
> - llvm-strip
> - llvm-symbolizer
> - llvm-xray
> - nm
> - objcopy
> - objdump
> - opt
> - ranlib
> - readelf
> - size
> - strings
> - strip
>
> In addition, all these executables are now position independent (PIE).
>
> Please let me know if you encounter any problems resulting due to this
> change, as I intend to MFC it. For example, I tried covering all
> incremental build scenarios, but I may have missed some corner case.
>
> -Dimitry
>
>


Reply via email to