需要GLIB-2.56来编译QEMU
我下载了glib-2.56,并使用./配置-prefix =/usr
和制作并制作安装
。但是,当我尝试编译QEMU
时,我仍然会遇到此错误。
我正在使用Ubuntu 16.04 LTS。
root@ubuntu-c:~/qemu/bin/debug/native# ../../../configure --enable-debug
ERROR: glib-2.56 gthread-2.56 is required to compile QEMU
知道如何解决错误吗?
I downloaded the glib-2.56 and configured it with ./configure --prefix=/usr
and make and make install
. But still I get this error when I try to compile qemu
.
I'm using Ubuntu 16.04 LTS.
root@ubuntu-c:~/qemu/bin/debug/native# ../../../configure --enable-debug
ERROR: glib-2.56 gthread-2.56 is required to compile QEMU
Any idea how to resolve the error?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
apt-get安装libglib2.0-dev
。总的来说,除非您真的< /strong>知道自己在做什么,否则您不应该在这样的 /usr中安装东西,希望您不会太糟糕的是安装了。一方面,Glib-2.56非常旧,可能比您的发行版随附的版本大得多。安装到 /usr可能意味着您只是降级了glib安装,下次您尝试启动一个程序,该程序需要较新的glib,由于缺少符号,它将失败。
我建议您重新安装
libglib2.0
package(apt-get-reinstall install install libglib2.0
)将Glib的副本/usr的副本返回到正确的版本。将来,您应该选择另一个位置来安装您构建的软件包...我建议使用jhbuild 要设置环境,以便例如使用您构建的共享库的可执行文件,而无需手动设置库路径(以及许多类似的内容,例如pkg-config
拾取您构建的代码而不是系统软件包)。apt-get install libglib2.0-dev
.In general you shouldn't be installing stuff in /usr like that unless you really know what you're doing, hopefully you didn't mess up your Ubuntu installation too badly. For one thing, glib-2.56 is very old, probably much older than the version which comes with your distro. Installing to /usr probably means you just downgraded your glib installation, and next time you try to start a program which requires a newer glib it will fail due to missing symbols.
I suggest you reinstall the
libglib2.0
package (apt-get --reinstall install libglib2.0
) to get the copy of glib in /usr back to the right version. In the future, you should pick another location to install packages you built... I suggest using jhbuild to set up the environment so you can have, for example, executables which use shared libraries you built without having to manually set the library path (as well as lots of similar stuff, likepkg-config
picking up the code you built instead of system packages).