本文介绍了如何使libtool指向用户安装的库?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

限时删除!!

我正在尝试安装一个rubygem,它会继续尝试读取不可用的库.

I am trying to install a rubygem which keeps on trying to read a library which is not available.

grep: /usr/lib64/libgdbm.la: No such file or directory/bin/sed: can't read /usr/lib64/libgdbm.la: No such file or directorylibtool: link: /usr/lib64/libgdbm.la' is not a valid libtool archive

grep: /usr/lib64/libgdbm.la: No such file or directory/bin/sed: can't read /usr/lib64/libgdbm.la: No such file or directorylibtool: link: /usr/lib64/libgdbm.la' is not a valid libtool archive

为了解决此问题,我安装了自己的libgdbm并在makefile LDFLAGs中提供了libgdbm的路径,但是没有用.

In order to work around this, I installed my own libgdbm and provided the path to the libgdbm in the makefile LDFLAGs but to no avail.

非常感谢您的帮助.

推荐答案

此rubygem似乎在做脏事,因为任何干净的库搜索(-L或pkg-config)都会产生类似库/包"的消息找不到gdbm".特别是la文件上的grep-sed过程似乎真的很脏.确保圣诞老人知道这颗宝石的作者今年没有礼物.

This rubygem seems to do dirty stuff, since any clean library search (-L or pkg-config) would have resulted in a message like "library/package gdbm not found". And especially the grep-and-sed procedure on the la file seems really dirty. Make sure Santa knows that the author of this gem gets no presents this year.

gem可能已硬编码了libtool档案的路径.首先,尝试在gem的Makefile中grep表示/usr/lib64/libgdbm.la.更改硬编码的路径,并确保安装脚本对任何系统目录都没有写许可权,因为它似乎在sed s下运行.

The gem probably has the path to the libtool archive hardcoded. First of all, try to grep for /usr/lib64/libgdbm.la in the Makefile of the gem. Change the hardcoded path, and make sure the installation script has no write permissions on any system directories, because it seems to run wild with seds.

这篇关于如何使libtool指向用户安装的库?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

1403页,肝出来的..

09-08 09:52