I'm trying to make a small change to an automake build. The system to modify uses configure.ac and Makefile.am inputs. For a single object file within one subdirectory I have to invoke a script before compiling, to patch config info into the build. I don't see the right location to allow such pre-processing ahead of compiling this specific C file. What I've tried is to insert an additional target into all: all-am But this seems not to be the way to go and in addition I wasn't able to figure how to overload this generated line.

I have a question when working with autotools, specifically when working with generating configure scripts by running autoreconf -fi I'll get these warnings: libtoolize: putting auxiliary files in '.'. libtoolize: copying file './ltmain.sh' libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac, libtoolize: and rerunning libtoolize and aclocal. libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.ac:12: installing './compile' configure.ac:15: installing './config.guess' configure.ac:15: installing './config.sub' configure.ac:6: installing './install-sh' configure.ac:6: installing './missing' Makefile.am: installing './INSTALL' src/Makefile.am:5: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/Makefile.am: installing './depcomp' src/filteropt/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/memory/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/pagemanager/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/raster/Makefile.am:5: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/raster/blendSource/Makefile.am:3: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') After this I can manually go through and change INCLUDES to AM_CPPFLAGS as well as adding -I m4 but shouldn't I be able to update the configure files so that I do not get these warnings? Where would I make those edits so that I can avoid these warnings?

- On ubuntu 24.04 - GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu) - automake (GNU automake) 1.16.5 - autoconf (GNU Autoconf) 2.71 From [automake doc](https://www.gnu.org/software/autoconf/manual/autoconf-2.71/autoconf.pdf) >${var:+value} Old BSD shells, including the Ultrix sh, don’t accept the colon for any shell substitution, and complain and die. Similarly for ${var:=value}, ${var:?value}, etc. However, all shells that support functions allow the use of colon in shell substitution, and since m4sh requires functions, you can portably use null variable substitution patterns in configure scripts. The substituion does not happen in the following example Given : SOURCE_DATE_EPOCH = 333 src/Makefile.am

bin_PROGRAMS = myproject
myproject_SOURCES = main.c

param6=123
a=${param6:+xyz}
$(info ####### a = $(a)#######)

$(info ####### $(SOURCE_DATE_EPOCH) #######)
$(info ##########  ${SOURCE_DATE_EPOCH:+ -d @${SOURCE_DATE_EPOCH}})

output :

####### a = #######
####### 333 #######
##########

The third info log isn't printing SOURCE_DATE_EPOCH value despite it being defined Is it possible to use variable substitution like ":+" in automake files ?

I am using a fairly dated Ubuntu 18/RHEL6 system with old build tools, I'm trying to update it but don't want to crush the existing tools installation. I created the following script which installed autoconf as an alternative, but I am unsure how to bring over the autoconf macros in the installed share. > autoreconf --version
autoreconf (GNU Autoconf) 2.71
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
,
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille. Then when I try to run autoreconf --install --force, it would tell me it couldn't find the macro...

autoreconf --verbose --install --force
autoreconf: export WARNINGS=
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
autoreconf: configure.ac: not using Intltool
autoreconf: configure.ac: not using Gtkdoc
autoreconf: running: aclocal --force -I m4
autoreconf: running: /opt/autoconf/bin/autoconf --force
configure.ac:1040: error: possibly undefined macro: m4_ifdef
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: error: /opt/autoconf/bin/autoconf failed with exit status: 1

Is there a way to accomplish what I'm trying to do? Having automake, autoconf, libtool, etc as alternatives? The script (I have a similar script for automake, pkgconf, etc):

#!/bin/bash
set -e

WHAT=autoconf
VERSION=2.71

function install() {
    [ $# -eq 0 ] && { run_error "Usage: install "; exit; }
    local VERSION=${1}
    local TARBALL=${WHAT}-${VERSION}.tar.xz
    local URL=ftp://ftp.gnu.org/gnu/${WHAT}/${TARBALL}
    local WHERE=/tmp/update-${WHAT}
    echo "Downloading ${URL}"
    mkdir -p ${WHERE}
    cd ${WHERE}
    curl -L --create-dirs -o ${TARBALL} ${URL}

    if [ -f "${TARBALL}" ]; then
        tar -xf ${TARBALL}
        cd ${WHAT}-${VERSION}/
        ./configure --prefix="/opt/${WHAT}"
        make
        echo "Installing..."
        sudo make install
        echo -e "${TARBALL} installed \e[1;32mOK\e[39m"
    else
        echo -e "Cannot download ${URL}"
        exit 1
    fi
}

function install_alternatives() {
    for fullpath in /opt/${WHAT}/bin/* ; do
        local NAME="$(basename ${fullpath})"
        #echo "sudo update-alternatives --install /usr/local/bin/${NAME} ${NAME} ${fullpath} 50"
        sudo update-alternatives --install /usr/local/bin/${NAME} ${NAME} ${fullpath} 50
        . ~/.profile
    done
}

function remove_alternatives() {
    for fullpath in /opt/${WHAT}/bin/* ; do
        local NAME="$(basename ${fullpath})"
        #echo "sudo update-alternatives --remove ${NAME} ${fullpath}"
        sudo update-alternatives --remove ${NAME} ${fullpath}
        . ~/.profile
    done
}

if declare -f "$1" > /dev/null
then
    "$@"
else
    install ${VERSION}
    install_alternatives
fi

I'm using autoconf and automake to build a tiny project. For the project's manual, I've used OpenBSD's native [mdoc format](http://man.openbsd.org/mdoc) , and the installable man-formatted manual is generated from this using [the mandoc utility](http://man.openbsd.org/mdoc) . The man-formatted manual will be installed as the actual manual with make install, as some systems do not grok mdoc properly, or at all. In the project's doc directory, I have a Makefile.am file that currently looks like the following (the manual is for a utility called shell): dist_man1_MANS= shell.man EXTRA_DIST= shell.mdoc shell.man: shell.mdoc $(mandoc) -T man shell.mdoc >shell.man $(mandoc) will be properly expanded to the full path of the mandoc formatter (this variable is set by the configure script). This allows me to run make dist which creates shell.man and then creates a compressed tar archive containing both the source mdoc manual and the generated man manual along with the rest of the project's distribution files: $ tar tzf shell-toolbox-20180401.tar.gz ... shell-toolbox-20180401/doc/Makefile.am shell-toolbox-20180401/doc/shell.man shell-toolbox-20180401/doc/Makefile.in shell-toolbox-20180401/doc/shell.mdoc This tar archive can later be used to successfully build and install the project, and its manual. So far so good. However, if I run [make distcheck](http://www.gnu.org/software/automake/manual/html_node/Checking-the-Distribution.html) (because I'd like to make sure it absolutely positively works): $ make distcheck ... checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for mandoc... /usr/bin/mandoc checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating doc/Makefile config.status: creating src/shell Making all in src Making all in doc /usr/bin/mandoc -T man shell.mdoc >shell.man mandoc: shell.mdoc: ERROR: No such file or directory *** Error 3 in shell-toolbox-20180401/_build/sub/doc (Makefile:459 'shell.man') *** Error 1 in shell-toolbox-20180401/_build/sub (Makefile:345 'all-recursive') *** Error 1 in /home/myself/local/build/shell-toolbox (Makefile:576 'distcheck') It seems as if the source mdoc file is not available in the build directory when the manual needs to be built: $ ls shell-toolbox-20180401/_build/sub/doc total 32 -rw-r--r-- 1 myself myself 14989 Apr 1 21:35 Makefile -rw-r--r-- 1 myself myself 0 Apr 1 21:35 shell.man The zero-length shell.man file comes from the failed mandoc run. The source is available in the unpacked archive, but just not copied over to the _build/sub/doc directory: $ ls -l shell-toolbox-20180401/doc total 48 -r--r--r-- 1 myself myself 178 Apr 1 21:23 Makefile.am -r--r--r-- 1 myself myself 13925 Apr 1 21:23 Makefile.in -r--r--r-- 1 myself myself 3443 Apr 1 21:27 shell.man -r--r--r-- 1 myself myself 3319 Apr 1 18:54 shell.mdoc **Question**: What automake magic do I have to apply to get make distcheck to properly copy the mdoc source to the build directory before it attempts to generate the man-formatted manual? I'm looking for a "proper" way of doing this, not a hack. I tried using man1_SOURCES= shell.mdoc but that makes automake complain with doc/Makefile.am:2: warning: variable 'man1_SOURCES' is defined but no program or doc/Makefile.am:2: library has 'man1' as canonical name (possible typo) --- Another way to provoke this error is to manually do a [VPATH build](http://www.gnu.org/software/automake/manual/html_node/VPATH-Builds.html) (which is basically what's happening when doing make distcheck): $ make distclean $ mkdir t $ cd t $ ../configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/local/bin/gmkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes checking for mandoc... /usr/bin/mandoc checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating doc/Makefile config.status: creating src/shell $ make Making all in src Making all in doc /usr/bin/mandoc -T man shell.mdoc >shell.man mandoc: shell.mdoc: ERROR: No such file or directory *** Error 3 in doc (Makefile:459 'shell.man') *** Error 1 in /home/myself/local/build/shell-toolbox/t (Makefile:345 'all-recursive') $ ls -l doc total 32 -rw-r--r-- 1 myself myself 14589 Apr 1 22:42 Makefile -rw-r--r-- 1 myself myself 0 Apr 1 22:42 shell.man

I know I can use printf to automate parameter entry for some programs. For example: printf 'user_name\npassword' | sudo openconnect URL But this does not work for npm create qwik@latest. Because it has a step that is option selection. I know I can provide -y for npm to suppress its confirmation message. But I know that Qwik does not have [non-interactive CLI yet](https://github.com/BuilderIO/qwik/issues/2059) . Is there any way that I can automate this command? I'm using debian 11 bash.

I have installed samba and winbind in rhel8. I was trying to automate the domain join process as well. But when try it manually it is working as expected when we enter the password manually for "**service-user-account**" for domain join. But I don't see any command to automate with the password. I have tried with one of the below command, but it is giving an error. **Command:** net ads join -U $ad_user%$password but I am getting below error. I have put the *service account user and password in variable*. **error:** Failed to join domain: failed to lookup DC info for domain 'example.com' over rpc: The attempted logon is invalid. This is either due to a bad username or authentication information. **Kindly help me to automate this step**. Appreciate your kind support!. Thanks Uma

In a Makefile.am file I saw the following entry:

EXTRA_DIST = bootstrap \
	ChangeLog \
	config/config.rpath \
	m4/ax_pthread.m4 \
	m4/iconv.m4 \
	MacOSX/someheader.h
    [...]

and I wanted to find out what it means, but the documentation doesn't seem to define what "distribution" actually means. It doesn't mean "compiled lib", does it? It's a source code distribution of some sort? (why would anyone need that? We can just use git or zip the root folder?) Hope someone can clarify.

I am trying to build using ./configure. I have 1. Three include directories -I/path1/include -I/path2/include -I/path3/include 2. Two link directories -L/path1/lib -L/path2/lib 3. Two -l flag options -ltensorflow -lasan 4. Two compile flags -O3 -g How can I put all these flags effectively as options in ./configure?

[The autoconf AX_CHECK_X86_FEATURES](https://www.gnu.org/software/autoconf-archive/ax_check_x86_features.html) will test for -mavx, -mavx2, etc and add it to CFLAGS. What is the right way to propagate it to CXXFLAGS too? Is it "clean" to always add CFLAGS to CXXFLAGS? It doesn't seem so... But my C++ code contains some avx2 code, so I need this.

configure.ac has precious variables, which are supposed to be subbed-in when calling configure, e.g. configuring the location of the system Lua interpreter as a precious variable[2] :

configure.ac:
  ...
  dnl Make LUA a precious variable.
  AC_ARG_VAR([LUA], [The Lua interpreter, e.g. /usr/bin/lua5.1])

command line:

./configure LUA=lua-5.3.6/src/lua

OR

export LUA=lua-5.3.6/src/lua
./configure

However, I'd like to hard code the location of the Lua interpreter instead of having to ask users to add it as an environment variable every time. How can I hard code it into configure.ac? https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Setting-Output-Variables.html

I am trying to install avro-keyboard on Kali Linux but I am getting this error message on folowing this step from the tutorials:

root@al-ajal:~# apt-get install git ibus libibus-1.0-dev automake autoconf gjs gir1.2-ibus-1.0 ibus-1.0

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'libibus-1.0-5' for regex 'ibus-1.0'
Note, selecting 'gir1.2-ibus-1.0' for regex 'ibus-1.0'
Package autoconf is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Package automake is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package ibus
E: Unable to locate package libibus-1.0-dev
E: Couldn't find any package by glob 'libibus-1.0-dev'
E: Couldn't find any package by regex 'libibus-1.0-dev'
E: Package 'automake' has no installation candidate
E: Package 'autoconf' has no installation candidate

What's wrong? I did not find any discussion regarding what to do if autoconf or automake is missing in the tutorials.

I have GNU Guile 2.2.6 installed on my system as guile, and GNU Guile 3.0.5 installed as guile3. I would like to install the info manuals for both versions. Both want to install the info files as /usr/share/info/guile.info{,-1,-2,..}, so whichever I install last overwrites the manual for the other version. How can I keep both versions? Version 2.2.6 is provided by my package manager, and I'm currently building version 3.0.5 like this:

./configure --prefix=/usr --program-suffix=3
make
sudo make install

Ideally info guile would bring up the documentation for version 2.2.6, while info guile3 would show the docs for version 3.0.5.

I am trying to build rsync 1.7.0 from git source. ~~~ $ autoreconf $ ./configure : config.status: error: cannot find input file: `config.h.in' ~~~ If I copy config.h.in from rsync-1.7.0.tar.gz, ./configure completes. But make fails: ~~~ $ make gcc -I. -I. -g -O2 -c rsync.c -o rsync.o In file included from rsync.c:20: rsync.h:274:10: fatal error: proto.h: No such file or directory 274 | #include "proto.h" | ^~~~~~~~~ compilation terminated. make: *** [Makefile:29: rsync.o] Error 1 ~~~ If I copy proto.h from rsync-1.7.0.tar.gz, it works. How do I create the missing proto.h and config.h.in that are in the tar file?

Slurm is an open source project using gnu autotools to build. The problem is as follows: when applying autoreconf to the project, the Makefile.in files created are missing the runstatedir macro. I'm using Fedora 32, and after filing a bug with the project owners (Schedmd) I've received a WONTFIX resolution with the following answer : > This is due to differences between the Debian/Ubuntu vs. Fedora > autotools packaging. > > The build tooling is managed on Debian/Ubuntu - which does not produce > such a diff today. Thus I won't be applying this. My question is - can I modify anything in the project to make it "universally" correct - that is - ensure autoreconf does the right thing on both Fedora and Ubuntu? The Fedora autotools package used is current as of this writing: rpm autoconf-2.69-33.fc32.noarch I have no idea which autoconf version is used in Debian/Ubuntu.

After compiling and installing GNU automake 1.15, I get this error whenever I run automake: Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/\${ <-- HERE ([^ \t=:+{}]+)}/ at /usr/local/bin/automake line 3936 I am running perl v5.22.0.

I'm building autoconf-2.68. I'm not very familiar with this tool. However, after analysing the Makefiles, I find that the build fails when running the script autoconf-2.68/bin/autom4te. I'm having this error: bash: ./autom4te :/home/user/workspace/output: bad interpreter: No such file or directory Some analysis that I have done echo $SHELL /bin/bash In the autom4te I find this line in the BEGIN function $ENV{'SHELL'} = '/bin/sh' if ($^O eq 'dos'); Could this cause a problem? Any idea to resolve? **Edit** The first lines of autom4te are: #! /home/user/Workspace/output/xx_yyyyyyy_pp88_tttttt_uuuuuuu_aaa_bbbbbbb/host/usr/bin/perl -w # -*- perl -*- # Generated from autom4te.in; do not edit by hand. eval 'case $# in 0) exec /home/user/Workspace/output/xx_yyyyyyy_pp88_tttttt_uuuuuuu_aaa_bbbbbbb/host/usr/bin/perl -S "$0";; *) exec /home/user/Workspace/output/xx_yyyyyyy_pp88_tttttt_uuuuuuu_aaa_bbbbbbb/host/usr/bin/perl -S "$0" "$@";; esac' if 0; The script caller: autoconf.in: $(srcdir)/autoconf.as $(m4sh_m4f_dependencies) $(MY_AUTOM4TE) --language M4sh --cache '' --melt $(srcdir)/autoconf.as -o $@ MY_AUTOM4TE is defined as: MY_AUTOM4TE = \ autom4te_perllibdir='$(top_srcdir)'/lib \ AUTOM4TE_CFG='$(AUTOM4TE_CFG)' $(top_builddir)/bin/autom4te \ -B '$(top_builddir)'/lib -B '$(top_srcdir)'/lib # keep ` '

For example, would it not be beneficial to have -jN > nrcpus during the configure phase, where CPU load is low? Then have -jN = nrcpus during compilation, where load should be evenly distributed to each CPU? How difficult would this be to implement in a build environment? Would it require changing each configuration file for each step? Is it possible to automate for multiple projects, given they use the same "make" program? This is assuming that the workload is never I/O bound.

I've downloaded [this](https://github.com/linuxmint/muffin) window manager from github and it has a autogen.sh script but it failed each time. I don't know what could happen or how to fix it: Output from ./autogen.sh: /usr/bin/gnome-autogen.sh checking for autoreconf >= 2.53... testing autoreconf... found 2.69 checking for glib-gettext >= 2.2.0... testing glib-gettextize... found 2.40.0 checking for intltool >= 0.25... testing intltoolize... found 0.50.2 checking for pkg-config >= 0.14.0... testing pkg-config... found 0.26 checking for gnome-doc-utils >= 0.4.2... testing gnome-doc-prepare... found 0.20.10 checking for gnome-common >= 2.3.0... testing gnome-doc-common... found 3.10.0 Checking for required M4 macros... Checking for forbidden M4 macros... **Warning**: I am going to run `configure' with no arguments. If you wish to pass any to it, please specify them on the `./autogen.sh' command line. Processing ./configure.ac Running glib-gettextize... Ignore non-fatal messages. Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running gnome-doc-common... Running gnome-doc-prepare... You should update your 'aclocal.m4' by running aclocal. Running intltoolize... Running autoreconf... autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force --warnings=no-portability autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. autoreconf: running: /usr/bin/autoconf --force --warnings=no-portability autoreconf: running: /usr/bin/autoheader --force --warnings=no-portability autoreconf: running: automake --add-missing --copy --force-missing --warnings=no-portability src/Makefile.am:205: error: HAVE_INTROSPECTION does not appear in AM_CONDITIONAL src/Makefile.am:8: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/Makefile.am:33: warning: source file 'core/async-getprop.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. src/Makefile.am:33: warning: source file 'core/bell.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/boxes.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/cogl-utils.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/compositor.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-background-actor.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-module.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-plugin.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-plugin-manager.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-shadow-factory.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-shaped-texture.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-texture-rectangle.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-texture-tower.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-window-actor.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-window-group.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/meta-window-shape.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'compositor/region-utils.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/above-tab-keycode.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/constraints.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/core.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/delete.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/display.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/draw-workspace.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/edge-resistance.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/errors.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/eventqueue.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/frame.c' is in a subdirectory, src/Makefile.am:33: warning: source file 'ui/theme.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/ui.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/preview-widget.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:202: warning: source file 'core/muffin.c' is in a subdirectory, src/Makefile.am:202: but option 'subdir-objects' is disabled src/Makefile.am:197: warning: source file 'ui/theme-viewer.c' is in a subdirectory, src/Makefile.am:197: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/testasyncgetprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/async-getprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/testboxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/boxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/util.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:245: warning: source file 'ui/testgradient.c' is in a subdirectory, src/Makefile.am:245: but option 'subdir-objects' is disabled src/compositor/plugins/Makefile.am:4: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/tools/Makefile.am:6: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/wm-tester/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') autoreconf: automake failed with exit status: 1:33: warning: source file 'ui/theme.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/ui.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/preview-widget.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:202: warning: source file 'core/muffin.c' is in a subdirectory, src/Makefile.am:202: but option 'subdir-objects' is disabled src/Makefile.am:197: warning: source file 'ui/theme-viewer.c' is in a subdirectory, src/Makefile.am:197: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/testasyncgetprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/async-getprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/testboxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/boxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/util.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:245: warning: source file 'ui/testgradient.c' is in a subdirectory, src/Makefile.am:245: but option 'subdir-objects' is disabled src/compositor/plugins/Makefile.am:4: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/tools/Makefile.am:6: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/wm-tester/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') autoreconf: automake failed with exit status: 1:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/gradient.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/group-props.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/group.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/iconcache.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/keybindings.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/main.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/place.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/theme.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/ui.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/preview-widget.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:202: warning: source file 'core/muffin.c' is in a subdirectory, src/Makefile.am:202: but option 'subdir-objects' is disabled src/Makefile.am:197: warning: source file 'ui/theme-viewer.c' is in a subdirectory, src/Makefile.am:197: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/testasyncgetprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/async-getprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/testboxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/boxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/util.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:245: warning: source file 'ui/testgradient.c' is in a subdirectory, src/Makefile.am:245: but option 'subdir-objects' is disabled src/compositor/plugins/Makefile.am:4: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/tools/Makefile.am:6: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/wm-tester/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') autoreconf: automake failed with exit status: 1:33: warning: source file 'core/prefs.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/screen.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/session.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/stack.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/stack-tracker.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/util.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/window-props.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/window.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/workspace.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'core/xprops.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/frames.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/tile-hud.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/menu.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/metaaccellabel.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/resizepopup.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/tabpopup.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/tile-preview.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/theme-parser.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/theme.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/ui.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:33: warning: source file 'ui/preview-widget.c' is in a subdirectory, src/Makefile.am:33: but option 'subdir-objects' is disabled src/Makefile.am:202: warning: source file 'core/muffin.c' is in a subdirectory, src/Makefile.am:202: but option 'subdir-objects' is disabled src/Makefile.am:197: warning: source file 'ui/theme-viewer.c' is in a subdirectory, src/Makefile.am:197: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/testasyncgetprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:246: warning: source file 'core/async-getprop.c' is in a subdirectory, src/Makefile.am:246: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/testboxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/boxes.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:244: warning: source file 'core/util.c' is in a subdirectory, src/Makefile.am:244: but option 'subdir-objects' is disabled src/Makefile.am:245: warning: source file 'ui/testgradient.c' is in a subdirectory, src/Makefile.am:245: but option 'subdir-objects' is disabled src/compositor/plugins/Makefile.am:4: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/tools/Makefile.am:6: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') src/wm-tester/Makefile.am:2: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS') autoreconf: automake failed with exit status: 1 or: http://pastebin.com/dJx2hkEz

In my configure.ac script, I have a basic check for X11: PKG_CHECK_MODULES(X11, x11 > 1.6.4, [AC_DEFINE(HAVE_X11)], []) If this fails, I still want to continue. I thought since I added a blank field in the failure condition, it would continue. However, I still get errors: configure: error: Package requirements (x11 > 1.6.4) were not met: No package "x11" found How can I write this line so that it continue if the package is not found?