libtool

wwsearch编译问题记录

由 老子叫甜甜 提交于 2019-12-20 17:11:12
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> wwsearch 编辑问题记录由一个俗人(wechat:dotzcv)整理 CMake构建问题：Could NOT find Threads (missing: Threads_FOUND) cmake版本低 https://blog.csdn.net/github_30605157/article/details/1027777412 2.依赖包安装 # 首先安装各种依赖包如下： yum install gcc gcc-c++ # 安装c++ # 安装boost yum install boost boost-devel boost-doc # 安装glog 以及其他依赖包 yum install glog glog-devel kyotocabinet kyotocabinet-devel marisa-devel opencc-devel yaml-cpp yaml-cpp-devel gtest gtest-devel # ibus-rime还需要什么 yum install libnotify zlib zlib-devel gflags gflags-devel 3.报错时候 遇到FlagRegisterer问题 和google库相关问题 可以尝试安装 1）安装 GFlags git clone

在C ++标识符中使用下划线的规则是什么？

由 你。 提交于 2019-12-15 21:55:05
【推荐】2019 Java 开发者跳槽指南.pdf(吐血整理) >>> 在C ++中，通常使用某种前缀来命名成员变量，以表示它们是成员变量，而不是局部变量或参数。 如果您来自MFC背景，则可能会使用 m_foo 。 我也偶尔见过 myFoo 。 C＃（或者可能只是.NET）似乎建议仅使用下划线，例如 _foo 。 C ++标准允许吗？ #1楼 是的，下划线可以在标识符的任何地方使用。 我相信规则是：第一个字符中的az，AZ，_中的任何一个，其后几个字符中的+ 0-9。 下划线前缀在C代码中很常见-单个下划线表示“专用”，通常保留双下划线以供编译器使用。 #2楼 从 MSDN ： 在所有范围内，C ++实现均保留在标识符的开头使用两个连续的下划线字符（__）或使用单个下划线后跟一个大写字母。 对于具有文件范围的名称，应避免使用前导下划线后跟小写字母，因为这可能与当前或将来的保留标识符冲突。 这意味着您可以使用单个下划线作为成员变量前缀，只要其后跟一个小写字母即可。 这显然来自C ++标准的17.4.3.1.2节，但是我找不到在线完整标准的原始资料。 另请参阅 此问题 。 #3楼 规则（在C ++ 11中未更改）： 在任何范围内都保留，包括用作 实现 宏： 以下划线开头的标识符，紧随其后的是大写字母 包含相邻下划线（或“双下划线”）的标识符 在全局名称空间中保留： 下划线开头的标识符

libtool doesn't provide library dependencies to link

由 给你一囗甜甜゛ 提交于 2019-12-14 03:52:20
问题 I am using libtool 2.2.6b on ubuntu lucid, and libtool 2.4.2 on ubuntu precise. On lucid my project will link properly. On precise it fails to link. Here's example code that demonstrates my problem; configure.ac AC_INIT([ltp], [0.0.1], [someone]) AM_INIT_AUTOMAKE AC_CONFIG_HEADERS([config.h]) AC_CONFIG_MACRO_DIR([.m4]) AC_CONFIG_FILES([Makefile foo/Makefile bar/Makefile wah/Makefile]) AC_PROG_CXX AC_PROG_LIBTOOL AM_SANITY_CHECK AC_LANG_CPLUSPLUS AC_OUTPUT Makefile.am SUBDIRS = foo bar wah

Why does building Apache Thrift fail with “error: cannot find the library”?

由 若如初见. 提交于 2019-12-13 10:33:01
问题 Trying to build Apache Thrift on Fedora 23 from the source in the official git repository fails with a "cannot find the library... or unhandled argument" error message: ... make[5]: Entering directory '/home/ssouth/Source/Apache Thrift/git-wip-us.apache.org/repos/asf/thrift/lib/cpp/test' /bin/sh ../../../libtool --tag=CXX --mode=link g++ -Wall -Wextra -pedantic -g -O2 -std=c++11 -L/usr/lib64 -o Benchmark Benchmark.o libtestgencpp.la -lssl -lcrypto -lrt -lpthread libtool: error: cannot find

Get libtool library output filename

由 ╄→尐↘猪︶ㄣ 提交于 2019-12-13 06:48:17
问题 I'm trying to define an Automake rule that will generate a text file containing the full path to a libtool library that will be built and installed by the same Makefile. Is there a straightforward way of retrieving the output filename for a libtool library (with the correct extension for the platform the program is being built on)? For example, I am trying to write something like this: lib_LTLIBRARIES = libfoo.la bar.txt: echo $(prefix)/lib/$(libfoo_la) >$@ Where $(libfoo_la) would expand to

How, when, where to set script variables of libtool? (e.g. hardcode_minus_L)

由 非 Y 不嫁゛ 提交于 2019-12-13 03:12:48
问题 Long story short: I worked on relative rpath linking with this script (that uses automake, autoconf, libtool). The problem is that the final rpath / runpath entry in the binary executable or so file still has the absolute path: it turned out libtool is configured by default like this with hardcode_libdir_flag_spec to include any -L value if it's set in LDFLAGS The only question remains: how and at which point (what's the proper way) can I set other libtool variables, like hardcode_minus_L .

How to get more info if lt_dlopen fails?

由 风流意气都作罢 提交于 2019-12-12 20:37:13
问题 I'm calling lt_dlopen and getting a generic file not found error (translated errno text). How can I get more information about what is actually failing, as the file is definitely there. This is a C++ program loading a C++ library. Otherwhere in the same program I use the same command to open other libraries without a problem, thus I fear it might be something specific to this library. I've used ldd and all those dependencies of the library are met. 回答1: I stumbled across something that kind

X-I.: command not found, and failed to build certain kind of software, what's wrong?

由 你离开我真会死。 提交于 2019-12-12 14:12:09
问题 the error message is as follows: ./libtool: line 1129: X-I.: command not found ./libtool: line 1129: X-DLT_CONFIG_H=<config.h>: command not found ./libtool: line 1129: X-DLTDL: command not found ./libtool: line 1129: X-I.: command not found ./libtool: line 1129: X-I.: command not found ./libtool: line 1129: X-Ilibltdl: command not found ./libtool: line 1129: X-I./libltdl: No such file or directory ./libtool: line 1129: X-I./libltdl: No such file or directory ./libtool: line 1129: X-g: command

How do I link against libtool static la library?

由 偶尔善良 提交于 2019-12-12 13:29:09
问题 I have compiled this library successfully. It generates a libcds2.la file that I am trying to link into my own project. I have all files (including the .h file) in the same directory as my project file. When I try to link and use the functions of said library, using: g++ -o test -I/opt/include/ -L/opt/lib/ -lcds2 libcdsNoptrs.cpp util.cpp comes back with ./test: error while loading shared libraries: libcds2.so.2: cannot open shared object file: No such file or directory whatever that is. But

Libtool issue while compiling Liblinphone

由 安稳与你 提交于 2019-12-12 05:14:28
问题 I'm trying to compile this lib: https://github.com/BelledonneCommunications/linphone-iphone During generation I get this: /linphone-iphone/submodules/build/..//externals/speex/libspeex/cb_search.c libtool: Version mismatch error. This is libtool 2.4.6, but the libtool: definition of this LT_INIT comes from libtool 2.4.2. libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 libtool: and run autoconf again. make[4]: *** [cb_search.lo] Error 63 make[3]: *** [all-recursive]
订阅 libtool