linux – ‘usrbinld:找不到-lecore_input’但是在编译术语时存在libecore_input.so

linux – ‘usrbinld:找不到-lecore_input’但是在编译术语时存在libecore_input.so,第1张

概述我正在尝试编译 Terminology终端模拟器(顺便说一下,它做了一些很酷的事情,并且正在检查工作).但是构建失败会给我以下错误: /usr/bin/ld: cannot find -lecore_input 在使用make -n来打印正在(或将要运行)的命令之后,我发现以下行是失败的: gcc -g -O2 -o terminology terminology-about.o termin 我正在尝试编译 Terminology终端模拟器(顺便说一下,它做了一些很酷的事情,并且正在检查工作).但是构建失败会给我以下错误:

/usr/bin/ld: cannot find -lecore_input

在使用make -n来打印正在(或将要运行)的命令之后,我发现以下行是失败的:

gcc -g -O2   -o terminology terminology-about.o terminology-col.o terminology-config.o terminology-controls.o terminology-ipc.o terminology-keyin.o terminology-main.o terminology-media.o terminology-options.o terminology-options_Font.o terminology-options_theme.o terminology-options_themepv.o terminology-options_wallpaper.o terminology-options_colors.o terminology-options_behavior.o terminology-options_keys.o terminology-options_helpers.o terminology-options_vIDeo.o terminology-sel.o terminology-termio.o terminology-termcmd.o terminology-termiolink.o terminology-termpty.o terminology-termptydbl.o terminology-termptyesc.o terminology-termptyops.o terminology-termptygfx.o terminology-termptyext.o terminology-termptysave.o lz4/terminology-lz4.o terminology-utf8.o terminology-win.o terminology-utils.o terminology-dbus.o terminology-extns.o terminology-app_server.o terminology-app_server_eet.o -lelementary -lm -lefreet_mime -lefreet_trash -ledbus -ldbus-1 -lecore_con -leina -lpthread -leet -levas -lecore -lecore_evas -lecore_file -ledje -lemotion -lecore_input -lecore_imf -lecore_imf_evas -lecore_ipc -lefreet -lethumb_clIEnt   -leldbus

从正确的目录运行此命令并添加-v选项,我得到以下输出:

Using built-in specs.ColLECT_GCC=gccColLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapperTarget: x86_64-linux-gnuConfigured with: ../src/configure -v --with-pkgversion='Debian 4.8.2-16' --with-BUGurl=file:///usr/share/doc/gcc-4.8/README.BUGs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-ID --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-deBUG --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64 --with-multilib-List=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnuThread model: posixgcc version 4.8.2 (Debian 4.8.2-16) COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/liBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/4.8/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../:/lib/:/usr/lib/ColLECT_GCC_OPTIONS='-v' '-g' '-O2' '-o' 'terminology' '-mtune=generic' '-march=x86-64' /usr/lib/gcc/x86_64-linux-gnu/4.8/collect2 --sysroot=/ --build-ID --eh-frame-hdr -m elf_x86_64 --hash-style=gnu -dynamic-linker /lib64/ld-linux-x86-64.so.2 -o terminology /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crt1.o /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.8/crtbegin.o -L/usr/lib/gcc/x86_64-linux-gnu/4.8 -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../../../lib -L/lib/x86_64-linux-gnu -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.8/../../.. terminology-about.o terminology-col.o terminology-config.o terminology-controls.o terminology-ipc.o terminology-keyin.o terminology-main.o terminology-media.o terminology-options.o terminology-options_Font.o terminology-options_theme.o terminology-options_themepv.o terminology-options_wallpaper.o terminology-options_colors.o terminology-options_behavior.o terminology-options_keys.o terminology-options_helpers.o terminology-options_vIDeo.o terminology-sel.o terminology-termio.o terminology-termcmd.o terminology-termiolink.o terminology-termpty.o terminology-termptydbl.o terminology-termptyesc.o terminology-termptyops.o terminology-termptygfx.o terminology-termptyext.o terminology-termptysave.o lz4/terminology-lz4.o terminology-utf8.o terminology-win.o terminology-utils.o terminology-dbus.o terminology-extns.o terminology-app_server.o terminology-app_server_eet.o -lelementary -lm -lefreet_mime -lefreet_trash -ledbus -ldbus-1 -lecore_con -leina -lpthread -leet -levas -lecore -lecore_evas -lecore_file -ledje -lemotion -lecore_input -lecore_imf -lecore_imf_evas -lecore_ipc -lefreet -lethumb_clIEnt -leldbus -lgcc --as-needed -lgcc_s --no-as-needed -lc -lgcc --as-needed -lgcc_s --no-as-needed /usr/lib/gcc/x86_64-linux-gnu/4.8/crtend.o /usr/lib/gcc/x86_64-linux-gnu/4.8/../../../x86_64-linux-gnu/crtn.o/usr/bin/ld: cannot find -lecore_inputcollect2: error: ld returned 1 exit status

当然安装了libecore_input:

$sudo updatedb$locate ecore_input.so/usr/lib/x86_64-linux-gnu/libecore_input.so/usr/lib/x86_64-linux-gnu/libecore_input.so.1/usr/lib/x86_64-linux-gnu/libecore_input.so.1.7.7

/usr/lib / x86_64-linux-gnu /位于gcc输出的liBRARY_PATH中,并在collect2命令中显示为-L选项.

当我尝试使用gcc-4.7时,我也会遇到同样的错误.这里出了什么问题?如何构建程序?

更新

由于这个原因实际上是一个包装问题,我应该补充一点,我正在使用Debian JessIE和混合测试/不稳定的存储库.

解决方法 这是由于/usr/lib/x86_64-linux-gnu/libecore_input.so由于Debian打包问题和混合测试/不稳定存储库的使用而导致的死链接.

/usr/lib/x86_64-linux-gnu/libecore_input.so链接是libecore-dev包的一部分,而库本身是libecore-input1的一部分.已安装的libecore-dev版本为1.8.6-1,而libecore-input1为1.7.7版本.因此libecore_input.so链接的目标是libecore_input.so.1.8.6,它不存在.虽然libecore-dev已经为其他库版本化了依赖项,但libecore-input1是间接依赖项,而且没有正确版本化.这可能是一个错误,因为如果包包含指向共享库的链接,那么它的依赖关系应该确保安装了正确的库版本.

解决方案只是升级libecore-input包.

总结

以上是内存溢出为你收集整理的linux – ‘/usr/bin/ld:找不到-lecore_input’但是在编译术语时存在libecore_input.so全部内容,希望文章能够帮你解决linux – ‘/usr/bin/ld:找不到-lecore_input’但是在编译术语时存在libecore_input.so所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错,欢迎将内存溢出网站推荐给程序员好友。

欢迎分享,转载请注明来源:内存溢出

原文地址: http://outofmemory.cn/yw/1029132.html

(0)
打赏 微信扫一扫 微信扫一扫 支付宝扫一扫 支付宝扫一扫
上一篇 2022-05-23
下一篇 2022-05-23

发表评论

登录后才能评论

评论列表(0条)

保存