Sponsored Content
Top Forums Shell Programming and Scripting automake does not create Makefile.in Post 302507022 by useless79 on Tuesday 22nd of March 2011 02:57:53 PM
Old 03-22-2011
automake does not create Makefile.in

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:

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.


Could any one let me know what went wrong ?

Thanks in advance,
Ravi

Last edited by pludi; 03-22-2011 at 04:53 PM..
 

10 More Discussions You Might Find Interesting

1. Programming

about create Makefile

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)
Discussion started by: mzp
0 Replies

2. UNIX for Advanced & Expert Users

automake

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)
Discussion started by: munnu
1 Replies

3. Programming

Makefile compilation Error -Unable to create executable

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)
Discussion started by: sivalives
7 Replies

4. Shell Programming and Scripting

Makefile cant create new install path

..... (2 Replies)
Discussion started by: mercury
2 Replies

5. UNIX for Advanced & Expert Users

Makefile problem - How to run module load in a Makefile

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)
Discussion started by: hernandinho
2 Replies

6. UNIX for Advanced & Expert Users

KDE Needs Automake >= 1.6.1 -- I have 1.11

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)
Discussion started by: lucelio
11 Replies

7. Homework & Coursework Questions

Help with Simple Multi-Level Makefile (Extremely New at Makefile)

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)
Discussion started by: Tatl
1 Replies

8. Shell Programming and Scripting

using automake and autoconf with C++

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)
Discussion started by: bacpp
0 Replies

9. Homework & Coursework Questions

Create Makefile from source files

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)
Discussion started by: pintu1228
5 Replies

10. Programming

Makefile instructions to create directories (CentOS7 , GNU Make 3.82)

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
AUTOMAKE(1)						      General Commands Manual						       AUTOMAKE(1)

NAME
automake - automatically create Makefile.in's from Makefile.am's SYNOPSIS
automake [ -a | --add-missing ] [ --amdir=DIR ] [ --build-dir=DIR ] [ -c | --copy ] [ --cygnus ] [ -f | --force-missing ] [ --foreign ] [ --gnits ] [ --gnu ] [ --help ] [ -i | --ignore-deps ] [ --include-deps ] [ --no-force ] [ -o DIR ] [ --output-dir=DIR ] [ --srcdir-name=DIR ] [ -v | --verbose ] [ --version ] [ --Werror | --Wno-error ] DESCRIPTION
To create all the Makefile.ins for a package, run the automake program in the top level directory, with no arguments. automake will auto- matically find each appropriate Makefile.am (by scanning configure.in) and generate the corresponding Makefile.in. Note that automake has a rather simplistic view of what constitutes a package; it assumes that a package has only one configure.in, at the top. If your package has multiple configure.ins, then you must run automake in each directory holding a configure.in. You can optionally give automake an argument; .am is appended to the argument and the result is used as the name of the input file. This feature is generally only used to automatically rebuild an out-of-date Makefile.in. Note that automake must always be run from the topmost directory of a project, even if being used to regenerate the Makefile.in in some subdirectory. This is necessary because automake must scan configure.in, and because automake uses the knowledge that a Makefile.in is in a subdirectory to change its behavior in some cases. automake accepts the following options: -a --add-missing Automake requires certain common files to exist in certain situations; for instance config.guess is required if configure.in runs AC_CANONICAL_HOST. Automake is distributed with several of these files; this option will cause the missing ones to be automatically added to the package, whenever possible. In general if Automake tells you a file is missing, try using this option. By default Automake tries to make a symbolic link pointing to its own copy of the missing file; this can be changed with --copy. --libdir=DIR Look for Automake data files in directory DIR instead of in the installation directory. This is typically used for debugging. -c --copy When used with --add-missing, causes installed files to be copied. The default is to make a symbolic link. --cygnus Causes the generated Makefile.ins to follow Cygnus rules, instead of GNU or Gnits rules. -f --force-missing When used with --add-missing, causes standard files to be rebuilt even if they already exist in the source tree. This involves removing the file from the source tree before creating the new symlink (or, with --copy, copying the new file). --foreign Set the global strictness to foreign. --gnits Set the global strictness to gnits. --gnu Set the global strictness to gnu. This is the default strictness. --help Print a summary of the command line options and exit. -i --ignore-deps This disables the dependency tracking feature. --include-deps This enables the dependency tracking feature. This feature is enabled by default. This option is provided for historical reasons only and probably should not be used. --no-force Ordinarily automake creates all Makefile.ins mentioned in configure.in. This option causes it to only update those Makefile.ins which are out of date with respect to one of their dependents. -o DIR --output-dir=DIR Put the generated Makefile.in in the directory DIR. Ordinarily each Makefile.in is created in the directory of the corresponding Makefile.am. This option is used when making distributions. -v --verbose Cause Automake to print information about which files are being read or created. --version Print the version number of Automake and exit. --Werror --Wno-error --Werror will cause all warnings issued by automake to become errors. Errors affect the exit status of automake, while warnings do not. --Wno-error, the default, causes warning to be treated as warnings only. SEE ALSO
aclocal(1), and the Texinfo documentation for automake AUTHORS
Automake was written primarily by David Mackenzie and Tom Tromey. This manpage written by Ben Pfaff <pfaffben@pilot.msu.edu> for the Debian GNU/Linux automake package. 28 Jan 2002 AUTOMAKE(1)
All times are GMT -4. The time now is 11:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy