07-29-2011
Macros how-to?
Hi, all
I just came to new system with RH, and it has alot of macros I was told to use, but I can't find how to open it for display or for edit, can you help me please, is it all about make/makefile?
let say I have macro <trx> like this, that does a lot of things:
>$ trx
... creating new service tree
... done
... cleaning log files
... done
.>$
I've checked www on make, but bit confusing to start with, can anybody give small sample how it works.
How to dig it up?
Thanks
M
Last edited by trento17; 07-29-2011 at 02:20 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm going write a small handbook. The typesetting software I'm going to use is troff. There are -ms -me -mm macros for troff. Which one is the most suitable? Thanks!
-Tony (2 Replies)
Discussion started by: tonyt
2 Replies
2. Programming
Hi,
I want to just expand the macros in a set of c files from a filelist which are in different directories. I don't want the header files included in the c file to be expanded. I have a perl script which does
gcc -E <infile> -I <path to search for header files> -imacros <infile>
But in... (1 Reply)
Discussion started by: spsenthil
1 Replies
3. UNIX for Dummies Questions & Answers
The question is , as the topic says, how does one save macros for VIM in the .vimrc.
I had a look on web and it gave all this ****** about how to build turing machines in vim code or something but i just want to store a macro to like :
if(){
}
I know how to do it IN vim but .vimrc??????!?!?!... (3 Replies)
Discussion started by: yngwie
3 Replies
4. Programming
The following is taken from some production code:
#ifdef LOCK_LOCKF
#ifdef HAVE_SYS_FILE_H
#include <sys/lockf.h>
#endif
#ifdef HAVE_SYS_FILE_H
#include <sys/file.h>
#endif
#define LOCK(file) fseek(file, 0L, 0), lockf(file, 1, 0L)
#define UNLOCK(file) fseek(file, 0L, 0),... (2 Replies)
Discussion started by: frequency8
2 Replies
5. Programming
This might be poorly worded.
In the header file, I have
#ifdef LOCK_FCNTL
#ifdef HAVE_FCNTL_H
#include <fcntl.h>
#endif
#define LOCK(file) setlock(fileno(file), F_WRLCK);
#define UNLOCK(file) setlock(fileno(file), F_UNLCK);
#endif /* LOCK_FCNTL */
#ifdef LOCK_FLOCK
#ifdef... (1 Reply)
Discussion started by: frequency8
1 Replies
6. Shell Programming and Scripting
Hey people!
I just started out working at an ISP as tech support and thought that I should ease the work load by scripting some small macros.
I create different commands with Alias through .bashrc which are all directed to the same script file. Here I planned on using Expect to run different... (0 Replies)
Discussion started by: GhettoFish
0 Replies
7. UNIX for Dummies Questions & Answers
I want to build a Makefile that simply takes a template file and modifies it (sed or perl, probably) before installing the result in the right place - my problem is creating the variable for substitution...
So I have
SYSTEM = SYS1 SYS2
SYS1_CHANNELS = CHANNEL1 CHANNEL2 CHANNEL4... (1 Reply)
Discussion started by: JerryHone
1 Replies
8. Linux
Masters,
I am trying to learn the serial mouse driver for linux kernel. On the kernel source tree I find out these macros and I am unable to find out the meaning of these macros. Please anyone help me to understand these.
These macros are defined in linux/serio.h... (2 Replies)
Discussion started by: iamjayanth
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I've some existing scripts wherein am using ftp + .netrc. I've defined my macros in .netrc file.
I want to switch to sftp now but it seems it doesn't support macros and .netrc and it gives "command invalid" error.
Is there any other alternative?
Note: I don't want help for... (1 Reply)
Discussion started by: ps51517
1 Replies
10. Programming
I have a PORT_NUM macro (10 digits long number)
in a server file, if i do
htons(PORT_NUM)
i get
warning: this decimal constant is unsigned only in ISO C90
warning: large integer implicitly truncated to unsigned type
whats wrong with this? (2 Replies)
Discussion started by: omega666
2 Replies
LEARN ABOUT XFREE86
ccmakedep
ccmakedep(1) General Commands Manual ccmakedep(1)
NAME
ccmakedep - create dependencies in makefiles using a C compiler
SYNOPSIS
ccmakedep [ cpp-flags ] [ -wwidth ] [ -smagic-string ] [ -fmakefile ] [ -oobject-suffix ] [ -v ] [ -a ] [ -cccompiler ] [ -- options -- ]
sourcefile ...
DESCRIPTION
The ccmakedep program calls a C compiler to preprocess each sourcefile, and uses the output to construct makefile rules describing their
dependencies. These rules instruct make(1) on which object files must be recompiled when a dependency has changed.
By default, ccmakedep places its output in the file named makefile if it exists, otherwise Makefile. An alternate makefile may be speci-
fied with the -f option. It first searches the makefile for a line beginning with
# DO NOT DELETE
or one provided with the -s option, as a delimiter for the dependency output. If it finds it, it will delete everything following this up
to the end of the makefile and put the output after this line. If it doesn't find it, the program will append the string to the makefile
and place the output after that.
EXAMPLE
Normally, ccmakedep will be used in a makefile target so that typing 'make depend' will bring the dependencies up to date for the makefile.
For example,
SRCS = file1.c file2.c ...
CFLAGS = -O -DHACK -I../foobar -xyz
depend:
ccmakedep -- $(CFLAGS) -- $(SRCS)
OPTIONS
The program will ignore any option that it does not understand, so you may use the same arguments that you would for cc(1), including -D
and -U options to define and undefine symbols and -I to set the include path.
-a Append the dependencies to the file instead of replacing existing dependencies.
-cccompiler
Use this compiler to generate dependencies.
-fmakefile
Filename. This allows you to specify an alternate makefile in which ccmakedep can place its output. Specifying "-" as the file
name (that is, -f-) sends the output to standard output instead of modifying an existing file.
-sstring
Starting string delimiter. This option permits you to specify a different string for ccmakedep to look for in the makefile. The
default is "# DO NOT DELETE".
-v Be verbose: display the C compiler command before running it.
-- options --
If ccmakedep encounters a double hyphen (--) in the argument list, then any unrecognized arguments following it will be silently
ignored. A second double hyphen terminates this special treatment. In this way, ccmakedep can be made to safely ignore esoteric
compiler arguments that might normally be found in a CFLAGS make macro (see the EXAMPLE section above). -D, -I, and -U options
appearing between the pair of double hyphens are still processed normally.
SEE ALSO
cc(1), make(1), makedepend(1), ccmakedep(1).
AUTHOR
ccmakedep was written by the X Consortium.
Colin Watson wrote this manual page, originally for the Debian Project, based partly on the manual page for makedepend(1).
XFree86 Version 4.7.0 ccmakedep(1)