hi,
I have written the Makefile.am and autoconf.ac files and am looking to build my project by providing the following commands:
$autoreconf -f -i -m
$./configure
both of the above work fine, but when I give the make command, I get the following error:
Code:
make all-am
make[1]: Entering directory `/home/BA/test'
depbase='echo test.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'';\
g++ -DHAVE_CONFIG_H -I. -g -O2 -MT test.o -MD -MP -MF $depbase.Tpo -c -o test.o test.cpp &&\
mv -f $depbase.Tpo $depbase.Po
g++ -g -O2 -o test.exe test.o
make[1]: *** No rule to make target 'autogen.sh', needed by 'all-am'. Stop.
make[1]: Leaving directory `/home/BA/test'
make: *** [all] Error 2
Can anyone please help me with fixing this error. thanks!
Heyas
I'm trying to rewrite the install procedure of TUI, applying the standards of the Autotools.
Inofficial:
unix - Why always ./configure; make; make install; as 3 seperate steps? - Stack Overflow
autoconf automake tutorial
Official:
... (4 Replies)
Hi,
I'm trying to make my source "buildable". autoconf and automake tools are used. configure and Makefile.in files are created successfully.
configure.ac:
AC_INIT()
AC_CONFIG_SRCDIR()
AC_PROG_CXX
AM_INIT_AUTOMAKE(main, 0.1)
AC_CHECK_HEADERS()... (0 Replies)
hi all,
I have written a simple C program hello.c and a Makefile.ac but when i try to run automake it does not create Makefile.in hence I am not able to run ./configure command in my directory. Following are the containts of my prog.
hello.c
--------
Code:
#include<stdio.h>
main()
{... (0 Replies)
Hi,
I'm on Fedora-11-x86_64 with KDevelop 3.5.4. I have automake 1.11 installed, but when I attempt to run automake and friends on a new project I get:
*** YOU'RE USING automake (GNU automake) 1.11
*** KDE requires automake 1.6.1 or newer
I reported(KDevelop) the error Bug: 210084 ... (11 Replies)
Hi gurus,
I'm a FreeBSD noob who has generated an error, searched everywhere for solutions, and has just joined this forum (and searched it) hoping you can help.
I really need to get mysql server installed again ASAP, and preferably with Sphinx as a storage engine, or my web app in dev is... (2 Replies)
I am using the GNU automake.
I have created the Configure.in and Makefile.am files but don't know how to link in my dependencies.
I have basically added another project (OpenCV) to my eclipse workspace and want to reference this in the build. I have set Eclipse up to include the Cpp files... (5 Replies)
hi,
i'm fairly new with automake and i ran into a problem that i have found no solution for. so i have a setup where i don't want all the output files generated by the compiler and alike in my src directory, instead i created a build/unix folder and i have build/unix/config set for... (0 Replies)
helo , i m using RHEL 4 and in that automake -2.59
now i install automake-2.61
but when i say # rpm -qa |grep automake
it shows only automake-2.59
actually i want to use automake-2.61
so how to resolve this issue
amit (5 Replies)
hi
on machine automake 1.9 are install but i am not able create make file
so please tell me what proper command to create make file using automake (1 Reply)
AUTOCONF(1) General Commands Manual AUTOCONF(1)NAME
wrapper - Wrapper for distinguishing Autoconf 2.13 and 2.50
SYNOPSIS
autoconf [ options ]
autoheader [ options ]
autoreconf [ options ]
DESCRIPTION
Autoconf is an automatic configure script builder with two major version series: 2.13 and earlier, 2.50 and later. Versions within either
series are largely compatible, but the two series are largely incompatible. When both versions are installed, as they are on your system
(given that you're reading this manpage), Debian selects between the two versions simultaneously. This manpage documents how the automatic
selection works. If you are actually looking for the documentation for either version of Autoconf, then refer to the SEE ALSO section
below.
Automatic version selection works via a wrapper script installed under the names autoconf, autoheader, and autoreconf. Each of these
attempts to detect which Autoconf is needed and run the correct version of the tool.
There are no wrappers for autoupdate, autoscan, or ifnames. These are not used during a package build. Choose the proper version by hand.
The following heuristics are used to choose an Autoconf version:
* If file configure.ac exists, Autoconf 2.50 is used. Autoconf 2.13 used the name configure.in instead, but version 2.50 supports
both.
(Usually autoconf is run without nonoption arguments. If a filename is supplied on the command line, then version 2.50 is used if
the filename ends in .ac.)
* Otherwise, configure.in (or the file specified on the command line, if any) is read. It is checked for the presence of an AC_PREREQ
directive. If it specifies a minimum version higher than 2.13, Autoconf 2.50 is used. aclocal.m4, if present, is also scanned.
* Otherwise, Autoconf 2.13 is used.
To force Autoconf 2.13 to be used, name the Autoconf input file configure.in and omit the use of AC_PREREQ() or specify a minimum version
of 2.13 or earlier. To force Autoconf 2.50 to be used, name the input file configure.ac or use AC_PREREQ(2.50).
I recommend not calling the programs autoconf2.13 or autoconf2.50, etc., directly, instead of through the wrappers. When used with pro-
grams like Automake, these direct calls won't propagate through into the Makefile, so later re-autoconf'ings won't use the correct version.
It's better to use one of the methods explained above to force a particular version.
SEE ALSO autoconf2.13(1), autoheader2.13(1), autoreconf2.13(1), autoconf2.50(1), autoheader2.50(1), autoreconf2.50(1), and the Autoconf manuals
autoconf and autoconf2.13.
AUTHORS
David MacKenzie, with help from Franc,ois Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor, Roland McGrath, Noah Friedman, David D.
Zuhn, and many others. This manpage written by Ben Pfaff <pfaffben@debian.org> for the Debian GNU/Linux autoconf2.13 package.
Autoconf Wrapper AUTOCONF(1)
