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:
Code:
#include<stdio.h>
main()
{
printf("hi\n");
}
Makefile.ac
--------------
Code:
Code:
bin_PROGRAMS = hello
hello_SOURCES = hello.c
following steps i followed to create configure and Makefile.in
Code:
autoscan
mv configure.scan configure.ac
autoheader
adding AM_INIT_AUTOMAKE in configure.ac
aclocal
automake --add-missing --copy
autoconf =================> gives err as no Makefile.in generated.
hello!
i want to create a Makefile on the freebsd 4.5,so i vi the hello.c
#include
int main(int argc, char** argv)
{
printf(''Hello, GNU!\n'');
return 0;
}
#autoscan
#cp configure.scan configure.in
#vi configure.in
modify:AC_OUTPUT AC_OUTPUT(Makefile)
#aclocal
#autoconf... (0 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)
Hi ,
While trying to compile a PRO*C code on unix using makefile i get the following errors. i am now working on a 10g migration (from 8i) ...
these makefile perfectly work in previous version.
ld: fatal: file... (7 Replies)
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 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)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
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:
make all-am
make: Entering directory... (0 Replies)
1. The problem statement, all variables and given/known data:
Create a makefile for a set of source files. Several sources files are given but we are not allowed to modify them. The goal is to create a makefile such that if a change is made to any of the source code files, the project can be... (5 Replies)
Hello,
My makefiles are set up to generate an environment specific build directory based on the local configuration and some values passed to make. It generally looks like,
# compilers, may be passed to make
CC++ = g++
FCOMP = gfortran
# version of program, may be passed to make
ver =... (4 Replies)
Discussion started by: LMHmedchem
4 Replies
LEARN ABOUT LINUX
automake-1.11
AUTOMAKE(1) User Commands AUTOMAKE(1)NAME
automake - manual page for automake 1.11.1
SYNOPSIS
automake [OPTION] ... [Makefile]...
DESCRIPTION
Generate Makefile.in for configure from Makefile.am.
Operation modes:
--help print this help, then exit
--version
print version number, then exit
-v, --verbose
verbosely list files processed
--no-force
only update Makefile.in's that are out of date
-W, --warnings=CATEGORY
report the warnings falling in CATEGORY
Dependency tracking:
-i, --ignore-deps
disable dependency tracking code
--include-deps
enable dependency tracking code
Flavors:
--cygnus
assume program is part of Cygnus-style tree
--foreign
set strictness to foreign
--gnits
set strictness to gnits
--gnu set strictness to gnu
Library files:
-a, --add-missing
add missing standard files to package
--libdir=DIR
directory storing library files
-c, --copy
with -a, copy missing files (default is symlink)
-f, --force-missing
force update of standard files
Warning categories include:
`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 (default in gnu and gnits modes)
`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
Files which are automatically distributed, if found:
ABOUT-GNU
README config.rpath ltcf-gcj.sh
ABOUT-NLS
THANKS config.sub ltconfig
AUTHORS
TODO configure ltmain.sh
BACKLOG
acconfig.h configure.ac mdate-sh
COPYING
aclocal.m4 configure.in missing
COPYING.DOC
ansi2knr.1 depcomp mkinstalldirs
COPYING.LESSER
ansi2knr.c elisp-comp py-compile
COPYING.LIB
compile install-sh stamp-vti
ChangeLog
config.guess libversion.in texinfo.tex
INSTALL
config.h.bot ltcf-c.sh ylwrap
NEWS config.h.top ltcf-cxx.sh
AUTHOR
Written by Tom Tromey <tromey@redhat.com>
and Alexandre Duret-Lutz <adl@gnu.org>.
REPORTING BUGS
Report bugs to <bug-automake@gnu.org>.
COPYRIGHT
Copyright (C) 2009 Free Software Foundation, Inc. License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
SEE ALSO
The full documentation for automake is maintained as a Texinfo manual. If the info and automake programs are properly installed at your
site, the command
info automake
should give you access to the complete manual.
automake 1.11.1 December 2009 AUTOMAKE(1)