Problem With Makefile

10 More Discussions You Might Find Interesting

1. Programming

Problem running a makefile

I have written this makefile and am getting an error saying make nfd gfortran -O -Wall -fbacktrace -fno-align-commons -c -o fd.o fd.f fd.f:49: Error: Can't open included file 'fd.par' make: *** Error 1 The directory structure is as follows . ├── library │ ├── fd │ │ ├──...

2. Programming

Problem creating a makefile

hello, I'm trying to create a makefile to run multiple c files. I am able to run one c file only with the code I have when I tried to run 2 or more c files I'm not able. here is my code # $Source: /home/hectormasencio/make/Makefile,v $ # $Date: 2012/11/27 11:35:30 $ CC= gcc OBJS= temp.o...

3. Programming

Noob makefile problem

Im trying to build a makefile for the first time in many years and Im coming to a screaching halt on something that should be child's play; just compiling two files. Here is an excerpt of the make file. (using GMAKE on a TI compiler) CCHP = <<compiler>> PROJ_DIR = . APP_DIR ...

4. Programming

Problem with Makefile

Hi, Here is my makefile http://pastie.org/1104332. I am trying to compile different .c files and .s files (assembly files) from different sub directories into E:/em35x/build/mfg-sample-app-cortexm3-iar-em357-em3xx-dev0680/ then the linker should link all the .o files from the build directory...

5. Programming

please help me with this big makefile problem

I need to create an executable with these two makefiles(they both have libaries i need(qt and ruby)) i have extconf.rb gui.ui gui_include.h main.cpp ScaleIM_client.rb ui_gui.h i want to combine them all into one executable please!...

6. 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

7. Programming

Simple Makefile Problem (with a dependency)

Hi all, I have 4 '.cpp' files and 1 header files: Tools.cpp Code1.cpp Code2.cpp Code3.cpp and Tools.hh Now all Code1.cpp, Code2.cpp, Code3.cpp use functions stored in Tools.cpp. Currently, what I do to compile all of them is using this simple shell script:

8. Programming

Problem with makefile

My make file is CFLAGS = -Wall -g LDFLAGS = -lm CC = g++ all: server client rc4.o: rc4.cpp rc4.h ${CC} ${CFLAGS} -c rc4.cpp server.o: server.cpp rc4.h ${CC} ${CFLAGS} -c .cpp client.o: client.cpp rc4.h ${CC} ${CFLAGS} -c client.cpp server: server.o...

9. Programming

Problem with a Makefile

Hi, I am very new with makefile topics , maybe this is a very symple question... I have this code wich compile very good ( I get it from the net), I will call it code A. I have to add it with a program that is all ready in use, (code B) that also compile good. When I put together it doesnt...

10. UNIX for Advanced & Expert Users

problem with Makefile

Hi, I have a makefile which looks like this ProcessA : commands touch pro1 ProcessB : pro1 commands touch pro2 ProcessC: pro3 commands and after some runs, i wish only pro3 to run and I check that "pro1" and "pro2" are there in the directory, but still, if i give make...

LEARN ABOUT DEBIAN

automake-1.9

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)

Emergency UNIX and Linux Support