'/ usr / bin / ld：找不到-lecore_input'，但编译术语时存在libecore_input.so

我正在尝试编译术语terminal仿真器（顺便说一句，这有一些非常酷的东西，正在检查）。 但是，构build失败给我以下错误：

/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=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured 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-gnu Thread model: posix gcc 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_input collect2: error: ld returned 1 exit status 

当然libecore_input被安装：

• 在构build期间如何测量CPU，内存和磁盘使用情况？
• Clang版本2.8和3.1之间的C开发人员之间的任何实际区别？
• 在32位机器上创build一个64位Debian软件包
• 好的，Haskell的小编译器for linux？
• 在C项目中检查未使用的variables

 $ 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时，我也遇到同样的错误。 这里出了什么问题？ 我怎样才能build立程序？

更新

由于这个原因实际上是一个包装问题，我应该补充说我正在使用Debian Jessie和混合testing / unstable仓库。