Bug 257954

Summary: liblldb build failure (lldb-tblgen not found) on i386 stable/13
Product: Base System Reporter: John Marshall <john>
Component: binAssignee: Jessica Clarke <jrtc27>
Status: New ---    
Severity: Affects Only Me CC: arichardson, emaste, jrtc27
Priority: ---    
Version: 13.0-STABLE   
Hardware: i386   
OS: Any   

Description John Marshall 2021-08-19 20:45:01 UTC
===> lib/clang/liblldb (all)
lldb-tblgen -gen-lldb-option-defs  -I /build/src/contrib/llvm-project/lldb/source/Commands -d CommandOptions.inc.d  -o CommandOptions.inc /build/src/contrib/llvm-project/lldb/source/Commands/Options.td
make[6]: exec(lldb-tblgen) failed (No such file or directory)
*** Error code 1

make[6]: stopped in /build/src/lib/clang/liblldb
*** Error code 1

Comment 1 Jessica Clarke freebsd_committer 2021-08-20 23:56:54 UTC
What system are you building on? I assume you have a system without LLDB and are attempting to do a buildworld that includes LLDB.

This will be fixed by https://reviews.freebsd.org/D31531.
Comment 2 John Marshall 2021-08-21 00:31:41 UTC
(In reply to Jessica Clarke from comment #1)
Thanks Jessica,

Yes, that is the case. The default on the system I'm building on is WITHOUT_LLDB and the default for stable/13 is WITH_LLDB; and I have not overriden LLDB defaults in src.conf.  I realize I could mask this by setting WITHOUT_LLDB in src.conf but thought I should report it.

Here is the build/target system...

FreeBSD 11.2-RELEASE-p14 #0 r351591: Fri Aug 30 05:18:42 AEST 2019
    john@rwsrv04.gfn.riverwillow.net.au:/build/obj/john/build/src/sys/RWSRV04 i386
FreeBSD clang version 6.0.0 (tags/RELEASE_600/final 326565) (based on LLVM 6.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2800.53-MHz 686-class CPU)
  Origin="GenuineIntel"  Id=0xf33  Family=0xf  Model=0x3  Stepping=3
  TSC: P-state invariant
real memory  = 1879048192 (1792 MB)
avail memory = 1830125568 (1745 MB)
Event timer "LAPIC" quality 100
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 hardware threads

Thanks for your attention to this!