Sponsored Content
Top Forums Programming Issue with make, no rule to make target etc. Post 302534722 by DGPickett on Tuesday 28th of June 2011 02:59:49 PM
Old 06-28-2011
Maybe there is a reason most make setups have a make file in each dir? Often, .c and .cpp in different dirs? You have a lot of ways to make *.o there!

Try adding a specific make group for the first file.

Make can be very chatty if asked.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

make and clean in a single rule in the makefile.

Hi, This stems from the following thread https://www.unix.com/showthread.php?t=18299 I have a makefile which makes either executables or a shared library. i.e. make -f unix.mak will create the executables and make -f unix.mak libolsv will create the shared library. Since these have to be... (4 Replies)
Discussion started by: vino
4 Replies

2. UNIX for Dummies Questions & Answers

Solaris 9: make: Fatal error:Command failed for target

Hi everyone first of all you should know that I've been working with solaris for a few days only. :) I need to install some programs and I have had the following troubles: 1. When I used /.configure it showed the following message: "no acceptable C compiler found in $PATH" I included... (2 Replies)
Discussion started by: eldiego
2 Replies

3. Linux

make file_Configuration lookup disabled for target.

hello everyone, while i am compiling a c++ module.at the compilation end i am getting the following error. ======================= Configuration lookup disabled for target"/swtemp/usbs/cc/unix-ce/root/subsys/cb/cdbc/obj_0001/HP-UX//rdr_types.h" what does it mean.can somebody clarify the... (0 Replies)
Discussion started by: mannam srinivas
0 Replies

4. UNIX for Dummies Questions & Answers

make command failed for target 'obj/gp_unix.o'

hi, i am trying to run make command in solaris 9. its giving the error: make:Fatal error:Command failed for target 'obj/gp_unix.o' i came to know X11 should be inastalled for gp_unix.o.But it is already installed.still the same error. ./configure worked fine. can anybody please suggest... (3 Replies)
Discussion started by: rosalina
3 Replies

5. Shell Programming and Scripting

To make sure I don't violate rule #7

I am hoping to find out if it is possible to use some sort of UNIX programming/scripting tools to solve a problem I have with reformatting email messages that are sent out of my IBM UNIX (AIX) system. I'm thinking some advanced awk/sed may work I do not have the time or the ability to do this... (6 Replies)
Discussion started by: toddk
6 Replies

6. Shell Programming and Scripting

make Fatal error: Command failed for target 'exp_inter.o'

I am trying to install Expect 5.43 on my Solaris 10 x86 PC. When I run the make file I get - Command failed for target 'exp_inter.o'. I tried to find the file (find / -name exp_inter.o -print 2>/dev/null) but could not. Where can I get this file from? (2 Replies)
Discussion started by: pazzy
2 Replies

7. Programming

compile fails in linux ... "No rule to make target" ... HELP

hello all, attached you can find a tool (written in C) that i really need to make it compile under linux i am able to compile and run it successfully in mac os x, but in linux the compilation fails the only thing that i did so far is to change the following #include <sys/malloc.h> to... (13 Replies)
Discussion started by: OneDreamCloser
13 Replies

8. UNIX for Dummies Questions & Answers

Make - two target produced by one recipe

Suppose executable X produces files A and B from nothing, Y produces C from A, Z produces D from B, and my final goal is to produce C and D. I wrote the following makefile: .PHONY: all all: C D C: A Y A D: B Z B A B: X This makefile seems to reflect all dependencies, as it should... (2 Replies)
Discussion started by: ybelenky
2 Replies

9. UNIX for Dummies Questions & Answers

make - two wildcards in the target

Suppose I have a Makefile like this: x/Ax: x/Bx touch x/Ax y/Ay: y/By touch y/Ay z/Az: z/Bz touch z/Az It does not look like a proper style for make. I would like to write something like %/A%: %/B% touch %/A% but make does not accept it. What is a right way to shorten such a... (1 Reply)
Discussion started by: ybelenky
1 Replies

10. Programming

Makefile No rule to make target

I am trying to create a makefile to build a program and am getting the following error: make -f tsimplex.mk make: *** No rule to make target `/main/tsimplex_main.cpp', needed by `tsimplex_main.o'. Stop. OPSYS = $(shell uname -s ) TARGET = tsimplex ROOTDIR = ../../.. GTSDIR =... (1 Reply)
Discussion started by: kristinu
1 Replies
IMAKE(1)						      General Commands Manual							  IMAKE(1)

NAME
imake - C preprocessor interface to the make utility SYNOPSIS
imake [ -Ddefine ] [ -Idir ] [ -Udefine ] [ -Ttemplate ] [ -f filename ] [ -C filename ] [ -s filename ] [ -e ] [ -v ] DESCRIPTION
Imake is used to generate Makefiles from a template, a set of cpp macro functions, and a per-directory input file called an Imakefile. This allows machine dependencies (such as compiler options, alternate command names, and special make rules) to be kept separate from the descriptions of the various items to be built. OPTIONS
The following command line options may be passed to imake: -Ddefine This option is passed directly to cpp. It is typically used to set directory-specific variables. For example, the X Window System uses this flag to set TOPDIR to the name of the directory containing the top of the core distribution and CURDIR to the name of the current directory, relative to the top. -Idirectory This option is passed directly to cpp. It is typically used to indicate the directory in which the imake template and configura- tion files may be found. -Udefine This option is passed directly to cpp. It is typically used to unset variables when debugging imake configuration files. -Ttemplate This option specifies the name of the master template file (which is usually located in the directory specified with -I) used by cpp. The default is Imake.tmpl. -f filename This option specifies the name of the per-directory input file. The default is Imakefile. -C filename This option specifies the name of the .c file that is constructed in the current directory. The default is Imakefile.c. -s filename This option specifies the name of the make description file to be generated but make should not be invoked. If the filename is a dash (-), the output is written to stdout. The default is to generate, but not execute, a Makefile. -e This option indicates the imake should execute the generated Makefile. The default is to leave this to the user. -v This option indicates that imake should print the cpp command line that it is using to generate the Makefile. HOW IT WORKS
Imake invokes cpp with any -I or -D flags passed on the command line and passes the name of a file containing the following 3 lines: #define IMAKE_TEMPLATE "Imake.tmpl" #define INCLUDE_IMAKEFILE <Imakefile> #include IMAKE_TEMPLATE where Imake.tmpl and Imakefile may be overridden by the -T and -f command options, respectively. The IMAKE_TEMPLATE typically reads in a file containing machine-dependent parameters (specified as cpp symbols), a site-specific parameters file, a file defining variables, a file containing cpp macro functions for generating make rules, and finally the Imakefile (specified by INCLUDE_IMAKEFILE) in the current directory. The Imakefile uses the macro functions to indicate what targets should be built; imake takes care of generating the appropriate rules. Imake configuration files contain two types of variables, imake variables and make variables. The imake variables are interpreted by cpp when imake is run. By convention they are mixed case. The make variables are written into the Makefile for later interpretation by make. By convention make variables are upper case. The rules file (usually named Imake.rules in the configuration directory) contains a variety of cpp macro functions that are configured according to the current platform. Imake replaces any occurrences of the string ``@@'' with a newline to allow macros that generate more than one line of make rules. For example, the macro #define program_target(program, objlist) @@ program: objlist @@ $(CC) -o $@ objlist $(LDFLAGS) when called with program_target(foo, foo1.o foo2.o) will expand to foo: foo1.o foo2.o $(CC) -o $@ foo1.o foo2.o $(LDFLAGS) Imake also replaces any occurrences of the word ``XCOMM'' with the character ``#'' to permit placing comments in the Makefile without caus- ing ``invalid directive'' errors from the preprocessor. Some complex imake macros require generated make variables local to each invocation of the macro, often because their value depends on parameters passed to the macro. Such variables can be created by using an imake variable of the form XVARdefn, where n is a single digit. A unique make variable will be substituted. Later occurrences of the variable XVARusen will be replaced by the variable created by the corresponding XVARdefn. On systems whose cpp reduces multiple tabs and spaces to a single space, imake attempts to put back any necessary tabs (make is very picky about the difference between tabs and spaces). For this reason, colons (:) in command lines must be preceded by a backslash (). USE WITH THE X WINDOW SYSTEM
The X Window System uses imake extensively, for both full builds within the source tree and external software. As mentioned above, two special variables, TOPDIR and CURDIR, are set to make referencing files using relative path names easier. For example, the following com- mand is generated automatically to build the Makefile in the directory lib/X/ (relative to the top of the sources): % ../.././config/imake -I../.././config -DTOPDIR=../../. -DCURDIR=./lib/X When building X programs outside the source tree, a special symbol UseInstalled is defined and TOPDIR and CURDIR are omitted. If the con- figuration files have been properly installed, the script xmkmf(1) may be used. INPUT FILES
Here is a summary of the files read by imake as used by X. The indentation shows what files include what other files. Imake.tmpl generic variables site.def site-specific, BeforeVendorCF defined *.cf machine-specific *Lib.rules shared library rules site.def site-specific, AfterVendorCF defined Imake.rules rules Project.tmpl X-specific variables *Lib.tmpl shared library variables Imakefile Library.tmpl library rules Server.tmpl server rules Threads.tmpl multi-threaded rules Note that site.def gets included twice, once before the *.cf file and once after. Although most site customizations should be specified after the *.cf file, some, such as the choice of compiler, need to be specified before, because other variable settings may depend on them. The first time site.def is included, the variable BeforeVendorCF is defined, and the second time, the variable AfterVendorCF is defined. All code in site.def should be inside an #ifdef for one of these symbols. FILES
Imakefile.c temporary input file for cpp /tmp/Imf.XXXXXX temporary Makefile for -s /tmp/IIf.XXXXXX temporary Imakefile if specified Imakefile uses # comments /usr/bin/cpp default C preprocessor SEE ALSO
make(1), xmkmf(1) S. I. Feldman, Make -- A Program for Maintaining Computer Programs ENVIRONMENT VARIABLES
The following environment variables may be set, however their use is not recommended as they introduce dependencies that are not readily apparent when imake is run: IMAKEINCLUDE If defined, this specifies a ``-I'' include argument to pass to the C preprocessor. E.g., ``-I/usr/X11/config''. IMAKECPP If defined, this should be a valid path to a preprocessor program. E.g., ``/usr/local/cpp''. By default, imake will use cc -E or /usr/bin/cpp, depending on the OS specific configuration. IMAKEMAKE If defined, this should be a valid path to a make program, such as ``/usr/local/make''. By default, imake will use whatever make pro- gram is found using execvp(3). This variable is only used if the ``-e'' option is specified. AUTHOR
Todd Brunhoff, Tektronix and MIT Project Athena; Jim Fulton, MIT X Consortium X Version 11 imake 1.0.2 IMAKE(1)
All times are GMT -4. The time now is 11:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy