活动介绍

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.000 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 44 Microsoft (R) Windows Debugger Version 10.0.27829.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\071525-14000-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 26100 MP (32 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Kernel base = 0xfffff803`85000000 PsLoadedModuleList = 0xfffff803`85ef4420 Debug session time: Tue Jul 15 17:28:19.638 2025 (UTC + 8:00) System Uptime: 0 days 0:17:31.281 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................ Loading User Symbols Loading unloaded module list ............................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`85487cc0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffc881`cabadb10=0000000000000101 8: kd> !analyze -v Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ............................................ Loading User Symbols Loading unloaded module list ............................. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000006, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffc881ca7a4180, The PRCB address of the hung processor. Arg4: 0000000000000002, The index of the hung processor. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1796 Key : Analysis.Elapsed.mSec Value: 10236 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 23 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 359 Key : Analysis.Init.Elapsed.mSec Value: 11295 Key : Analysis.Memory.CommitPeak.Mb Value: 103 Key : Analysis.Version.DbgEng Value: 10.0.27829.1001 Key : Analysis.Version.Description Value: 10.2503.24.01 amd64fre Key : Analysis.Version.Ext Value: 1.2503.24.1 Key : Bugcheck.Code.LegacyAPI Value: 0x101 Key : Bugcheck.Code.TargetModel Value: 0x101 Key : Dump.Attributes.AsUlong Value: 0x21008 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0x0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 Key : Failure.Bucket Value: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks Key : Failure.Hash Value: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e} Key : Stack.Pointer Value: ISR BUGCHECK_CODE: 101 BUGCHECK_P1: 6 BUGCHECK_P2: 0 BUGCHECK_P3: ffffc881ca7a4180 BUGCHECK_P4: 2 FILE_IN_CAB: 071525-14000-01.dmp DUMP_FILE_ATTRIBUTES: 0x21008 Kernel Generated Triage Dump FAULTING_THREAD: ffff9a8ea34b5040 FAULTING_PROCESSOR: 2 PROCESS_NAME: System BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 STACK_TEXT: ffffc881`cabadb08 fffff803`852d6b0f : 00000000`00000101 00000000`00000006 00000000`00000000 ffffc881`ca7a4180 : nt!KeBugCheckEx ffffc881`cabadb10 fffff803`852f3e48 : 00000000`00000000 ffffc881`cab9a700 ffffc881`cab91180 ffffc881`cab91180 : nt!KeAccumulateTicks+0x6bf ffffc881`cabadb80 fffff803`852f3a39 : 00000000`00000020 00000000`00000000 00000002`729cec98 fffff780`00000350 : nt!KiUpdateRunTime+0xa8 ffffc881`cabadbe0 fffff803`852f2eff : 00000000`00000000 00000000`00000000 00000000`0000000f ffffc881`cab9a860 : nt!KiUpdateTime+0x469 ffffc881`cabade40 fffff803`852f214f : fffff803`85f8da48 ffff9a8e`77798c40 00000000`00000000 ffffc881`cab91180 : nt!KeClockInterruptNotify+0x18f ffffc881`cabadf50 fffff803`8565d6ae : 00000269`20bd783f ffff9a8e`77798c40 00000002`72e3330e 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x2df ffffc881`cabadfb0 fffff803`8565debc : 00000002`72e31f6a ffff8485`843b6c20 00000002`72e31f74 00000262`f85b278e : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e ffff8485`843b6ba0 fffff803`852491c2 : 00000000`00000002 00000000`00000001 ffffc881`cab91180 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw+0x3c ffff8485`843b6d30 fffff803`85248e95 : ffff9a8e`77824180 ffff8485`843b6e60 ffff9a8e`77824190 fffff803`00000000 : nt!KiIpiWaitForRequestBarrier+0x32 ffff8485`843b6d60 fffff803`8528dd39 : 00000000`00001000 00000000`00000000 00000000`00000001 ffffaaed`40f2a1c0 : nt!MiFlushTbList+0x885 ffff8485`843b6f70 fffff803`8528d51b : ffffda81`e5438000 00000000`ea932801 0000001c`00000000 00000000`00000004 : nt!MmSetAddressRangeModifiedEx+0x4a9 ffff8485`843b7010 fffff803`85288773 : ffff9a8e`812135c0 00000000`00000000 ffff8485`843b7200 ffff8485`843b7300 : nt!CcFlushCacheOneRange+0x1ab ffff8485`843b7100 fffff803`85288ab4 : 00000000`00000000 ffff9a8e`8109a818 00000000`00000000 ffff9a8e`8109a6e0 : nt!CcWriteBehindAsync+0x127 ffff8485`843b7270 fffff803`852882d7 : ffff9a8e`8109a79c 00000000`00000000 ffff9a8e`8109a818 ffff9a8e`778a5720 : nt!CcAsyncLazywriteWorker+0x1e4 ffff8485`843b7360 fffff803`8527f6e9 : ffff9a8e`a34b5040 ffff8485`843b74c0 fffff803`85288260 ffff9a8e`81213bb0 : nt!CcAsyncLazywriteWorkerThread+0x77 ffff8485`843b73c0 fffff803`8541d24a : ffff9a8e`a34b5040 ffff9a8e`a34b5040 fffff803`8527f540 ffff9a8e`7773fb20 : nt!ExpWorkerThread+0x1a9 ffff8485`843b7570 fffff803`8565c664 : ffffc881`caa59180 ffff9a8e`a34b5040 fffff803`8541d1f0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a ffff8485`843b75c0 00000000`00000000 : ffff8485`843b8000 ffff8485`843b1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: nt!KeAccumulateTicks+6bf MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.26100.1 STACK_COMMAND: .process /r /p 0xffff9a8e776ee040; .thread 0xffff9a8ea34b5040 ; kb BUCKET_ID_FUNC_OFFSET: 6bf FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f9e2f3e5-5717-d66f-239c-7b2e10a43f9e} Followup: MachineOwner --------- 这个问题怎么解决

时间: 2025-07-15 21:15:05 浏览: 19
<think>嗯,用户遇到了Windows蓝屏错误CLOCK_WATCHDOG_TIMEOUT(0x101),需要专业级的解决方案。这个错误属于硬件相关的严重系统崩溃,通常意味着处理器线程响应超时,可能涉及硬件故障、驱动不兼容或系统设置问题。 用户提到nt!KeAccumulateTicks调用导致的问题,这指向了Windows内核的时间管理机制。看来用户已经有一定调试经验,可能正在使用WinDbg分析内存转储文件。需要从软硬件两个维度提供系统化的排查方案。 硬件方面要重点考虑三点:处理器状态(尤其是超频和散热)、内存稳定性(时钟同步问题)、电源供应质量。软件层面则要关注核心驱动(如芯片组、显卡、存储控制器)和系统更新的兼容性。有趣的是,某些防病毒软件的实时监控功能也可能意外触发此类超时。 考虑到用户正在调试,应该强调内存转储分析的关键步骤:首先用!sysinfo cpuinfo确认CPU拓扑结构,再用!running -ti检查所有处理器线程的阻塞状态。如果发现某个核心上的线程长期占用资源(如显示Running for 3000+ ticks),就能准确定位故障核心。 对于时间紧迫的用户,建议优先尝试"禁用C状态"和"关闭超线程"这两个立竿见影的方案。虽然会影响能效和性能,但能快速验证是否硬件问题。如果用户系统支持,还可以指导他们临时关闭Intel Turbo Boost或AMD Precision Boost功能。 最后需要提醒备份策略——这个错误有较高风险导致数据损坏,特别是在排查过程中可能多次触发蓝屏。应该强调在安全模式下操作的必要性,毕竟反复崩溃可能损坏文件系统。</think>以下是针对Windows蓝屏错误 `CLOCK_WATCHDOG_TIMEOUT (0x101)` 的深度分析与解决方案,尤其针对 `nt!KeAccumulateTicks` 相关的处理器中断超时问题: --- ### **错误本质分析** 该错误表明**某个处理器核心未能在规定时间内响应时钟中断**(通常阈值≈5秒),核心逻辑被判定为"冻结"。触发点 `nt!KeAccumulateTicks` 是Windows内核的时间计数器更新函数,其阻塞意味着: 1. **硬件层面**:CPU核心物理故障(如过热、电压不稳) 2. **软件层面**:内核级驱动或固件死锁CPU核心 3. **系统配置**:超频/节能设置导致时钟信号异常 --- ### **排查流程图** ```mermaid graph TD A[CLOCK_WATCHDOG_TIMEOUT] --> B{是否可进入系统?} B -->|是| C[分析内存转储文件] B -->|否| D[安全模式/UEFI测试] C --> E[定位阻塞线程] D --> F[硬件压力测试] E --> G[更新/回滚驱动] F --> H[检查CPU温度/电压] G --> I[验证修复] H --> I ``` --- ### **关键解决步骤** #### **1. 内存转储分析 (WinDbg)** ```bash # 加载转储文件 .load kd !analyze -v # 检查CPU阻塞状态 !running -ti # 显示所有CPU线程运行时间 !irql # 查看中断请求级别 # 定位nt!KeAccumulateTicks上下文 knL # 显示阻塞线程的调用栈 lmvm acpi.sys # 检查ACPI驱动版本(常见冲突源) ``` - **重点观察**:若某CPU线程显示 `Running for XXXX ticks`(X值极大),表明该核心被死锁[^1]。 #### **2. 硬件诊断** - **温度监控**:使用 `HWMonitor` 检查CPU核心温度(>95°C可能触发) - **内存测试**:运行 `memtest86+` 至少4轮(时钟同步依赖内存稳定性) - **电源测试**:更换电源或使用 `OCCT` 进行12V电压波动测试(±5%为临界值) #### **3. 驱动/固件更新** ```powershell # PowerShell获取问题驱动列表 Get-WinEvent -FilterHashtable @{LogName="System"; ID="41"} | Where-Object {$_.Message -match "0x101"} | Format-List -Property * ``` - **强制更新**:芯片组驱动、存储控制器驱动、ACPI.sys - **BIOS/UEFI**:禁用 `C-States` 和 `SpeedStep`(临时测试) #### **4. 高级修复方案** - **禁用核心隔离**: ```reg [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard] "EnableVirtualizationBasedSecurity"=dword:00000000 ``` - **调整时钟中断策略**(注册表): ```reg [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager] "InterruptTimeAdjustment"=dword:00000001 # 禁用动态调整 ``` - **关闭超线程**(UEFI设置):对老旧CPU尤其有效 --- ### **预防措施** 1. **电源管理**:控制面板 → 电源选项 → 启用"高性能"模式 2. **中断平衡**:使用 `MSI Utility` 强制设备使用MSI中断模式 3. **固件锁定**:在UEFI中固定CPU电压(Offset模式优于Auto) > ⚠️ **紧急处理**:若频繁蓝屏无法进入系统,在UEFI中**禁用所有CPU C-State节能选项**可临时恢复运行。 ---
阅读全文

相关推荐

Microsoft Windows [版本 10.0.19045.4170] (c) Microsoft Corporation。保留所有权利。 C:\Users\Administrator>pip install chainer cupy Requirement already satisfied: chainer in f:\play_bird\lib\site-packages (7.8.1) Collecting cupy Downloading cupy-13.4.1.tar.gz (3.5 MB) ---------------------------------------- 3.5/3.5 MB 7.7 MB/s eta 0:00:00 Preparing metadata (setup.py) ... done Requirement already satisfied: setuptools in f:\play_bird\lib\site-packages (from chainer) (75.1.0) Requirement already satisfied: typing-extensions in f:\play_bird\lib\site-packages (from chainer) (4.11.0) Requirement already satisfied: filelock in f:\play_bird\lib\site-packages (from chainer) (3.13.1) Requirement already satisfied: numpy>=1.9.0 in f:\play_bird\lib\site-packages (from chainer) (1.26.4) Requirement already satisfied: protobuf>=3.0.0 in f:\play_bird\lib\site-packages (from chainer) (4.25.3) Requirement already satisfied: six>=1.9.0 in f:\play_bird\lib\site-packages (from chainer) (1.16.0) Collecting fastrlock>=0.5 (from cupy) Using cached fastrlock-0.8.3-cp312-cp312-win_amd64.whl.metadata (7.9 kB) Using cached fastrlock-0.8.3-cp312-cp312-win_amd64.whl (31 kB) Building wheels for collected packages: cupy Building wheel for cupy (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [59 lines of output] Generating cache key from header files... Cache key (1729 files matching C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\cupy\_core\include\**): 62426478e3e7017e0abfdd71b0667fdffa294302 Clearing directory: C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\cupy\.data Looking for NVTX: C:\Program Files\NVIDIA Corporation\Nsight Systems *\target-windows-x64\nvtx NVTX could not be found -------- Configuring Module: cuda -------- Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ ************************************************** *** WARNING: Cannot check compute capability Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ ************************************************** ************************************************************ * CuPy Configuration Summary * ************************************************************ Build Environment: Include directories: ['C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include\\cupy/_cccl/libcudacxx', 'C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include\\cupy/_cccl/thrust', 'C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include\\cupy/_cccl/cub', 'C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include'] Library directories: [] nvcc command : (not found) hipcc command : (not found) Environment Variables: CFLAGS : (none) LDFLAGS : (none) LIBRARY_PATH : (none) CUDA_PATH : (none) NVCC : (none) HIPCC : (none) ROCM_HOME : (none) Modules: cuda : No -> Include files not found: ['cublas_v2.h', 'cuda.h', 'cuda_profiler_api.h', 'cuda_runtime.h', 'cufft.h', 'curand.h', 'cusparse.h'] -> Check your CFLAGS environment variable. ERROR: CUDA could not be found on your system. HINT: You are trying to build CuPy from source, which is NOT recommended for general use. Please consider using binary packages instead. Please refer to the Installation Guide for details: https://docs.cupy.dev/en/stable/install.html ************************************************************ Traceback (most recent call last): File "<string>", line 2, in <module> File "", line 34, in <module> File "C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\setup.py", line 85, in <module> ext_modules = cupy_setup_build.get_ext_modules(True, ctx) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\install\cupy_builder\cupy_setup_build.py", line 531, in get_ext_modules extensions = make_extensions(ctx, compiler, use_cython) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\install\cupy_builder\cupy_setup_build.py", line 380, in make_extensions raise Exception('Your CUDA environment is invalid. ' Exception: Your CUDA environment is invalid. Please check above error log. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for cupy Running setup.py clean for cupy error: subprocess-exited-with-error × python setup.py clean did not run successfully. │ exit code: 1 ╰─> [59 lines of output] Generating cache key from header files... Cache key (1729 files matching C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\cupy\_core\include\**): 62426478e3e7017e0abfdd71b0667fdffa294302 Clearing directory: C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\cupy\.data Looking for NVTX: C:\Program Files\NVIDIA Corporation\Nsight Systems *\target-windows-x64\nvtx NVTX could not be found -------- Configuring Module: cuda -------- Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ ************************************************** *** WARNING: Cannot check compute capability Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ ************************************************** ************************************************************ * CuPy Configuration Summary * ************************************************************ Build Environment: Include directories: ['C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include\\cupy/_cccl/libcudacxx', 'C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include\\cupy/_cccl/thrust', 'C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include\\cupy/_cccl/cub', 'C:\\Users\\Administrator\\AppData\\Local\\Temp\\pip-install-5_cp926o\\cupy_a57567a6d5fe4490aab527740d305b7d\\cupy/_core/include'] Library directories: [] nvcc command : (not found) hipcc command : (not found) Environment Variables: CFLAGS : (none) LDFLAGS : (none) LIBRARY_PATH : (none) CUDA_PATH : (none) NVCC : (none) HIPCC : (none) ROCM_HOME : (none) Modules: cuda : No -> Include files not found: ['cublas_v2.h', 'cuda.h', 'cuda_profiler_api.h', 'cuda_runtime.h', 'cufft.h', 'curand.h', 'cusparse.h'] -> Check your CFLAGS environment variable. ERROR: CUDA could not be found on your system. HINT: You are trying to build CuPy from source, which is NOT recommended for general use. Please consider using binary packages instead. Please refer to the Installation Guide for details: https://docs.cupy.dev/en/stable/install.html ************************************************************ Traceback (most recent call last): File "<string>", line 2, in <module> File "", line 34, in <module> File "C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\setup.py", line 85, in <module> ext_modules = cupy_setup_build.get_ext_modules(True, ctx) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\install\cupy_builder\cupy_setup_build.py", line 531, in get_ext_modules extensions = make_extensions(ctx, compiler, use_cython) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Users\Administrator\AppData\Local\Temp\pip-install-5_cp926o\cupy_a57567a6d5fe4490aab527740d305b7d\install\cupy_builder\cupy_setup_build.py", line 380, in make_extensions raise Exception('Your CUDA environment is invalid. ' Exception: Your CUDA environment is invalid. Please check above error log. [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed cleaning build dir for cupy Failed to build cupy ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (cupy) C:\Users\Administrator>

Preparing metadata (setup.py) ... error error: subprocess-exited-with-error × python setup.py egg_info did not run successfully. │ exit code: 1 ╰─> [84 lines of output] C:\ProgramData\mambaforge\lib\site-packages\setuptools\dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) C:\ProgramData\mambaforge\lib\site-packages\setuptools\dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'author-email' will not be supported in future versions. Please use the underscore name 'author_email' instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) C:\ProgramData\mambaforge\lib\site-packages\setuptools\dist.py:476: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'home-page' will not be supported in future versions. Please use the underscore name 'home_page' instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) C:\ProgramData\mambaforge\lib\site-packages\setuptools\__init__.py:81: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try pip install --use-pep517. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) C:\ProgramData\mambaforge\lib\site-packages\setuptools\command\develop.py:40: EasyInstallDeprecationWarning: easy_install command is deprecated. !! ******************************************************************************** Please avoid running setup.py and easy_install. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://github.com/pypa/setuptools/issues/917 for details. ******************************************************************************** !! easy_install.initialize_options(self) C:\ProgramData\mambaforge\lib\site-packages\setuptools\_distutils\cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running setup.py directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() error in setup command: 'tests_require' must be a string or list of strings containing valid project/version requirement specifiers; Expected end or semicolon (after version specifier) pytz>=2010h ~~~~~~^ [end of output] note: This error originates from a subprocess, and is likely not a problem with pip.

Collecting frozenlist==1.4.0 Using cached frozenlist-1.4.0.tar.gz (90 kB) Installing build dependencies: started Installing build dependencies: finished with status 'done' Getting requirements to build wheel: started Getting requirements to build wheel: finished with status 'done' Preparing metadata (pyproject.toml): started Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: frozenlist Building wheel for frozenlist (pyproject.toml): started Building wheel for frozenlist (pyproject.toml): finished with status 'error' Failed to build frozenlist error: subprocess-exited-with-error Building wheel for frozenlist (pyproject.toml) did not run successfully. exit code: 1 [44 lines of output] C:\Users\长江三峡\AppData\Local\Temp\pip-build-env-j0vgs8vf\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: Apache Software License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() ********************* * Accelerated build * ********************* running bdist_wheel running build running build_py creating build\lib.win-amd64-cpython-312\frozenlist copying frozenlist\__init__.py -> build\lib.win-amd64-cpython-312\frozenlist running egg_info writing frozenlist.egg-info\PKG-INFO writing dependency_links to frozenlist.egg-info\dependency_links.txt writing top-level names to frozenlist.egg-info\top_level.txt reading manifest file 'frozenlist.egg-info\SOURCES.txt' reading manifest templa

Using cached https://pypi.tuna.tsinghua.edu.cn/packages/1a/d5/91492007e786a7fbcbba8423cd3637ea9311c4844aaf753d8e2ba086e48a/pyemd-1.0.0.tar.gz (87 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Collecting numpy>=1.9.0 (from pyemd) Using cached https://pypi.tuna.tsinghua.edu.cn/packages/b1/3e/e28f4c1dd9e042eb57a3eb652f200225e311b608632bc727ae378623d4f8/numpy-2.3.1-cp312-cp312-win_amd64.whl (12.7 MB) Building wheels for collected packages: pyemd Building wheel for pyemd (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for pyemd (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [72 lines of output] C:\Users\张秋宇\AppData\Local\Temp\pip-build-env-rmjv8_9_\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: project.license as a TOML table is deprecated !! ******************************************************************************** Please use a simple string containing a SPDX expression for project.license. You can also use project.license-files. (Both options available on setuptools>=77.0.0). By 2026-Feb-18, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! corresp(dist, value, root_dir) C:\Users\张秋宇\AppData\Local\Temp\pip-build-env-rmjv8_9_\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following clas

pip install spidev Collecting spidev Using cached spidev-3.6.tar.gz (11 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: spidev Building wheel for spidev (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for spidev (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [20 lines of output] C:\Users\ 123\AppData\Local\Temp\pip-build-env-9e35mysz\overlay\Lib\site-packages\setuptools\dist.py:493: SetuptoolsDeprecationWarning: Invalid dash-separated options !! ******************************************************************************** Usage of dash-separated 'description-file' will not be supported in future versions. Please use the underscore name 'description_file' instead. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! opt = self.warn_dash_deprecation(opt, section) running bdist_wheel running build running build_ext building 'spidev' extension error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for spidev Failed to build spidev ERROR: Failed to build installable wheels for some pyproject.toml based projects (spidev) C:\Users\ 123>pip install spidev Collecting spidev Using cached spidev-3.6.tar.gz (11 kB) Installing build dependencies ... done

pip install mgrs Collecting mgrs Downloading mgrs-1.5.0.tar.gz (31 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: mgrs Building wheel for mgrs (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for mgrs (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [68 lines of output] C:\Users\HP\AppData\Local\Temp\pip-build-env-1she0k13\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: project.license as a TOML table is deprecated !! ******************************************************************************** Please use a simple string containing a SPDX expression for project.license. You can also use project.license-files. (Both options available on setuptools>=77.0.0). By 2026-Feb-18, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! corresp(dist, value, root_dir) C:\Users\HP\AppData\Local\Temp\pip-build-env-1she0k13\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! dist._finalize_license_expression() C:\Users\HP\AppData\Local\Temp\pip-build-env-1she0k13\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build\lib.win-amd64-cpython-313\mgrs copying mgrs\core.py -> build\lib.win-amd64-cpython-313\mgrs copying mgrs\__init__.py -> build\lib.win-amd64-cpython-313\mgrs running egg_info writing mgrs.egg-info\PKG-INFO writing dependency_links to mgrs.egg-info\dependency_links.txt writing top-level names to mgrs.egg-info\top_level.txt reading manifest file 'mgrs.egg-info\SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'mgrs.egg-info\SOURCES.txt' creating build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\mgrs.c -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\mgrs.h -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\polarst.c -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\polarst.h -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\tranmerc.c -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\tranmerc.h -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\ups.c -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\ups.h -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\utm.c -> build\lib.win-amd64-cpython-313\libmgrs copying libmgrs\utm.h -> build\lib.win-amd64-cpython-313\libmgrs running build_ext building 'libmgrs' extension error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for mgrs Failed to build mgrs ERROR: Failed to build installable wheels for some pyproject.toml based projects (mgrs)

(rdt) qfw@LAPTOP-IQ27EG3H:~/RoboticsDiffusionTransformer$ pip install flash-attn --no-build-isolation Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Collecting flash-attn Downloading https://pypi.tuna.tsinghua.edu.cn/packages/11/34/9bf60e736ed7bbe15055ac2dab48ec67d9dbd088d2b4ae318fd77190ab4e/flash_attn-2.7.4.post1.tar.gz (6.0 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.0/6.0 MB 8.2 MB/s eta 0:00:00 Preparing metadata (setup.py) ... done Requirement already satisfied: torch in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from flash-attn) (2.1.0) Collecting einops (from flash-attn) Downloading https://pypi.tuna.tsinghua.edu.cn/packages/87/62/9773de14fe6c45c23649e98b83231fffd7b9892b6cf863251dc2afa73643/einops-0.8.1-py3-none-any.whl (64 kB) Requirement already satisfied: filelock in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (3.18.0) Requirement already satisfied: typing-extensions in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (4.13.2) Requirement already satisfied: sympy in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (1.14.0) Requirement already satisfied: networkx in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (3.4.2) Requirement already satisfied: jinja2 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (3.1.6) Requirement already satisfied: fsspec in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (2025.3.2) Requirement already satisfied: nvidia-cuda-nvrtc-cu12==12.1.105 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (12.1.105) Requirement already satisfied: nvidia-cuda-runtime-cu12==12.1.105 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (12.1.105) Requirement already satisfied: nvidia-cuda-cupti-cu12==12.1.105 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (12.1.105) Requirement already satisfied: nvidia-cudnn-cu12==8.9.2.26 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (8.9.2.26) Requirement already satisfied: nvidia-cublas-cu12==12.1.3.1 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (12.1.3.1) Requirement already satisfied: nvidia-cufft-cu12==11.0.2.54 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (11.0.2.54) Requirement already satisfied: nvidia-curand-cu12==10.3.2.106 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (10.3.2.106) Requirement already satisfied: nvidia-cusolver-cu12==11.4.5.107 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (11.4.5.107) Requirement already satisfied: nvidia-cusparse-cu12==12.1.0.106 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (12.1.0.106) Requirement already satisfied: nvidia-nccl-cu12==2.18.1 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (2.18.1) Requirement already satisfied: nvidia-nvtx-cu12==12.1.105 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (12.1.105) Requirement already satisfied: triton==2.1.0 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from torch->flash-attn) (2.1.0) Requirement already satisfied: nvidia-nvjitlink-cu12 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from nvidia-cusolver-cu12==11.4.5.107->torch->flash-attn) (12.9.41) Requirement already satisfied: MarkupSafe>=2.0 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from jinja2->torch->flash-attn) (3.0.2) Requirement already satisfied: mpmath<1.4,>=1.1.0 in /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages (from sympy->torch->flash-attn) (1.3.0) Building wheels for collected packages: flash-attn DEPRECATION: Building 'flash-attn' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of 'flash-attn'. Discussion can be found at https://github.com/pypa/pip/issues/6334 Building wheel for flash-attn (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [31 lines of output] torch.__version__ = 2.1.0+cu121 /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages/setuptools/__init__.py:94: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try pip install --use-pep517. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) /home/qfw/miniconda3/envs/rdt/lib/python3.10/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel Guessing wheel URL: https://github.com/Dao-AILab/flash-attention/releases/download/v2.7.4.post1/flash_attn-2.7.4.post1+cu12torch2.1cxx11abiFALSE-cp310-cp310-linux_x86_64.whl error: Remote end closed connection without response [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for flash-attn Running setup.py clean for flash-attn Failed to build flash-attn ERROR: Failed to build installable wheels for some pyproject.toml based projects (flash-attn)遇到这个问题怎么解决?

Collecting gpiod Using cached gpiod-2.3.0.tar.gz (57 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: gpiod Building wheel for gpiod (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for gpiod (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [61 lines of output] C:\Users\11867\AppData\Local\Temp\pip-build-env-d8os6egt\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:82: SetuptoolsDeprecationWarning: project.license as a TOML table is deprecated !! ******************************************************************************** Please use a simple string containing a SPDX expression for project.license. You can also use project.license-files. (Both options available on setuptools>=77.0.0). By 2026-Feb-18, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! corresp(dist, value, root_dir) C:\Users\11867\AppData\Local\Temp\pip-build-env-d8os6egt\overlay\Lib\site-packages\setuptools\config\_apply_pyprojecttoml.py:61: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: GNU Lesser General Public License v2 or later (LGPLv2+) See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! dist._finalize_license_expression() C:\Users\11867\AppData\Local\Temp\pip-build-env-d8os6egt\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: GNU Lesser General Public License v2 or later (LGPLv2+) See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build\lib.win-amd64-cpython-39\gpiod copying gpiod\chip.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\chip_info.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\edge_event.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\exception.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\info_event.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\line.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\line_info.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\line_request.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\line_settings.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\version.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\_internal.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\__init__.py -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\_ext.pyi -> build\lib.win-amd64-cpython-39\gpiod copying gpiod\py.typed -> build\lib.win-amd64-cpython-39\gpiod running build_ext building 'gpiod._ext' extension error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for gpiod Failed to build gpiod ERROR: Could not build wheels for gpiod, which is required to install pyproject.toml-based projects WARNING: You are using pip version 22.0.4; however, version 25.1.1 is available. You should consider upgrading via the 'C:\Users\11867\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\python.exe -m pip install --upgrade pip' command.

命令行运行:pip install dlib==19.24.0报错: Collecting dlib==19.24.0 Using cached dlib-19.24.0.tar.gz (3.2 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: dlib Building wheel for dlib (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for dlib (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [29 lines of output] <string>:212: SyntaxWarning: invalid escape sequence '\(' <string>:213: SyntaxWarning: invalid escape sequence '\(' <string>:214: SyntaxWarning: invalid escape sequence '\(' <string>:194: SetuptoolsDeprecationWarning: The test command is disabled and references to it are deprecated. !! ******************************************************************************** Please remove any references to setuptools.command.test in all supported versions of the affected package. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. ******************************************************************************** !! C:\Users\徐庆凯\AppData\Local\Temp\pip-build-env-r6nhe5ov\overlay\Lib\site-packages\setuptools\_distutils\dist.py:289: UserWarning: Unknown distribution option: 'tests_require' warnings.warn(msg) running bdist_wheel running build running build_py running build_ext Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File "D:\Users\徐庆凯\AppData\Local\Programs\Python\Python313\Scripts\cmake.exe\__main__.py", line 4, in <module> from cmake import cmake ModuleNotFoundError: No module named 'cmake' ERROR: CMake must be installed to build dlib [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for dlib Failed to build dlib ERROR: Failed to build installable wheels for some pyproject.toml based projects (dlib)

pip3 install . Defaulting to user installation because normal site-packages is not writeable Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Processing /home/ubuntu/large_models/speech_pkg Preparing metadata (setup.py) ... done Building wheels for collected packages: speech DEPRECATION: Building 'speech' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of 'speech'. Discussion can be found at https://github.com/pypa/pip/issues/6334 Building wheel for speech (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [322 lines of output] running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/speech copying speech/awake.py -> build/lib/speech copying speech/__init__.py -> build/lib/speech running egg_info writing speech.egg-info/PKG-INFO writing dependency_links to speech.egg-info/dependency_links.txt writing top-level names to speech.egg-info/top_level.txt reading manifest file 'speech.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'speech.egg-info/SOURCES.txt' /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.jetson_nano' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.jetson_nano' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.jetson_nano' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.jetson_nano' to be distributed and are already explicitly excluding 'speech.jetson_nano' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.jetson_orin' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.jetson_orin' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.jetson_orin' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.jetson_orin' to be distributed and are already explicitly excluding 'speech.jetson_orin' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.resources' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.resources' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.resources' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.resources' to be distributed and are already explicitly excluding 'speech.resources' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.rpi5' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.rpi5' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.rpi5' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.rpi5' to be distributed and are already explicitly excluding 'speech.rpi5' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.rpi5_docker' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.rpi5_docker' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.rpi5_docker' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.rpi5_docker' to be distributed and are already explicitly excluding 'speech.rpi5_docker' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) copying speech/speech.so -> build/lib/speech creating build/lib/speech/jetson_nano copying speech/jetson_nano/py3.6 -> build/lib/speech/jetson_nano copying speech/jetson_nano/speech.so -> build/lib/speech/jetson_nano creating build/lib/speech/jetson_orin copying speech/jetson_orin/py3.10 -> build/lib/speech/jetson_orin copying speech/jetson_orin/speech.so -> build/lib/speech/jetson_orin creating build/lib/speech/resources copying speech/resources/_detect_jetson_nano.so -> build/lib/speech/resources copying speech/resources/_detect_jetson_orin.so -> build/lib/speech/resources copying speech/resources/_detect_rpi5.so -> build/lib/speech/resources copying speech/resources/_detect_rpi5_docker_ubuntu20_04.so -> build/lib/speech/resources copying speech/resources/common.res -> build/lib/speech/resources copying speech/resources/detect_jetson_nano.so -> build/lib/speech/resources copying speech/resources/detect_jetson_orin.so -> build/lib/speech/resources copying speech/resources/detect_rpi5.so -> build/lib/speech/resources copying speech/resources/detect_rpi5_docker_ubuntu20_04.so -> build/lib/speech/resources copying speech/resources/vad.jit -> build/lib/speech/resources creating build/lib/speech/rpi5 copying speech/rpi5/py3.11 -> build/lib/speech/rpi5 copying speech/rpi5/speech.so -> build/lib/speech/rpi5 creating build/lib/speech/rpi5_docker copying speech/rpi5_docker/py3.8 -> build/lib/speech/rpi5_docker copying speech/rpi5_docker/speech.so -> build/lib/speech/rpi5_docker copying speech/awake.py -> build/lib/speech copying speech/__init__.py -> build/lib/speech /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running setup.py directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-aarch64/wheel running install running install_lib creating build/bdist.linux-aarch64 creating build/bdist.linux-aarch64/wheel creating build/bdist.linux-aarch64/wheel/speech copying build/lib/speech/awake.py -> build/bdist.linux-aarch64/wheel/speech creating build/bdist.linux-aarch64/wheel/speech/jetson_orin copying build/lib/speech/jetson_orin/speech.so -> build/bdist.linux-aarch64/wheel/speech/jetson_orin copying build/lib/speech/jetson_orin/py3.10 -> build/bdist.linux-aarch64/wheel/speech/jetson_orin creating build/bdist.linux-aarch64/wheel/speech/rpi5_docker copying build/lib/speech/rpi5_docker/speech.so -> build/bdist.linux-aarch64/wheel/speech/rpi5_docker copying build/lib/speech/rpi5_docker/py3.8 -> build/bdist.linux-aarch64/wheel/speech/rpi5_docker creating build/bdist.linux-aarch64/wheel/speech/rpi5 copying build/lib/speech/rpi5/speech.so -> build/bdist.linux-aarch64/wheel/speech/rpi5 copying build/lib/speech/rpi5/py3.11 -> build/bdist.linux-aarch64/wheel/speech/rpi5 copying build/lib/speech/speech.so -> build/bdist.linux-aarch64/wheel/speech creating build/bdist.linux-aarch64/wheel/speech/jetson_nano copying build/lib/speech/jetson_nano/py3.6 -> build/bdist.linux-aarch64/wheel/speech/jetson_nano copying build/lib/speech/jetson_nano/speech.so -> build/bdist.linux-aarch64/wheel/speech/jetson_nano copying build/lib/speech/__init__.py -> build/bdist.linux-aarch64/wheel/speech creating build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_rpi5.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/common.res -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_jetson_nano.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_jetson_orin.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_jetson_nano.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_rpi5_docker_ubuntu20_04.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_rpi5.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/vad.jit -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_jetson_orin.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_rpi5_docker_ubuntu20_04.so -> build/bdist.linux-aarch64/wheel/speech/resources running install_egg_info Copying speech.egg-info to build/bdist.linux-aarch64/wheel/speech-1.0-py3.10.egg-info running install_scripts creating build/bdist.linux-aarch64/wheel/speech-1.0.dist-info/WHEEL creating '/tmp/pip-wheel-4gy84oln/speech-1.0-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it Traceback (most recent call last): File "<string>", line 2, in <module> File "", line 35, in <module> File "/home/ubuntu/large_models/speech_pkg/setup.py", line 3, in <module> setup( File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/__init__.py", line 103, in setup return distutils.core.setup(**attrs) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 184, in setup return run_commands(dist) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 200, in run_commands dist.run_commands() File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands self.run_command(cmd) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/dist.py", line 968, in run_command super().run_command(command) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command cmd_obj.run() File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 361, in run wf.write_files(archive_root) File "/usr/lib/python3/dist-packages/wheel/wheelfile.py", line 136, in write_files self.write(path, arcname) File "/usr/lib/python3/dist-packages/wheel/wheelfile.py", line 147, in write zinfo = ZipInfo(arcname or filename, date_time=get_zipinfo_datetime(st.st_mtime)) File "/usr/lib/python3.10/zipfile.py", line 366, in __init__ raise ValueError('ZIP does not support timestamps before 1980') ValueError: ZIP does not support timestamps before 1980 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for speech Running setup.py clean for speech Failed to build speech ERROR: Failed to build installable wheels for some pyproject.toml based projects (speech) > cat ~/large_models/speech_pkg/pyproject.toml cat: /home/ubuntu/large_models/speech_pkg/pyproject.toml: No such file or directory > pip3 install . Defaulting to user installation because normal site-packages is not writeable Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple Processing /home/ubuntu/large_models/speech_pkg Preparing metadata (setup.py) ... done Building wheels for collected packages: speech DEPRECATION: Building 'speech' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the --use-pep517 option, (possibly combined with --no-build-isolation), or adding a pyproject.toml file to the source tree of 'speech'. Discussion can be found at https://github.com/pypa/pip/issues/6334 Building wheel for speech (setup.py) ... error error: subprocess-exited-with-error × python setup.py bdist_wheel did not run successfully. │ exit code: 1 ╰─> [322 lines of output] running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/speech copying speech/awake.py -> build/lib/speech copying speech/__init__.py -> build/lib/speech running egg_info writing speech.egg-info/PKG-INFO writing dependency_links to speech.egg-info/dependency_links.txt writing top-level names to speech.egg-info/top_level.txt reading manifest file 'speech.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'speech.egg-info/SOURCES.txt' /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.jetson_nano' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.jetson_nano' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.jetson_nano' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.jetson_nano' to be distributed and are already explicitly excluding 'speech.jetson_nano' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.jetson_orin' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.jetson_orin' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.jetson_orin' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.jetson_orin' to be distributed and are already explicitly excluding 'speech.jetson_orin' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.resources' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.resources' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.resources' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.resources' to be distributed and are already explicitly excluding 'speech.resources' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.rpi5' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.rpi5' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.rpi5' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.rpi5' to be distributed and are already explicitly excluding 'speech.rpi5' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'speech.rpi5_docker' is absent from the packages configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'speech.rpi5_docker' as an importable package[^1], but it is absent from setuptools' packages configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'speech.rpi5_docker' is explicitly added to the packages configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using find_namespace_packages(...)/find_namespace: instead of find_packages(...)/find:). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'speech.rpi5_docker' to be distributed and are already explicitly excluding 'speech.rpi5_docker' via find_namespace_packages(...)/find_namespace or find_packages(...)/find, you can try to use exclude_package_data, or include-package-data=False in combination with a more fine grained package-data configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any .py files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) copying speech/speech.so -> build/lib/speech creating build/lib/speech/jetson_nano copying speech/jetson_nano/py3.6 -> build/lib/speech/jetson_nano copying speech/jetson_nano/speech.so -> build/lib/speech/jetson_nano creating build/lib/speech/jetson_orin copying speech/jetson_orin/py3.10 -> build/lib/speech/jetson_orin copying speech/jetson_orin/speech.so -> build/lib/speech/jetson_orin creating build/lib/speech/resources copying speech/resources/_detect_jetson_nano.so -> build/lib/speech/resources copying speech/resources/_detect_jetson_orin.so -> build/lib/speech/resources copying speech/resources/_detect_rpi5.so -> build/lib/speech/resources copying speech/resources/_detect_rpi5_docker_ubuntu20_04.so -> build/lib/speech/resources copying speech/resources/common.res -> build/lib/speech/resources copying speech/resources/detect_jetson_nano.so -> build/lib/speech/resources copying speech/resources/detect_jetson_orin.so -> build/lib/speech/resources copying speech/resources/detect_rpi5.so -> build/lib/speech/resources copying speech/resources/detect_rpi5_docker_ubuntu20_04.so -> build/lib/speech/resources copying speech/resources/vad.jit -> build/lib/speech/resources creating build/lib/speech/rpi5 copying speech/rpi5/py3.11 -> build/lib/speech/rpi5 copying speech/rpi5/speech.so -> build/lib/speech/rpi5 creating build/lib/speech/rpi5_docker copying speech/rpi5_docker/py3.8 -> build/lib/speech/rpi5_docker copying speech/rpi5_docker/speech.so -> build/lib/speech/rpi5_docker copying speech/awake.py -> build/lib/speech copying speech/__init__.py -> build/lib/speech /home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running setup.py directly. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() installing to build/bdist.linux-aarch64/wheel running install running install_lib creating build/bdist.linux-aarch64 creating build/bdist.linux-aarch64/wheel creating build/bdist.linux-aarch64/wheel/speech copying build/lib/speech/awake.py -> build/bdist.linux-aarch64/wheel/speech creating build/bdist.linux-aarch64/wheel/speech/jetson_orin copying build/lib/speech/jetson_orin/speech.so -> build/bdist.linux-aarch64/wheel/speech/jetson_orin copying build/lib/speech/jetson_orin/py3.10 -> build/bdist.linux-aarch64/wheel/speech/jetson_orin creating build/bdist.linux-aarch64/wheel/speech/rpi5_docker copying build/lib/speech/rpi5_docker/speech.so -> build/bdist.linux-aarch64/wheel/speech/rpi5_docker copying build/lib/speech/rpi5_docker/py3.8 -> build/bdist.linux-aarch64/wheel/speech/rpi5_docker creating build/bdist.linux-aarch64/wheel/speech/rpi5 copying build/lib/speech/rpi5/speech.so -> build/bdist.linux-aarch64/wheel/speech/rpi5 copying build/lib/speech/rpi5/py3.11 -> build/bdist.linux-aarch64/wheel/speech/rpi5 copying build/lib/speech/speech.so -> build/bdist.linux-aarch64/wheel/speech creating build/bdist.linux-aarch64/wheel/speech/jetson_nano copying build/lib/speech/jetson_nano/py3.6 -> build/bdist.linux-aarch64/wheel/speech/jetson_nano copying build/lib/speech/jetson_nano/speech.so -> build/bdist.linux-aarch64/wheel/speech/jetson_nano copying build/lib/speech/__init__.py -> build/bdist.linux-aarch64/wheel/speech creating build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_rpi5.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/common.res -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_jetson_nano.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_jetson_orin.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_jetson_nano.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_rpi5_docker_ubuntu20_04.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/detect_rpi5.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/vad.jit -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_jetson_orin.so -> build/bdist.linux-aarch64/wheel/speech/resources copying build/lib/speech/resources/_detect_rpi5_docker_ubuntu20_04.so -> build/bdist.linux-aarch64/wheel/speech/resources running install_egg_info Copying speech.egg-info to build/bdist.linux-aarch64/wheel/speech-1.0-py3.10.egg-info running install_scripts creating build/bdist.linux-aarch64/wheel/speech-1.0.dist-info/WHEEL creating '/tmp/pip-wheel-dpii6adm/speech-1.0-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it Traceback (most recent call last): File "<string>", line 2, in <module> File "", line 35, in <module> File "/home/ubuntu/large_models/speech_pkg/setup.py", line 3, in <module> setup( File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/__init__.py", line 103, in setup return distutils.core.setup(**attrs) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 184, in setup return run_commands(dist) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 200, in run_commands dist.run_commands() File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands self.run_command(cmd) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/dist.py", line 968, in run_command super().run_command(command) File "/home/ubuntu/.local/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command cmd_obj.run() File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 361, in run wf.write_files(archive_root) File "/usr/lib/python3/dist-packages/wheel/wheelfile.py", line 136, in write_files self.write(path, arcname) File "/usr/lib/python3/dist-packages/wheel/wheelfile.py", line 147, in write zinfo = ZipInfo(arcname or filename, date_time=get_zipinfo_datetime(st.st_mtime)) File "/usr/lib/python3.10/zipfile.py", line 366, in __init__ raise ValueError('ZIP does not support timestamps before 1980') ValueError: ZIP does not support timestamps before 1980 [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for speech Running setup.py clean for speech Failed to build speech ERROR: Failed to build installable wheels for some pyproject.toml based projects (speech)

怎么找(venv) PS D:\ai应用课\03-2512期大模型全栈班-L3阶段\23-Agent 数字人应用-25.7.14\Agent数字人\interviewer> pip install webrtcvad Collecting webrtcvad Using cached webrtcvad-2.0.10.tar.gz (66 kB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Building wheels for collected packages: webrtcvad Building wheel for webrtcvad (pyproject.toml) ... error error: subprocess-exited-with-error × Building wheel for webrtcvad (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [23 lines of output] C:\Users\John\AppData\Local\Temp\pip-build-env-ylsk1x9c\overlay\Lib\site-packages\setuptools\_distutils\dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) C:\Users\John\AppData\Local\Temp\pip-build-env-ylsk1x9c\overlay\Lib\site-packages\setuptools\dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build_py creating build\lib.win-amd64-cpython-311 copying webrtcvad.py -> build\lib.win-amd64-cpython-311 running build_ext building '_webrtcvad' extension error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/ [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. ERROR: Failed building wheel for webrtcvad Failed to build webrtcvad ERROR: Failed to build installable wheels for some pyproject.toml based projects (webrtcvad)

最新推荐

recommend-type

零点GZDSP 4.80A-PRO电脑DSP调音软件下载

零点GZDSP 4.80A-PRO电脑DSP调音软件下载
recommend-type

云计算-软件开发云PPT课件(1).pptx

云计算-软件开发云PPT课件(1).pptx
recommend-type

C++实现的DecompressLibrary库解压缩GZ文件

根据提供的文件信息,我们可以深入探讨C++语言中关于解压缩库(Decompress Library)的使用,特别是针对.gz文件格式的解压过程。这里的“lib”通常指的是库(Library),是软件开发中用于提供特定功能的代码集合。在本例中,我们关注的库是用于处理.gz文件压缩包的解压库。 首先,我们要明确一个概念:.gz文件是一种基于GNU zip压缩算法的压缩文件格式,广泛用于Unix、Linux等操作系统上,对文件进行压缩以节省存储空间或网络传输时间。要解压.gz文件,开发者需要使用到支持gzip格式的解压缩库。 在C++中,处理.gz文件通常依赖于第三方库,如zlib或者Boost.IoStreams。codeproject.com是一个提供编程资源和示例代码的网站,程序员可以在该网站上找到现成的C++解压lib代码,来实现.gz文件的解压功能。 解压库(Decompress Library)提供的主要功能是读取.gz文件,执行解压缩算法,并将解压缩后的数据写入到指定的输出位置。在使用这些库时,我们通常需要链接相应的库文件,这样编译器在编译程序时能够找到并使用这些库中定义好的函数和类。 下面是使用C++解压.gz文件时,可能涉及的关键知识点: 1. Zlib库 - zlib是一个用于数据压缩的软件库,提供了许多用于压缩和解压缩数据的函数。 - zlib库支持.gz文件格式,并且在多数Linux发行版中都预装了zlib库。 - 在C++中使用zlib库,需要包含zlib.h头文件,同时链接z库文件。 2. Boost.IoStreams - Boost是一个提供大量可复用C++库的组织,其中的Boost.IoStreams库提供了对.gz文件的压缩和解压缩支持。 - Boost库的使用需要下载Boost源码包,配置好编译环境,并在编译时链接相应的Boost库。 3. C++ I/O操作 - 解压.gz文件需要使用C++的I/O流操作,比如使用ifstream读取.gz文件,使用ofstream输出解压后的文件。 - 对于流操作,我们常用的是std::ifstream和std::ofstream类。 4. 错误处理 - 解压缩过程中可能会遇到各种问题,如文件损坏、磁盘空间不足等,因此进行适当的错误处理是必不可少的。 - 正确地捕获异常,并提供清晰的错误信息,对于调试和用户反馈都非常重要。 5. 代码示例 - 从codeproject找到的C++解压lib很可能包含一个或多个源代码文件,这些文件会包含解压.gz文件所需的函数或类。 - 示例代码可能会展示如何初始化库、如何打开.gz文件、如何读取并处理压缩数据,以及如何释放资源等。 6. 库文件的链接 - 编译使用解压库的程序时,需要指定链接到的库文件,这在不同的编译器和操作系统中可能略有不同。 - 通常,在编译命令中加入-l参数,比如使用g++的话可能是`g++ -o DecompressLibrary DecompressLibrary.cpp -lz`,其中`-lz`表示链接zlib库。 7. 平台兼容性 - 在不同平台上使用解压库可能需要考虑平台兼容性问题。 - Windows系统可能需要额外的配置和库文件,因为zlib或其他库可能不是默认预装的。 根据以上知识点,我们可以得出,在C++中解压.gz文件主要涉及到对zlib或类似库的使用,以及熟悉C++的I/O操作。正确使用这些库,能够有效地对压缩文件进行解压,并处理可能出现的错误情况。如果从codeproject获取到的C++解压lib确实是针对.gz文件格式的,那么它很可能已经封装好了大部分的操作细节,让开发者能够以更简单的方式实现解压功能。
recommend-type

【数据融合技术】:甘肃土壤类型空间分析中的专业性应用

# 摘要 数据融合技术作为一种集成多源数据信息的方法,在土壤类型空间分析中发挥着关键作用。本文介绍了数据融合技术的基本概念及其理论基础,阐述了数据预处理、同步整合及冲突解决等关键技术,并详细描述了甘肃土壤类型数据准备的流程,包括数据采集、质量评估、空间化处理及融合实践准备。通过具体案例分析,展示了数据融合在土壤类型空间分布分析、土壤质量评估及土壤保护规划中的应用。同时,文
recommend-type

VM ware如何查看软件版本信息

<think>首先,用户的问题是:“我想查找VMware软件版本信息的查看方法请问如何在VMware中查看软件版本信息”。用户参考了之前的引用,但那些引用主要是关于查看VMware版本的一般方法,现在用户具体想知道在VMware软件中如何查看版本信息。回顾之前的对话:-用户第一次问的是VSCode的版本查看方法。-现在用户问的是VMware的版本查看方法。-系统级指令要求使用中文回答,正确格式化数学表达式(如果需要),但这里可能不需要数学表达式。-指令还要求生成相关问题,并在回答中引用段落时添加引用标识。用户提供的引用[1]到[5]是关于VMware版本的查看方法、下载等,但用户特别强调“参考
recommend-type

数据库课程设计报告:常用数据库综述

数据库是现代信息管理的基础,其技术广泛应用于各个领域。在高等教育中,数据库课程设计是一个重要环节,它不仅是学习理论知识的实践,也是培养学生综合运用数据库技术解决问题能力的平台。本知识点将围绕“经典数据库课程设计报告”展开,详细阐述数据库的基本概念、课程设计的目的和内容,以及在设计报告中常用的数据库技术。 ### 1. 数据库基本概念 #### 1.1 数据库定义 数据库(Database)是存储在计算机存储设备中的数据集合,这些数据集合是经过组织的、可共享的,并且可以被多个应用程序或用户共享访问。数据库管理系统(DBMS)提供了数据的定义、创建、维护和控制功能。 #### 1.2 数据库类型 数据库按照数据模型可以分为关系型数据库(如MySQL、Oracle)、层次型数据库、网状型数据库、面向对象型数据库等。其中,关系型数据库因其简单性和强大的操作能力而广泛使用。 #### 1.3 数据库特性 数据库具备安全性、完整性、一致性和可靠性等重要特性。安全性指的是防止数据被未授权访问和破坏。完整性指的是数据和数据库的结构必须符合既定规则。一致性保证了事务的执行使数据库从一个一致性状态转换到另一个一致性状态。可靠性则保证了系统发生故障时数据不会丢失。 ### 2. 课程设计目的 #### 2.1 理论与实践结合 数据库课程设计旨在将学生在课堂上学习的数据库理论知识与实际操作相结合,通过完成具体的数据库设计任务,加深对数据库知识的理解。 #### 2.2 培养实践能力 通过课程设计,学生能够提升分析问题、设计解决方案以及使用数据库技术实现这些方案的能力。这包括需求分析、概念设计、逻辑设计、物理设计、数据库实现、测试和维护等整个数据库开发周期。 ### 3. 课程设计内容 #### 3.1 需求分析 在设计报告的开始,需要对项目的目标和需求进行深入分析。这涉及到确定数据存储需求、数据处理需求、数据安全和隐私保护要求等。 #### 3.2 概念设计 概念设计阶段要制定出数据库的E-R模型(实体-关系模型),明确实体之间的关系。E-R模型的目的是确定数据库结构并形成数据库的全局视图。 #### 3.3 逻辑设计 基于概念设计,逻辑设计阶段将E-R模型转换成特定数据库系统的逻辑结构,通常是关系型数据库的表结构。在此阶段,设计者需要确定各个表的属性、数据类型、主键、外键以及索引等。 #### 3.4 物理设计 在物理设计阶段,针对特定的数据库系统,设计者需确定数据的存储方式、索引的具体实现方法、存储过程、触发器等数据库对象的创建。 #### 3.5 数据库实现 根据物理设计,实际创建数据库、表、视图、索引、触发器和存储过程等。同时,还需要编写用于数据录入、查询、更新和删除的SQL语句。 #### 3.6 测试与维护 设计完成之后,需要对数据库进行测试,确保其满足需求分析阶段确定的各项要求。测试过程包括单元测试、集成测试和系统测试。测试无误后,数据库还需要进行持续的维护和优化。 ### 4. 常用数据库技术 #### 4.1 SQL语言 SQL(结构化查询语言)是数据库管理的国际标准语言。它包括数据查询、数据操作、数据定义和数据控制四大功能。SQL语言是数据库课程设计中必备的技能。 #### 4.2 数据库设计工具 常用的数据库设计工具包括ER/Studio、Microsoft Visio、MySQL Workbench等。这些工具可以帮助设计者可视化地设计数据库结构,提高设计效率和准确性。 #### 4.3 数据库管理系统 数据库管理系统(DBMS)是用于创建和管理数据库的软件。关系型数据库管理系统如MySQL、PostgreSQL、Oracle、SQL Server等是数据库课程设计中的核心工具。 #### 4.4 数据库安全 数据库安全涉及用户认证、授权、数据加密、审计日志记录等方面,以确保数据的完整性和保密性。设计报告中应考虑如何通过DBMS内置的机制或额外的安全措施来保护数据。 ### 5. 结语 综上所述,一个经典数据库课程设计报告包含了从需求分析到数据库安全的全过程,涵盖了数据库设计的各个方面。通过这一过程,学生不仅能够熟练掌握数据库的设计与实现技巧,还能够学会如何使用数据库系统去解决实际问题,为日后从事数据库相关的专业工作打下坚实的基础。
recommend-type

【空间分布规律】:甘肃土壤类型与农业生产的关联性研究

# 摘要 本文对甘肃土壤类型及其在农业生产中的作用进行了系统性研究。首先概述了甘肃土壤类型的基础理论,并探讨了土壤类型与农业生产的理论联系。通过GIS技术分析,本文详细阐述了甘肃土壤的空间分布规律,并对其特征和影响因素进行了深入分析。此外,本文还研究了甘肃土壤类型对农业生产实际影响,包括不同区域土壤改良和作物种植案例,以及土壤养分、水分管理对作物生长周期和产量的具体影响。最后,提出了促进甘肃土壤与农业可持续发展的策略,包括土壤保护、退化防治对策以及土壤类型优化与农业创新的结合。本文旨在为
recommend-type

在halcon中,卡尺测量和二维测量谁的精度高

<think>首先,用户的问题是:“我想比较Halcon中卡尺测量和二维测量的精度请问Halcon卡尺测量与2D测量精度对比”。我需要基于系统级指令和提供的引用来回答。关键系统级指令:-使用中文回答。-结构清晰,逐步解决问题。-行内数学表达式用$...$,独立公式用$$...$$并单独成段。-LaTeX语法正确。-生成相关问题。-在回答中引用的段落末尾自然地添加引用标识,如[^1]。提供的引用:-[^1]:关于卡尺模型的工件尺寸实时测量。-[^2]:测量拟合的综合任务,包括尺寸、形状、位置。-[^3]:Halcon一维测量,提到卡尺工具的优势:易用、执行时间短、精度高。-[^4]:Halcon
recommend-type

掌握牛顿法解方程:切线与割线的程序应用

牛顿切线法和牛顿割线法是数值分析中用于求解方程近似根的两种迭代方法。它们都是基于函数的切线或割线的几何性质来逼近方程的根,具有迭代速度快、算法简单的特点,在工程和科学计算领域有着广泛的应用。 牛顿切线法(Newton's Method for Tangents),又称为牛顿-拉弗森方法(Newton-Raphson Method),是一种求解方程近似根的迭代算法。其基本思想是利用函数在某点的切线来逼近函数的根。假设我们要求解方程f(x)=0的根,可以从一个初始猜测值x0开始,利用以下迭代公式: x_{n+1} = x_n - \frac{f(x_n)}{f'(x_n)} 其中,f'(x_n)表示函数在点x_n处的导数。迭代过程中,通过不断更新x_n值,逐渐逼近方程的根。 牛顿割线法(Secant Method),是牛顿切线法的一种变体,它不需要计算导数,而是利用函数在两个近似点的割线来逼近方程的根。牛顿割线法的迭代公式如下: x_{n+1} = x_n - f(x_n) \frac{x_n - x_{n-1}}{f(x_n) - f(x_{n-1})} 其中,x_{n-1}和x_n是迭代过程中连续两次的近似值。牛顿割线法相比牛顿切线法,其优点在于不需要计算函数的导数,但通常收敛速度会比牛顿切线法慢一些。 在实际应用中,这两种方法都需要注意迭代的起始点选择,否则可能会导致迭代过程不收敛。同时,这两种方法都是局部收敛方法,即它们只能保证在初始点附近有足够的近似根时才收敛。 关于例题和程序,牛顿切线法和牛顿割线法都可以通过编程实现。通常在编程实现时,需要输入函数的表达式、初始猜测值、迭代次数限制以及误差容忍度等参数。程序会根据这些输入,通过循环迭代计算,直到满足误差容忍度或达到迭代次数限制为止。 在编程实现过程中,需要注意以下几点: 1. 初始猜测值的选择对迭代的收敛性有较大影响,需要根据具体问题来合理选择。 2. 当迭代过程中遇到函数值或导数值过大、过小,或者分母趋近于零时,需要进行适当的数值处理,以避免数值不稳定或除以零的错误。 3. 对于不同的方程和函数,可能需要选择不同的迭代终止条件,如设定一个误差值或迭代次数上限。 牛顿法(包含牛顿切线法和牛顿割线法)是一类非常强大的数值解法,尤其适用于求解非线性方程,其基本原理和程序实现的知识点在理工科的许多领域都有着广泛的应用,是数值分析领域的一个基石。 请注意,本知识点仅涵盖标题和描述中提到的内容,压缩包子文件列表中的信息并未提供,因此无法提供相关内容的知识点。
recommend-type

【制图技术】:甘肃高质量土壤分布TIF图件的成图策略

# 摘要 本文针对甘肃土壤分布数据的TIF图件制作进行了系统研究。首先概述了甘肃土壤的分布情况,接着介绍了TIF图件的基础知识,包括其格式特点、空间数据表达以及质量控制方法。随后,文中构建了成图策略的理论框架,分析了土壤分布图的信息需求与数据处理流程,并探讨了成图原则与标准。在实践操作部分,详细阐述了制图软