Open TommyJerryMairo opened 3 years ago
The builder environment is openSUSE Leap 15.2
:
NAME="openSUSE Leap"
VERSION="15.2"
ID="opensuse-leap"
ID_LIKE="suse opensuse"
VERSION_ID="15.2"
PRETTY_NAME="openSUSE Leap 15.2"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:leap:15.2"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org/
The builder runs on Intel Xeon E5-2698 v3
:
processor : 63
vendor_id : GenuineIntel
cpu family : 6
model : 63
model name : Intel(R) Xeon(R) CPU E5-2698 v3 @ 2.30GHz
stepping : 2
microcode : 0x46
cpu MHz : 1200.852
cache size : 40960 KB
physical id : 1
siblings : 32
core id : 15
cpu cores : 16
apicid : 63
initial apicid : 63
fpu : yes
fpu_exception : yes
cpuid level : 15
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc dtherm ida arat pln pts md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit
bogomips : 4596.22
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
Both libogg.a
and libogg.la
are in place:
tjm@Builder_xstvd:ffmpeg-build-script$ ls workspace/lib64/libogg.*
workspace/lib64/libogg.a workspace/lib64/libogg.la*
This issue is caused by using workspace/lib
in configure command line options, where the actual install path is workspace/lib64
. I suggest the script creates a soft link of workspace/lib
with name workspace/lib64
I've encountered a weird error when
./build-ffmpeg --build
:It seems there might be a dependency or build order issue. Or the configure file of libvorbis doesn't recognized the static build of libogg. Full log comes below: