53

This comes from automake, specifically from its AM_SANITY_CHECK macro, which is called from AM_INIT_AUTOMAKE, which is normally called early in configure.ac. The gist of this macro is: Check that the path to the source directory doesn't contain certain “unsafe” characters which can be hard to properly include in shell scripts makefiles. Check that ls ...


50

The correct way is: ./configure CFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" but this may not work with all configure scripts. It's probably better to set environment variables such as CPATH and LIBRARY_PATH (see gcc man page). An example: export CPATH=/usr/local/include export LIBRARY_PATH=/usr/local/lib export LD_LIBRARY_PATH=/usr/local/lib ...


44

If the file is called configure.ac, do $> autoconf Depends: M4, Automake If you're not sure what to do, try $> cat readme They must mean that you use "autoconf" to generate an executable "configure" file. So the order is: $> autoconf $> ./configure $> make $> make install


35

I believe the automake process involving a Makefile.in is something like this: Makefile.am | \'/ +--------------+ | automake | +--------------+ | \'/ Makefile.in | \'/ +--------------+ +--------------+ | ./configure |<-- | autoconf |<-- configure.in +--------------+ +--------------+ | ...


34

Executing (exit 1); is the simplest way of triggering an ERR trap. It will also trigger immediate exit if set -e is in effect. (Triggering the error condition requires a command to fail; exit with a failure value in a subshell causes the subshell to fail.) exit 1; will do neither of those things. So {(exit 1); exit 1;} can be used to first produce the ERR ...


25

it's just a convention that signifies the given file is for input; in my experience, these files tend to be a sort of generic template from which a specific output file or script results.


22

./configure usually creates a config.log file. It should contain the commands executed to check for the library.


17

That’s a sanity check, to ensure that the configuration script is correctly able to determine whether a header file is present or not: it asks the compiler to use a non-existant header, and checks that the compiler (correctly) fails. Note that your build goes on after that “error”... To figure out the cause of a build failure, you should generally work up ...


17

The configure script is a script that will configure the software that it was distributed with for compilation (if applicable) and installation. These scripts are often (as in this case) created by GNU autoconf (a tool used by developers specifically for creating portable configure scripts), which means that it will have at least a minimum of a certain set ...


15

The failsafe for generating a configure script is autoreconf -i, which not only takes care of calling autoconf itself, but also a host of other tools that may be needed.


12

In this case VAR=value ./configure the behavior depends on your current shell, while in this ./configure VAR=value the behavior depends on the configure-script. Some of the developers prefer the latter because they would like to choose whether to set variables within the script, rather than have someone magically set the script's variables from outside. ...


11

According to this thread, you should just install libXt-devel package and you should be fine. But perhaps you also should install xorg-x11-server-devel and libX11-devel? That would be: yum install xorg-x11-server-devel libX11-devel libXt-devel


11

To install to a custom directory, use this: ./configure --prefix=/desired/path make sudo make install By default, programs installed without the added prefix will be located in /usr/local/bin. To verify this, you can type which program_name after installation. If you install your program in a custom directory, it will be installed in /desired/path/bin. ...


9

The first syntax is correct. ./configure CFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib" However, it is strongly recommended to either use binary packages(7) or, if for whatever reason you absolutely need to build from source, make use of the ports(7) infrastructure, as explained by the FAQ section 15. Set up the ports tree as detailed in the FAQ....


9

This would help remove the problem sudo apt-get install libnautilus-extension-dev


9

The simple approach in your case is to install the open-vm-tools package. To address your question, there is no fool-proof way of listing all missing packages at once, mostly because this wasn’t designed in and configure scripts allow their authors to do anything — so there’s no way to know in advance how to continue and whether continuing is safe. An ...


8

There is no purpose for this as far as I can see, there is nothing that can be achieved directly by starting a subshell and then immediately exiting. Things like this are most likely a side effect of automatically generating code - in some cases there may be other commands executed in the subshell where having the exit 1 makes sense. Ultimately there is a ...


7

They are input files for the m4 macro preprocessor. Among other things, these files contain macros marked by @, that get expanded by m4.


7

The key here turned out to be the PKG_CONFIG_PATH environment variable. This was empty on a standard shell session on my system. There seem to be lots of directories with pkgconfig in the name, but to find the correct one I was able to use apt-file per this thread i.e. $ apt-file search fontconfig.pc libfontconfig1-dev: /usr/lib/x86_64-linux-gnu/pkgconfig/...


7

./configure scripts look for minix/config.h to determine whether they're building on Minix, or not. The test is defined in specific.m4. Autoconf sets a couple of variables up when it detects Minix, that's all it does — of course, specific builds may then react differently, but that depends on the project being built, not on Autoconf. As you've noticed, the ...


6

This option was added to address xterm flickering (on some setups) when resizing/scrolling back/long outputs. The initial patch was posted by a user on Archlinux forums. It was later integrated into xterm source code.


6

gnucash-2.6.9/packaging/gnucash.spec and gnucash-2.6.9/packaging/gnucash.spec.in are not part of the Debian packaging. They are the project's own spec files (the second one is a template) for packaging gnucash in RPM form. gnucash-2.6.9/configure.ac is also part of upstream. This is an Autoconf file which is used to generate the gnucash-2.6.9/configure. ...


5

The test is done by compiling a small dummy C program and by checking how the compiler names the output file. The following example is a simplified version of what configure is doing #!/bin/sh cat << EOT > dummy.c int main(int argc, char ** argv) { return 0; } EOT gcc -o dummy dummy.c if [ -f dummy.exe ] ; then # exe fi I would suggest ...


5

Yes, and no. Removing source file won't affect installed binaries and other resources, But you should keep them, in case you need to rebuild them. i.e when system libraries updated, it's likely for you to rebuild / re-link the binary


5

The 'configure' command is NOT a standard Linux/UNIX command. configure is a script that is generally provided with the source of most standardized type Linux packages and contains code that will "patch" and localize the source distribution so that it will compile and load on your local Linux system. Sometimes configure is put on your disk without the ...


5

You probably need to point the configure script at your configuration scripts: ./configure --with-tcltk --with-tcl-config=/usr/lib/tclConfig.sh --with-tk-config=/usr/lib/tkConfig.sh These are provided respectively by tcl-dev and tk-dev in Debian 8.


5

OK, take a look at gnucash-2.6.x/debian/rules. Find the line that says override_dh_auto_configure: (line 23 in my case), and add your overrides below it. In your case --enable-aqbanking is already there (for wheezy-backports at least), so simply delete it. More info can be found in the man page. Update: In addition, sometimes there's a variable in the ...


5

The actual error line in the log is: gcc: error trying to exec 'as': execvp: Permission denied The problem is probably that you have a file as in your PATH that is not the "real" assembler, normally in /bin/as. Change your PATH so that /bin and /usr/bin are first in the list, before your current order of /usr/local/jdk/bin /usr/lib64/qt-3.3/bin /home/...


5

Whenever you get messages about missing packages (or suggestions to modify your PKG_CONFIG_PATH) during a build, it usually indicates that you are missing the corresponding development package - which is typically separate from the runtime package that is normally installed on the system. In this case you have the most recent version of fontconfig but are ...


5

This is the solution to the issue mentioned above Follow the example to modify the configure file of R Then: tar xvf zlib-1.2.11.tar.gz cd zlib-1.2.11 ./configure --prefix=$HOME/Programme/zlib-1.2.11 make && make install tar zxvf bzip2-1.0.6.tar.gz cd bzip2-1.0.6 make -f Makefile-libbz2_so make clean modify the Makefile (original: CC=gcc after ...


Only top voted, non community-wiki answers of a minimum length are eligible