The Linux already having both gcc & arm-gcc in the environment path: So I configure the gdb 6.6: compiled without error, but looks like gdb used the wrong compiler. So How to indicate the correct CC for gdb? I tried make CC=arm-none-linux-gnueabi-gcc, but will get the error: Answer Don’t use –target. It means something else to Autotools. Use –build and
Tag: autotools
autogen.sh: You need gtk-doc to build this package
I want to compile LXDE’s libfm from source, but when I run ./autogen.sh, it fails with this error: Answer After some experimenting, I figured out which package to install. It was: After that ./autogen.sh executed successfully and created the ./configure script. I also needed to run sudo apt-get build-dep libfm4 which installed other dependencies such as the Vala compiler.
make using autotools gives undefined reference errors while custom Makefile works fine
I’m trying to convert the build mechanism of ccextractor (Open source closed caption extractor) from custom Makefile to Autotools generated Makefile. Current Makefile looks like this: Building through above Makefile works fine. My Makefile.am looks like this: If I run make after autoreconf -i on above file, build fails with error: If I run ./configure as ./configure LIBS=”-lm -lz” build
Building C with automake under OS X and Linux
Currently I’m writing a RPC system for delay tolerant networks based on the Serval project from Australia (GitHub) in C. Mainly I’m developing on macOS El Capitan and everything works fine. But it is somewhat important that my code runs on macOS and Linux. But Linux makes trouble. I choose automake as my build system since this is the only
How to print value of C macro in configure
I have configure.in script. I want to invoke configure ( after autoheader && autoconf ) and see value of PAGE_SHIFT macro from system header page_types.h. Something like this: checking PAGE_SHIFT… 12 I’ve tried those: 1. Result: macro PAGE_SHIFT was detected, but haven’t been printed 2. Result: doesn’t work 3. Result: works, but can’t be used with cross-compile method was suggested
What is the proper way of including linux kernel config?
I’m porting an old version of a software that is partly a linux kernel module to EL5, after doing the relevant hacks, the horrible GNU autotools mess that is used to compile the thing (no, it does not compile the kernel module via kbuild 🙁 ) I keep getting lots of warnings ‘Including config.h is deprecated’ – I am told