04-14-2014
As MAKE is a UNIX command how about......
MAKE == Managers Always Know Everything...
<wink>
This User Gave Thanks to wisecracker For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
How does the Solaris identifies the controller subscript ? ( like c0txdxs0 or c1txdxsx ?? )
I have a unix box ( Ultra 30) running with 2.5.1.
When I connected an external hard disk to the on-board scsi port, it got identified as c0t1dxsx...
(... (1 Reply)
Discussion started by: shibz
1 Replies
2. Programming
Im not very experienced with C so this is probably a basic question. I have a script that opens up 5 sockets, it then runs through a loop and on a given event reconnects to the relevant socket and sends some data. The socket to be reconnected to is kept track of with a 'count' variable. The sockets... (5 Replies)
Discussion started by: geester
5 Replies
3. Shell Programming and Scripting
Hi,
I want to create a file named 'abc(+1)' and append the data of file 'abc' to it. But getting error as unexpected'(' when i tried to use the following command.
cat abc > abc(+1)
Is there any other way to include brackets along with +1 in the file name?
TIA. (3 Replies)
Discussion started by: vimalr
3 Replies
4. Shell Programming and Scripting
hi all,
Please advise at what circumstance those file will become
-rwxr-xr-x 1 psa psa 1969088 Aug 18 2006 #libaa.sl
-rwx------ 1 psa psa 2166784 Jul 25 2006 #libcrypto.sl.0.9.7
-rwx------ 1 psa psa 904040 Jul 25 2006 #libxxx.sl
-rwx------ 1 psa ... (2 Replies)
Discussion started by: rauphelhunter
2 Replies
5. Shell Programming and Scripting
OK, so a quick background:
I am a sys admin for a 1:1 deployment in academia with Macbooks, totaling around 6,000. Macbooks get shifted around from building to building and go to and from the repair center if hardware repair is needed. Often, some machines will get moved from one building to... (8 Replies)
Discussion started by: tlarkin
8 Replies
6. Shell Programming and Scripting
Hi,
I need some help!
I have a file in which i im splitting into 20 different files each called
model_001.in
model_002.in
etc...
i would like to make directory for each file using only the name and not the extension so that the directory names are
model_001
model_002
etc.
... (8 Replies)
Discussion started by: olifu02
8 Replies
7. Shell Programming and Scripting
i have a file staff.txt with contents
tom|25|New York
sims|40|London
neyo|18|Moscow
i want to label the column at the top, my output should be
Names|age|city of birth
tom|25|New York
sims|40|London
neyo|18|Moscow (4 Replies)
Discussion started by: blackzinga80
4 Replies
8. IP Networking
Hi gurus, I am trying to understand the enviroment which we are using. The fact that I am asking is that this is production enviroment and I cannot change anything to experiment. Following servers are somehow related to each other, please help me figure out if my conclusions are correct.
-... (0 Replies)
Discussion started by: wakatana
0 Replies
9. Shell Programming and Scripting
#!/bin/bash
while read inputline
do
what="$inputline"
echo $what;
if ;
then
exit
fi
$reextend $what
$print ls -a
done
this is my code i am trying to change all of the file types of a certain directory to another file type but im not all the way there can someone help please (3 Replies)
Discussion started by: domdom110
3 Replies
10. Shell Programming and Scripting
Hi,
I have a folder that contains files
abc.txt
def.txt
....and so on
Inside abc.txt, I have @<TRIPOS>MOLECULE
4|Chelerythrine|abcb11_earlyIdentification_Stronginhib_washed_ligprep|sdf|1|dock
Inside def.txt, I have @<TRIPOS>MOLECULE... (6 Replies)
Discussion started by: rossi
6 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)