autoconf

How do I get autotools to compile with the Intel compiler?

由 ℡╲_俬逩灬. 提交于 2019-12-01 14:39:42
问题 I want my code to compile with the Intel compiler(s) or with gcc/g++ depending on a configure argument. Is this possible? What do I need to put in my configure.ac and Makefile.am files to make this happen? 回答1: If you want to use a compiler other than gcc when you compile, pass 'CC=/path/to/compiler' as an argument to configure. (That is, run ./configure CC=/path. Do not use the form CC=/path ./configure.) If you want the default compiler to be something other than gcc, you can put CC=${CC-

Where to put helper-scripts with GNU autoconf/automake?

由 大城市里の小女人 提交于 2019-12-01 11:46:49
I'm working on a project that will be distributed with GNU autoconf/automake, and I have a set of bash scripts which call awk scripts. I would like the bash scripts to end up in the $PATH, but not the awk scripts. How should I insert these into the project? Should they be put in with other binaries? Also, is there a way to determine the final location of the file after installation? I presume that /usr/local/bin isn't always where the executables end up... Add something like this to Makefile.am scriptsdir = $(prefix)/bin scripts_DATA = awkscript1 awkscript2 In this case it will install

Correct installation of config.h for shared library using autotools

由 早过忘川 提交于 2019-12-01 06:06:44
问题 I am converting a C++ program which uses the autotools build system to use a shared library, introducing the use of libtool. Most of the program functionality is being placed in the shared library, which is loaded by the main program, so that the common code can be accessed by other programs in future. Throughout the program and library sources the autoheader generated config.h is used with the usual macro: #if HAVE_CONFIG_H # include <config.h> #endif In configure.ac I use the macro to

How do I troubleshoot boost library/header inclusion via autoconf/automake?

由 我的未来我决定 提交于 2019-12-01 01:04:55
I'm new to autom4te, and I'm trying to use autoconf/automake to build and link a C++ program on multiple architectures. Complicating the linking is the fact that the project requires boost (filesystem, system, program_options). I'm using boost.m4 (from http://github.com/tsuna/boost.m4/tree/ ), and it seems to locate all the libraries and headers successfully. Unfortunately, linking still fails, leaving me confused. These are the relevant lines of configure.ac : AC_CONFIG_MACRO_DIR([m4]) # ... AC_PROG_CXX AC_PROG_LIBTOOL # ... BOOST_REQUIRE([1.41.0]) BOOST_FILESYSTEM BOOST_SYSTEM BOOST_PROGRAM

How do I troubleshoot boost library/header inclusion via autoconf/automake?

由 寵の児 提交于 2019-11-30 19:32:50
问题 I'm new to autom4te, and I'm trying to use autoconf/automake to build and link a C++ program on multiple architectures. Complicating the linking is the fact that the project requires boost (filesystem, system, program_options). I'm using boost.m4 (from http://github.com/tsuna/boost.m4/tree/), and it seems to locate all the libraries and headers successfully. Unfortunately, linking still fails, leaving me confused. These are the relevant lines of configure.ac : AC_CONFIG_MACRO_DIR([m4]) # ...

With autoconf/automake, how do I specify include file paths?

由 痞子三分冷 提交于 2019-11-30 17:53:09
问题 Let's say I want to have the generate makefile pass some specific header paths to g++. What do I need to add to configure.ac or Makefile.am to specify this? (note - I do not want to pass it in the CPPFLAGS with ./configure. I want those paths baked in before that step) EDIT: Specifically, I want to to include let's say /usr/include/freetype and /mypath/include. I put AC_CHECK_HEADERS([freetype/config/ftheader.h]) and it passes, but doesn't seem to add it to the -I passed to g++. I also did

autotools: force make not to rebuild configure/Makefile

由 雨燕双飞 提交于 2019-11-30 15:34:28
问题 I have a project with autotools: automake, autoconf. I want to prohibit make from remaking files configure , Makefile.in , etc; just to do compile job. Some of files are edited by hand, and I know that I should not to do this. (Or the project was updated from CVS with all generated files stored in CVS). But at the moment I have no correct version autotools installed. What must be modification times of this files (which must be newer/older): aclocal.m4 configure.in confdb/ax_prefix_config_h.m4

GNU Autotools: rebuild without version info

由 爷，独闯天下 提交于 2019-11-30 13:13:51
I need to build a lib that is configured with autotools. The usual configure && make && make install steps produce versioned shared lib, something like libfoo.so.x.x Is it possible to modify configure.ac or Makefile.am (and of course follow up with autoreconf ) so that un-versioned lib is build. Thank you! Yes, assuming that the library is built with libtool , you can remove the version information by adding the -avoid-version flag to the library's LDFLAGS. For example, if before there was libfoo_la_LDFLAGS = -version-info 1:0 you would change it to libfoo_la_LDFLAGS = -avoid-version . After

nginx+ftp搭建图片服务器修改nginx 配置文件中root路径403错误

由 给你一囗甜甜゛ 提交于 2019-11-30 11:27:52
关于参考《 nginx+ftp搭建图片服务器 》【https://my.oschina.net/iyinghui/blog/750459】遇到问题总结： 问题1： 在安装nginx的时候如果提示make命令不认识错误 解决方案： 先安装make命令： yum -y install gcc automake autoconf libtool make 问题2： 在修改了nginx默认路径的时候在访问nginx提示403错误。 文章具体位置： 解决方案： 在nginx配置文件最上面一行被注释掉的 如果没有修改最上面一行： 修改成root用户后，重新加载nginx配置文件。 OK。可以正常访问了 注：别使用root用户。最好给nginx创建一个单独的用户 来源： oschina 链接： https://my.oschina.net/u/930697/blog/791080

Automake generating binaries to bin/ instead of in src/

由 旧时模样 提交于 2019-11-30 06:27:26
I searched for the answer to this question but couldn't find any good. Maybe they're old and something has changed, so I ask again. I have a directory structure as: my_project src bin I want that, when I do make in the root dir, the binaries are put in ./bin, instead of cluttering ./src. But how? EDIT: I am using C++. My Makefile.am has nothing special. Just the bin_PROGRAM and _SOURCES variables. When I run make, the binaries generated are put into ./src. I simply want them in ./bin. You've got the wrong idea here. Your build tree is wherever you run configure . That's how autoconf is
订阅 autoconf