12-19-2007
i try to run the make clean, and it works just fine
i change everything and reduce it to this
Quote:
PROG = testprog
TRGTS = testMake1 testMake2
all:
$(MAKE) -f testMake1 $@
$(MAKE) -f testMake2 $@
and it works
9 More Discussions You Might Find Interesting
1. HP-UX
Hi:
I am new to HP-UX. After the system starts up, it is written in the documents that press any key within 10 sec to interrupt, and go to the main prompt, where I can select the boot device or boot from CD to recover system. However if I interrupt boot, it goes straight to HPUX> prompt. Please... (2 Replies)
Discussion started by: amitra123
2 Replies
2. Programming
Friends I am Trying this code to call main Recursively But It is showing segmentation errot
#include<stdio.h>
int main()
{
int i;
for(i=0;i<10;i++)
{
if(i==5)
{
exit(0);
}
else
{
main();
}
}
} (7 Replies)
Discussion started by: krishna_sicsr
7 Replies
3. Programming
Is it possible to execute any function before main() function in C or C++. (6 Replies)
Discussion started by: arun.viswanath
6 Replies
4. UNIX for Advanced & Expert Users
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
5. UNIX and Linux Applications
We compile the sendmail.cf file using main.mc. I have managed to place all of our configuration options in main.mc without a problem, with the exception of one.
I want to have the HelpFile commented out by default in sendmail.cf. How can I instruct main.mc to place an entry for HelpFile in... (1 Reply)
Discussion started by: dangral
1 Replies
6. UNIX for Advanced & Expert Users
I have 2 libraries in 2 different directories that I build with Makefiles.
library B depends on library A. If I modify a .cpp file in library A and run lib B's Makefile can I have B's makefile to automatically rebuild library A?
I am now rebuilding A, followed by B... but I'd like B to... (0 Replies)
Discussion started by: wwuster
0 Replies
7. Shell Programming and Scripting
It seems $? can only contain one byte. see below:
int main()
{
return 0x12345678;
}
After I run the code and check the $? value it output 120, obviously it is the decimal of the last byte of 0x12345678. And if I return a value less than 255, the $? value seems right.
Why? and... (3 Replies)
Discussion started by: vistastar
3 Replies
8. Homework & Coursework Questions
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
9. Programming
I am trying to obtain documentation using ri on my local machine. If I dont require any method in my script and I want to find information on .value or .inspect or anything that is native without calling in a method how can I look that up with ri, or even rdoc? (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
LEARN ABOUT HPUX
dpatch.make
DPATCH.MAKE(7) dpatch DPATCH.MAKE(7)
NAME
dpatch.make - simplistic wrapper around dpatch(1) for make(1).
SYNOPSIS
include /usr/share/dpatch/dpatch.make
DESCRIPTION
For backwards compatibility and ease of use, dpatch.make is provided along with dpatch(1). Its purpose is to implement generic patch and
unpatch rules that can be reused in debian/rules scripts.
WARNING
dpatch is deprecated, please switch to the `3.0 (quilt)' Debian source package format instead. See http://wiki.debian.org/Projects/Deb-
Src3.0#FAQ for a short guide on how to do it.
USAGE
Using dpatch.make is rather straightforward: one has to include the file in debian/rules, change the appropriate targets to depend on patch
and unpatch, and that is all it takes.
Figuring out what the appropriate target is, requires some thought. Generally, one has a build target, or config.status, or configure (or
any of these with a -stamp suffix). Most of the time these are called first during the build, so one of these (the one that exists, and is
not depended upon by another one) has to be modified to depend on the patch target in dpatch.make.
Doing the same for the clean target is easier. One only has to rename the old rule to, say, clean-patched, then make a new one that has
clean-patched and unpatch in its list of prerequisites.
CUSTOMISATION
There are a few variables which are used by dpatch.make, which can be set before including it, in order to change the systems behaviour a
little.
These variables are:
DEB_SOURCE_PACKAGE
This is the name of the source package, used when creating the stamp file. By default, it is empty.
DPATCH_STAMPDIR
This is the directory where stamp files will be put. Default is debian/patched.
DPATCH_STAMPFN
The name of the stamp file, which contains the patch descriptions and other possible meta-data. Default value is patch-stamp.
DPATCH_PREDEPS
A list of make targets to call before applying the dpatch.
DPATCH_WORKDIR
The target directory to apply patches to. By default, it is the current directory.
PATCHLIST
The list of patches to apply. This is an alternative to debian/patches/00list - that is, if this variable is not empty, the
contents of 00list will be ignored, and this variable will be used instead.
EXAMPLE
include /usr/share/dpatch/dpatch.make
build: build-stamp
build-stamp: patch-stamp
${MAKE}
touch build-stamp
clean: clean1 unpatch
clean1:
${MAKE} clean
rm -rf debian/files debian/substvars debian/imaginary-package
.PHONY: patch unpatch ...
.
.
.
SIDE EFFECTS
Using dpatch.make instead of calling dpatch directly has one side effect: it will create a file called patch-stamp containing some
meta-information extracted from the scriptlets.
Depending on a phony patch target directly from build target may cause build target to be reevaluated even when there is no change to be
done. Instead, try making build-stamp depend on patch-stamp as specified in this example.
AUTHOR
Originally by Gergely Nagy. Modified by Junichi Uekawa.
SEE ALSO
dpatch(1), dpatch(7), dpatch-edit-patch(1), dpatch-list-patch(1), dpatch-convert-diffgz(1)
DPATCH 2 Dec 13 2011 DPATCH.MAKE(7)