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)
AUTORECONF(1) User Commands AUTORECONF(1)NAME
autoreconf - Update generated configuration files
SYNOPSIS
autoreconf [OPTION] ... [CONFIGURE-AC or DIRECTORY] ...
DESCRIPTION
Run `autoconf' (and `autoheader', `aclocal', `automake', `autopoint' (formerly `gettextize'), and `libtoolize' where appropriate) repeat-
edly to remake the GNU Build System files in the DIRECTORIES or the directory trees driven by CONFIGURE-AC (defaulting to `.').
By default, it only remakes those files that are older than their predecessors. If you install new versions of the GNU Build System, run-
ning `autoreconf' remakes all of the files by giving it the `--force' option.
Operation modes:
-h, --help
print this help, then exit
-V, --version
print version number, then exit
-v, --verbose
verbosely report processing
-d, --debug
don't remove temporary files
-f, --force
consider all files obsolete
-i, --install
copy missing auxiliary files
-s, --symlink
with -i, install symbolic links instead of copies
-m, --make
when applicable, re-run ./configure && make
-W, --warnings=CATEGORY
report the warnings falling in CATEGORY [syntax]
Warning categories include:
`cross'
cross compilation issues
`gnu' GNU coding standards (default in gnu and gnits modes)
`obsolete'
obsolete features or constructions
`override'
user redefinitions of Automake rules or variables
`portability'
portability issues
`syntax'
dubious syntactic constructs (default)
`unsupported'
unsupported or incomplete features (default)
`all' all the warnings
`no-CATEGORY'
turn off warnings in CATEGORY
`none' turn off all the warnings
`error'
treat warnings as errors
The environment variable `WARNINGS' is honored. Some subtools might support other warning types, using `all' is encouraged.
Library directories:
-B, --prepend-include=DIR
prepend directory DIR to search path
-I, --include=DIR
append directory DIR to search path
The environment variables AUTOCONF, AUTOHEADER, AUTOMAKE, ACLOCAL, AUTOPOINT, LIBTOOLIZE are honored.
AUTHOR
Written by David J. MacKenzie and Akim Demaille.
REPORTING BUGS
Report bugs to <bug-autoconf@gnu.org>.
COPYRIGHT
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO autoconf(1), automake(1), autoreconf(1), autoupdate(1), autoheader(1), autoscan(1), config.guess(1), config.sub(1), ifnames(1), libtool(1).
The Debian project regards the full documentation for autoreconf to be non-free, so it is not included in Debian. Nevertheless, the non-
free distribution that accompanies Debian includes the manual in its autoconf-doc package. Otherwise, you may be able to access the Auto-
conf manual online.
autoreconf 2.59 September 2005 AUTORECONF(1)
