/bin/bash: xmllint: 未找到命令

本文介绍了解决Ubuntu 32位系统中编译问题的方法,当遇到编译过程中缺少xmllint的问题时,可以通过安装libxml2-utils来解决。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

转载请注明出处:http://blog.youkuaiyun.com/droyon/article/details/8655517

我原先的ubuntu是32位的,如果在编译过程中,如果发现报告了上述问题,那么动手安装xmllint。

命令:

sudo apt-get  install libxml2-utils


其他的类似。



关注我的技术公众号,查看更多优质技术文章推送

微信扫一扫下方二维码即可关注:

关注我的技术公众号,查看更多优质技术文章推送


报错root@debian:/usr/src/asterisk-13.38.3# ./configure --with-crypto --with-ssl --with-srtp --with-pjproject-bundled checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking whether char is unsigned... no checking for uname... /usr/bin/uname checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C preprocessor... gcc -E checking how to run the C++ preprocessor... g++ -E checking for a sed that does not truncate output... /usr/bin/sed checking for egrep... grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for gawk... no checking for mawk... mawk checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for ranlib... ranlib checking for GNU make... make checking for egrep... (cached) /usr/bin/grep -E checking for strip... strip checking for ar... ar checking for bison... : checking for cmp... /usr/bin/cmp checking for cat... /usr/bin/cat checking for cut... /usr/bin/cut checking for flex... : checking for grep... (cached) /usr/bin/grep checking for python2.7... no checking for python2... no checking for python... no checking for python3... /usr/bin/python3 checking for find... /usr/bin/find checking for basename... /usr/bin/basename checking for dirname... /usr/bin/dirname checking for sh... /bin/bash checking for ln... /usr/bin/ln checking for doxygen... : checking for dot... : checking for wget... /usr/bin/wget checking for curl... /usr/bin/curl checking for xmllint... : checking for xmlstarlet... no checking for xml... no checking for bash... /bin/bash checking for git... /usr/bin/git checking for alembic... : checking for bzip2... /usr/bin/bzip2 checking for tar... /usr/bin/tar checking for patch... /usr/bin/patch checking for sed... (cached) /usr/bin/sed checking for nm... /usr/bin/nm checking for ldconfig... /sbin/ldconfig checking for sha1sum... /usr/bin/sha1sum checking for openssl... /usr/bin/openssl checking for bison that supports parse-param... checking for soxmix... no checking for md5... no checking for md5sum... md5sum checking for a sed that does not truncate output... (cached) /usr/bin/sed checking whether gcc is Clang... no checking whether pthreads work with -pthread... yes checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE checking whether more special flags are required for pthreads... no checking for PTHREAD_PRIO_INHERIT... yes checking for RAII support... checking for gcc -fnested-functions... no checking for clang strsep/strcmp optimization... no checking for embedded pjproject (may have to download)... configuring [pjproject] Verifying /tmp/pjproject-2.10.tar.bz2 [pjproject] Verify successful [pjproject] Unpacking /tmp/pjproject-2.10.tar.bz2 [pjproject] Applying patches /usr/src/asterisk-13.38.3/third-party/pjproject/patches /usr/src/asterisk-13.38.3/third-party/pjproject/source The text leading up to this was: -------------------------- |From e8000cc80e5f8ba02cc52852edc02cdb0e949525 Mon Sep 17 00:00:00 2001 |From: Richard Mudgett <rmudgett@digium.com> |Date: Mon, 6 Aug 2018 11:24:25 -0500 |Subject: [PATCH 1/5] 0000-configure-ssl-library-path.patch | |--- | aconfigure | 6 +++++- | aconfigure.ac | 6 +++++- | 2 files changed, 10 insertions(+), 2 deletions(-) | |diff --git a/aconfigure b/aconfigure |index 1c449b8..c4c6060 100755 |--- a/aconfigure |+++ b/aconfigure -------------------------- File to patch: 如何解决
最新发布
07-30
install prefix /home/chang/dev/ffmpeg-rockchip/rk3576 source path . C compiler /opt/android-ndk-r26b/toolchains/llvm/prebuilt/linux-x86_64/bin/aarch64-linux-android34-clang C library bionic host C compiler gcc host C library glibc ARCH aarch64 (generic) big-endian no runtime cpu detection yes NEON enabled yes DOTPROD enabled no I8MM enabled no debug symbols yes strip symbols yes optimize for size no optimizations yes static no shared yes postprocessing support no network support yes threading support pthreads safe bitstream reader yes texi2html enabled no perl enabled yes pod2man enabled yes makeinfo enabled no makeinfo supports HTML no xmllint enabled yes External libraries: iconv libdrm rkmpp zlib External libraries providing hardware acceleration: cuda_llvm rkmpp v4l2_m2m 这样的输出正常吗?支持了rkmpp吗?PKG_CONFIG_PATH="/home/chang/dev/mpp/mpp_build/install/usr/local/lib/pkgconfig:/home/chang/dev/mpp/mpp_build/install/lib/pkgconfig" ./configure --target-os=android --arch=aarch64 --prefix=/home/chang/dev/ffmpeg-rockchip/rk3576 --enable-cross-compile --cross-prefix=$TOOLCHAIN/bin/llvm- --sysroot=/opt/android-ndk-r26b/toolchains/llvm/prebuilt/linux-x86_64/sysroot --cc=$TOOLCHAIN/bin/${TARGET}-clang --cxx=$TOOLCHAIN/bin/${TARGET}-clang++ --enable-rkmpp --enable-libdrm --enable-shared --enable-version3 --disable-static --disable-doc --disable-programs --pkg-config=$(which pkg-config) --extra-cflags="-I/home/chang/dev/mpp/mpp_build/install/include" --extra-ldflags="-L/home/chang/dev/mpp/mpp_build/install/lib"
03-25
<think>好的,我需要帮助用户分析他们的FFmpeg配置输出是否正常,特别是是否成功支持了rkmpp。首先,我应该仔细查看用户提供的配置输出和他们的编译命令。 用户给出的配置输出中,External libraries部分列出了rkmpp,这说明在配置过程中检测到了rkmpp库。同时,硬件加速部分也有rkmpp,这进一步确认了支持。不过,我需要检查是否有任何错误或警告信息,但用户没有提供这部分内容,所以暂时假设配置过程没有报错。 接下来,查看用户的编译命令。他们设置了PKG_CONFIG_PATH指向mpp的安装目录,这有助于pkg-config找到rkmpp的.pc文件。--enable-rkmpp选项显式启用了rkmpp支持,并且指定了额外的包含路径和库路径,确保编译器能找到头文件和库。这里需要注意pkg-config是否正确定位,用户使用--pkg-config=$(which pkg-config)可能没问题,但需要确认pkg-config版本是否兼容。 可能的隐患包括:Android NDK的版本与mpp库的兼容性,rkmpp是否针对Android正确编译,以及运行时库是否会被正确链接。用户可能需要验证生成的FFmpeg二进制文件是否实际链接了librockchip_mpp.so,可以通过检查readelf或ldd输出来确认。 总结来说,配置输出显示rkmpp已启用,但建议用户进行编译后的测试,比如运行编码或解码命令,查看日志是否有rkmpp相关的加速使用。如果遇到问题,可能需要检查配置阶段的详细日志,确保没有遗漏的错误。</think>根据你提供的配置输出和参数,以下是逐步分析: 1. **rkmpp支持状态确认**: - 在`External libraries`和`硬件加速`列表中均明确显示`rkmpp`,说明: ```bash ✅ rkmpp支持已成功启用(--enable-rkmpp生效) ``` 2. **关键配置验证**: ```bash PKG_CONFIG_PATH="/home/chang/dev/mpp/mpp_build/install/...:/..." # 正确指向mpp库路径 --enable-rkmpp # 显式启用硬件编解码 --extra-cflags="-I/home/chang/.../include" # 正确包含头文件 --extra-ldflags="-L/home/chang/.../lib" # 正确链接库文件 ``` 3. **潜在风险点检查**: - 🔍 验证mpp库架构: ```bash file /home/chang/dev/mpp/mpp_build/install/lib/librockchip_mpp.so ``` 应显示`ELF 64-bit LSB shared object, ARM aarch64`,确保与目标架构aarch64匹配 - ⚠️ 运行时依赖检查: ```bash readelf -d ffmpeg | grep NEEDED ``` 应包含`librockchip_mpp.so`动态库依赖 4. **编译后验证建议**: ```bash ./ffmpeg -hwaccels | grep rkmpp # 预期输出:rkmpp ./ffmpeg -decoders | grep h264_rkmpp # 检查具体解码器 ./ffmpeg -encoders | grep h264_rkmpp # 检查具体编码器 ``` 5. **已知问题排查**: - 若遇到`undefined reference`错误,需检查: ```bash mpp头文件版本与库版本是否一致 Android NDK API级别(android34)是否匹配设备系统版本 ``` 结论:当前配置输出显示rkmpp支持正常,但建议通过实际编解码测试验证功能完整性。
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

hailushijie

您的鼓励是我创作最大的动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值