主頁 > 移動端開發 > 編譯Qualcomm的Hexagon exampls錯誤

編譯Qualcomm的Hexagon exampls錯誤

2020-09-14 06:23:33 移動端開發

在下載了Qualcomm的Hexagon SDK 351版本之后，想跑里面的examples，然后參照檔案的說，比如在examples/common/sobel3x3_v60目錄下面，先執行了SDK根目錄下面的setup_sdk_env.cmd，然后執行make tree V=hexagon_Debug_dynamic_toolv82_v65編譯命令，結果編譯錯誤，輸出如下錯誤log，

Target: hexagon
Thread model: posix
QuIC LLVM Hexagon Clang version 8.3.02 (based on LLVM 7.0.0)
InstalledDir: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin
 "F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin\\hexagon-link.exe" --hash-style=sysv -march=hexagon -mcpu=hexagonv60 -G0 -o hexagon_Release_dynamic_toolv72_v60/atomic_q F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/crt0_standalone.o F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/crt0.o F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/init.o -LF:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0 -LF:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60 -LF:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib --start-group --whole-archive -lc -lgcc -lc++ -lc++abi -lc_eh F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/target/hexagon/lib/v60/G0/libhexagon.a --no-whole-archive --end-group --dynamic-linker= -E --force-dynamic --start-group hexagon_Release_dynamic_toolv72_v60/atomic_q.o hexagon_Release_dynamic_toolv72_v60/atomic.a --end-group --start-group -lstandalone -lc -lgcc --end-group F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/fini.o
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x0): undefined reference to `pthread_mutex_lock'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x50): undefined reference to `pthread_mutex_unlock'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0xf0): undefined reference to `pthread_mutex_lock'        
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4): undefined reference to `clock_gettime'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0xe8): undefined reference to `clock_gettime'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x324): undefined reference to `pthread_getspecific'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4): undefined reference to `pthread_cond_destroy'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x18): undefined reference to `pthread_cond_signal'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x2c): undefined reference to `pthread_cond_broadcast'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4c): undefined reference to `pthread_cond_wait'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x140): undefined reference to `pthread_cond_timedwait'   
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4a8): undefined reference to `pthread_getspecific'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x1e0): undefined reference to `pthread_mutex_trylock'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x1f4): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x210): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x190): undefined reference to `pthread_getspecific'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x1ac): undefined reference to `pthread_setspecific'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x1b8): undefined reference to `pthread_getspecific'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4): undefined reference to `pthread_mutex_destroy'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x14): undefined reference to `pthread_mutex_lock'        
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x34): undefined reference to `pthread_mutex_trylock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4c): undefined reference to `pthread_mutex_unlock'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x6c): undefined reference to `pthread_mutexattr_init'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x7c): undefined reference to `pthread_mutexattr_settype' 
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x88): undefined reference to `pthread_mutex_init'        
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x9c): undefined reference to `pthread_mutexattr_destroy' 
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0xc0): undefined reference to `pthread_mutexattr_destroy' 
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0xd4): undefined reference to `pthread_mutex_destroy'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0xec): undefined reference to `pthread_mutex_destroy'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x100): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x120): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x134): undefined reference to `pthread_mutex_trylock'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x160): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x16c): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x178): undefined reference to `pthread_mutex_destroy'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x1bc): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x200): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x20): undefined reference to `pthread_join'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x54): undefined reference to `pthread_detach'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x220): undefined reference to `pthread_mutex_trylock'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x258): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x280): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x294): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x2cc): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x2d8): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x2e4): undefined reference to `pthread_mutex_destroy'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x328): undefined reference to `pthread_self'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x340): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x39c): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x3d0): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x134): undefined reference to `nanosleep'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x3ec): undefined reference to `pthread_self'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x3f4): undefined reference to `pthread_mutex_trylock'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x438): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x468): undefined reference to `pthread_mutex_lock'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x488): undefined reference to `pthread_mutex_unlock'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x8): undefined reference to `pthread_once'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x20): undefined reference to `pthread_getspecific'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x490): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4d0): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x198): undefined reference to `pthread_key_create'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x48): undefined reference to `pthread_setspecific'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x88): undefined reference to `pthread_once'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x14): undefined reference to `pthread_mutex_lock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x4f0): undefined reference to `pthread_cond_wait'        
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x510): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xac): undefined reference to `pthread_getspecific'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x58): undefined reference to `pthread_cond_wait'      
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x90): undefined reference to `pthread_mutex_unlock'   
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x51c): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x530): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x540): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x54c): undefined reference to `pthread_cond_broadcast'   
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x564): undefined reference to `pthread_mutex_lock'       
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x574): undefined reference to `pthread_mutex_unlock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++.a(.text+0x580): undefined reference to `pthread_cond_broadcast'   
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xbc): undefined reference to `pthread_key_create'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xe8): undefined reference to `pthread_setspecific'
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xc8): undefined reference to `pthread_mutex_lock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xe8): undefined reference to `pthread_mutex_unlock'   
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x28): undefined reference to `pthread_mutex_lock'     
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xf8): undefined reference to `pthread_mutex_unlock'   
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x180): undefined reference to `pthread_mutex_lock'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x23c): undefined reference to `pthread_mutex_unlock'  
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xf8): undefined reference to `pthread_cond_broadcast' 
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x130): undefined reference to `pthread_mutex_lock'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x150): undefined reference to `pthread_mutex_unlock'  
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x160): undefined reference to `pthread_cond_broadcast'Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0x58): undefined reference to `pthread_setspecific'    
Error: F:/Qualcomm/Hexagon_SDK/3.4.3/tools/HEXAGON_Tools/8.3.02/Tools/bin/../target/hexagon/lib/v60/G0/libc++abi.a(.text+0xd8): undefined reference to `pthread_key_create'     
Fatal: Linking had errors.
hexagon-clang.exe: error: hexagon-link command failed with exit code 1 (use -v to see invocation)
make[1]: *** [hexagon_Release_dynamic_toolv72_v60/atomic_q] Error 1

粗一看，顯然是缺少了對libpthread.so的依賴，第一反應就是想著看能不能添加對這個庫的依賴，后面又看了一下編譯命令，輸入make tree V=hexagon，看到提示支持的variants，發現有不同的toolv，部分如下

  hexagon_Debug_toolv72_v60
  hexagon_Debug_toolv81_v60
  hexagon_Debug_toolv81_v62
  hexagon_Debug_toolv81_v65 
  hexagon_Debug_toolv82_v60
  hexagon_Debug_toolv82_v62
  hexagon_Debug_toolv82_v65
  hexagon_Debug_toolv82_v66 
  hexagon_Debug_toolv83_v60
  hexagon_Debug_toolv83_v62
  hexagon_Debug_toolv83_v65
  hexagon_Debug_toolv83_v66

然后就想到本SDK中的tools為83版本，于是把編譯命令改為make tree V=hexagon_Debug_toolv83_v60，果然，順利編譯完成，然后又試著改為了make tree V=hexagon_Debug_toolv83_v66，也是正確的，所以，出現上述的錯誤的關鍵就是在于tools的版本不對，如果這個版本不對，比如我的編譯命令中表明需要使用82版本，而本SDK中又只有83版本，然后就找不到對應的tools，所以就會出現這樣的問題，

VSCode配置

c_cpp_properties.json檔案設定實體

{
    "configurations": [
        {
            "name": "Win32",
            "includePath": [
                "${workspaceFolder}/**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\tools\\HEXAGON_Tools\\8.3.07\\Tools\\target\\hexagon\\include\\**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\tools\\HEXAGON_Tools\\8.3.07\\Tools\\include\\**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\incs\\**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\tools\\android-ndk-r19c\\sysroot\\usr\\include\\**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\libs\\fastcv\\fastcv\\hexagon_Release_toolv83_v66\\**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\libs\\fastcv\\dspCV\\inc\\**",
                "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\libs\\fastcv\\dspCV\\hexagon_Release_dynamic_toolv83_v66\\**"
            ],
            "defines": [
                "_DEBUG",
                "UNICODE",
                "_UNICODE",
                "__hexagon__",
                "__HVX_ARCH__=66",
                "__HVX_LENGTH__=128",
                "__HVX__",
                "__HVXDBL__"
            ],
            "windowsSdkVersion": "10.0.17763.0",
            "compilerPath": "F:\\Qualcomm\\Hexagon_SDK\\3.5.1\\tools\\HEXAGON_Tools\\8.3.07\\Tools\\bin\\hexagon-clang.exe",
            "cStandard": "c11",
            "cppStandard": "c++11",
            "intelliSenseMode": "clang-x64"
        }
    ],
    "version": 4
}

轉載請註明出處，本文鏈接：https://www.uj5u.com/yidong/31655.html

標籤：Android

上一篇：android的APT技術

下一篇：Android.mk檔案LOCAL_SDK_VERSION選項

標籤雲
其他(157675) Python(38076) JavaScript(25376) Java(17977) C(15215) 區塊鏈(8255) C＃(7972) AI(7469) 爪哇(7425) MySQL(7132) html(6777) 基礎類(6313) sql(6102) 熊猫(6058) PHP(5869) 数组(5741) R(5409) Linux(5327) 反应(5209) 腳本語言(PerlPython)(5129) 非技術區(4971) Android(4554) 数据框(4311) css(4259) 节点.js(4032) C語言(3288) json(3245) 列表(3129) 扑(3119) C++語言(3117) 安卓(2998) 打字稿(2995) VBA(2789) Java相關(2746) 疑難問題(2699) 细绳(2522) 單片機工控(2479) iOS(2429) ASP.NET(2402) MongoDB(2323) 麻木的(2285) 正则表达式(2254) 字典(2211) 循环(2198) 迅速(2185) 擅长(2169) 镖(2155) 功能(1967) .NET技术(1958) Web開發(1951) python-3.x(1918) HtmlCss(1915) 弹簧靴(1913) C++(1909) xml(1889) PostgreSQL(1872) .NETCore(1853) 谷歌表格(1846) Unity3D(1843) for循环(1842)

熱門瀏覽
  • 【從零開始擼一個App】Dagger2

    Dagger2是一個IOC框架，一般用于Android平臺，第一次接觸的朋友，一定會被搞得暈頭轉向。它延續了Java平臺Spring框架代碼碎片化，注解滿天飛的傳統。嘗試將各處代碼片段串聯起來，理清思緒，真不是件容易的事。更不用說還有各版本細微的差別。 與Spring不同的是，Spring是通過反射 ......

    uj5u.com 2020-09-10 06:57:59 more
  • Flutter Weekly Issue 66

    新聞 Flutter 季度調研結果分享 教程 Flutter+FaaS一體化任務編排的思考與設計 詳解Dart中如何通過注解生成代碼 GitHub 用對了嗎？Flutter 團隊分享如何管理大型開源專案 插件 flutter-bubble-tab-indicator A Flutter librar ......

    uj5u.com 2020-09-10 06:58:52 more
  • Proguard 常用規則

    介紹 Proguard 入口，如何查看輸出，如何使用 keep 設定入口以及使用實體，如何配置壓縮，混淆，校驗等規則。

    ......

    uj5u.com 2020-09-10 06:59:00 more
  • Android 開發技術周報 Issue#292

    新聞 Android即將獲得類AirDrop功能：可向附近設備快速分享檔案 谷歌為安卓檔案管理應用引入可安全隱藏資料的Safe Folder功能 Android TV新主界面將顯示電影、電視節目和應用推薦內容 泄露的Android檔案暗示了傳說中的谷歌Pixel 5a與折疊屏新機 谷歌發布Andro ......

    uj5u.com 2020-09-10 07:00:37 more
  • AutoFitTextureView Error inflating class

    報錯： Binary XML file line #0: Binary XML file line #0: Error inflating class xxx.AutoFitTextureView 解決： <com.example.testy2.AutoFitTextureView android: ......

    uj5u.com 2020-09-10 07:00:41 more
  • 根據Uri，Cursor沒有獲取到對應的屬性

    Android： 背景：呼叫攝像頭，拍攝視頻，指定保存的地址，但是回傳的Cursor檔案，只有名稱和大小的屬性，沒有其他諸如時長，連ID屬性都沒有 使用 cursor.getInt(cursor.getColumnIndexOrThrow(MediaStore.Video.Media.DURATIO ......

    uj5u.com 2020-09-10 07:00:44 more
  • Android連載29-持久化技術

    一、持久化技術 我們平時所使用的APP產生的資料，在記憶體中都是瞬時的，會隨著斷電、關機等丟失資料，因此android系統采用了持久化技術，用于存盤這些“瞬時”資料 持久化技術包括：檔案存盤、SharedPreference存盤以及資料庫存盤，還有更復雜的SD卡記憶體儲。 二、檔案存盤 最基本存盤方式， ......

    uj5u.com 2020-09-10 07:00:47 more
  • Android Camera2Video整合到自己專案里

    背景： Android專案里呼叫攝像頭拍攝視頻，原本使用的 MediaStore.ACTION_VIDEO_CAPTURE， 后來因專案需要，改成了camera2 1.Camera2Video 官方demo有點問題，下載后，不能直接整合到專案 問題1.多次拍攝視頻崩潰 問題2.雙擊record按鈕， ......

    uj5u.com 2020-09-10 07:00:50 more
  • Android 開發技術周報 Issue#293

    新聞 谷歌為Android TV開發者提供多種新功能 Android 11將自動填表功能整合到鍵盤輸入建議中 谷歌宣布Android Auto即將支持更多的導航和數字停車應用 谷歌Pixel 5只有XL版本 搭載驍龍765G且將比Pixel 4更便宜 [圖]Wear OS將迎來重磅更新：應用啟動時間 ......

    uj5u.com 2020-09-10 07:01:38 more
  • 海豚星空掃碼投屏 Android 接收端 SDK 集成 六步驟

    掃碼投屏，開放網路，獨占設備，不需要額外下載軟體，微信掃碼，發現設備。支持標準DLNA協議，支持倍速播放。視頻，音頻，圖片投屏。好點意思。還支持自定義基于 DLNA 擴展的操作動作。好像要收費，沒體驗。 這里簡單記錄一下集成程序。 一 跟目錄的build.gradle添加私有mevan倉庫 mave ......

    uj5u.com 2020-09-10 07:01:43 more
最新发布
  • 歡迎頁輪播影片

    如圖，引導開始，球從上落下，同時淡入文字，然后文字開始輪播，最后一頁時停止，點擊進入首頁。 在來看看效果圖。 重力球先不講，主要歡迎輪播簡單實作 首先新建一個類 TextTranslationXGuideView，用于影片展示 文本是類似的，最后會有個圖片箭頭影片，布局很簡單，就是一個 TextVi ......

    uj5u.com 2023-04-20 08:40:31 more
  • 【FAQ】關于華為推送服務因營銷訊息頻次管控導致服務通訊類訊息

    一． 問題描述 使用華為推送服務下發IM訊息時，下發訊息請求成功且code碼為80000000，但是手機總是收不到訊息； 在華為推送自助分析（Beta）平臺查看發現，訊息發送觸發了頻控。 二． 問題原因及背景 2023年1月05日起，華為推送服務對咨詢營銷類訊息做了單個設備每日推送數量上限管理，具體 ......

    uj5u.com 2023-04-20 08:40:11 more
  • 歡迎頁輪播影片

    如圖，引導開始，球從上落下，同時淡入文字，然后文字開始輪播，最后一頁時停止，點擊進入首頁。 在來看看效果圖。 重力球先不講，主要歡迎輪播簡單實作 首先新建一個類 TextTranslationXGuideView，用于影片展示 文本是類似的，最后會有個圖片箭頭影片，布局很簡單，就是一個 TextVi ......

    uj5u.com 2023-04-20 08:39:36 more
  • 【FAQ】關于華為推送服務因營銷訊息頻次管控導致服務通訊類訊息

    一． 問題描述 使用華為推送服務下發IM訊息時，下發訊息請求成功且code碼為80000000，但是手機總是收不到訊息； 在華為推送自助分析（Beta）平臺查看發現，訊息發送觸發了頻控。 二． 問題原因及背景 2023年1月05日起，華為推送服務對咨詢營銷類訊息做了單個設備每日推送數量上限管理，具體 ......

    uj5u.com 2023-04-20 08:39:13 more
  • iOS從UI記憶體地址到讀取成員變數（oc/swift）

    開發除錯時，我們發現bug時常首先是從UI顯示發現例外，下一步才會去定位UI相關連的資料的。XCode有給我們提供一系列debug工具，但是很多人可能還沒有形成一套穩定的除錯流程，因此本文嘗試解決這個問題，順便提出一個暴論：UI顯示例外問題只需要兩個步驟就能完成定位作業的80%： 定位例外 UI 組 ......

    uj5u.com 2023-04-19 09:16:23 more
  • FIDE重磅更新！性能飛躍！體驗有禮！

    FIDE 開發者工具重構升級啦！實作500%性能提升，誠邀體驗！ 一直以來不少開發者朋友在社區反饋，在使用 FIDE 工具的程序中，時常會遇到諸如加載不及時、代碼預覽/渲染性能不如意的情況，十分影響開發體驗。 作為技術團隊，我們深知一件趁手的開發工具對開發者的重要性，因此，在2023年開年，FinC ......

    uj5u.com 2023-04-19 09:16:15 more
  • 游戲內嵌社區服務開放，助力開發者提升玩家互動與留存

    華為 HMS Core 游戲內嵌社區服務提供快速訪問華為游戲中心論壇能力，支持玩家直接在游戲內瀏覽帖子和交流互動，助力開發者擴展內容生產和觸達的場景。 一、為什么要游戲內嵌社區？ 二、游戲內嵌社區的典型使用場景 1、游戲內打開論壇 您可以在游戲內繪制論壇入口，為玩家提供沉浸式發帖、瀏覽、點贊、回帖、 ......

    uj5u.com 2023-04-19 09:15:46 more
  • iOS從UI記憶體地址到讀取成員變數（oc/swift）

    開發除錯時，我們發現bug時常首先是從UI顯示發現例外，下一步才會去定位UI相關連的資料的。XCode有給我們提供一系列debug工具，但是很多人可能還沒有形成一套穩定的除錯流程，因此本文嘗試解決這個問題，順便提出一個暴論：UI顯示例外問題只需要兩個步驟就能完成定位作業的80%： 定位例外 UI 組 ......

    uj5u.com 2023-04-19 09:14:53 more
  • FIDE重磅更新！性能飛躍！體驗有禮！

    FIDE 開發者工具重構升級啦！實作500%性能提升，誠邀體驗！ 一直以來不少開發者朋友在社區反饋，在使用 FIDE 工具的程序中，時常會遇到諸如加載不及時、代碼預覽/渲染性能不如意的情況，十分影響開發體驗。 作為技術團隊，我們深知一件趁手的開發工具對開發者的重要性，因此，在2023年開年，FinC ......

    uj5u.com 2023-04-19 09:14:08 more
  • 游戲內嵌社區服務開放，助力開發者提升玩家互動與留存

    華為 HMS Core 游戲內嵌社區服務提供快速訪問華為游戲中心論壇能力，支持玩家直接在游戲內瀏覽帖子和交流互動，助力開發者擴展內容生產和觸達的場景。 一、為什么要游戲內嵌社區？ 二、游戲內嵌社區的典型使用場景 1、游戲內打開論壇 您可以在游戲內繪制論壇入口，為玩家提供沉浸式發帖、瀏覽、點贊、回帖、 ......

    uj5u.com 2023-04-19 09:08:34 more

Copyright © 2010-2020 有解無憂