12-12-2008
Hm!
That means that different 'make' has different syntax flavor!
I haven't use the man-pages, but book on my table, it is right.
I will try it on work and add a result here.
Thank you for replay!
OK!!
I have checked it and
the second way works in my make,
BUT first one - does not!! - The statement just simply ignored.
Any way, again: Big Thank You!
Last edited by alex_5161; 12-16-2008 at 06:37 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm having a problem with a macro i put in my .exrc file.
Here's what I put: map #I ^[
^ [ is control-v and the escape key.
It places a # a the beginning of a line by simply hitting the # on the keyboard. Problem is, now when I hit "o" or "O" to move up or down a line, it places a # at... (1 Reply)
Discussion started by: Atama
1 Replies
2. HP-UX
I'm upleveling code from 10.20 to 11.11....but I'm running into a problem in which the USRSTACK macro does not seem to be defined in 11.11. Has anybody else experienced this/fixed it/worked around it? Is there a different macro I should be using instead?
Thanks for any info you can provide!! (1 Reply)
Discussion started by: jalburger
1 Replies
3. Programming
Can i define a macro for a function of 10 LOC. (9 Replies)
Discussion started by: bankpro
9 Replies
4. Programming
Hi,
In my application I have some number c files. In each of the file the following line will be the first statement.
#ident "@(#) set.c 14.1.2.2 05/15/01 17:06:32"
I would like to know what is the use of the above statement.
Thanks
Sarwan (1 Reply)
Discussion started by: sarwan
1 Replies
5. Linux
Linux, C++, make, macro
In source code, we used some #ifdef macros. How can I enable #ifdef macro in the command line of "make" (NOTE: I do NOT want to change source code or makefile to define that macro from time to time).
e.g. test.cpp:
...
#ifdef TEST1
// code segment for test1
...... (3 Replies)
Discussion started by: princelinux
3 Replies
6. Shell Programming and Scripting
Hi,
I just opened one old RH box and found number of "macros" in there, that how they called in how-to doc, let say you type <rx> and this does a lot of stuff.
I can't figure out how it work, how I can edit/display these macros? Can anybody point to the right directions? I have some academic... (3 Replies)
Discussion started by: trento17
3 Replies
7. UNIX for Dummies Questions & Answers
Hi everyone,
What I am trying to do is assign a F-key a macro to save a file in vi and display said file in firefox. The details are as follows:
I am using a Win 7 laptop with and ssh program to log into a unix system.
What I am trying to do is figure out how to bring up the firefox... (1 Reply)
Discussion started by: csharp100
1 Replies
8. UNIX for Dummies Questions & Answers
Can I create a macro in UNIX? If so where do I find out how? (1 Reply)
Discussion started by: JD_Sal
1 Replies
9. UNIX for Dummies Questions & Answers
Hey guys, thanks for lookin....my question is I want to create a macro on HPUX to SFTP a .xls to my Windows Server....I have exstensively searched and all I can find is What a macro is not how to create one.
Reasoning for having a macro is to put it in a file creation script and have it run at... (7 Replies)
Discussion started by: DStewart
7 Replies
10. Programming
Can some body explain this part in a header file for me?
#include <limits.h>
#define BIGNUM unsigned long long
typedef BIGNUM (*hash_t) (char *str);
......I have hard time for the second part:
typedef BIGNUM (*hash_t) (char *str); First, I could not find the definition of hash_t, which... (1 Reply)
Discussion started by: yifangt
1 Replies
assert.h(3HEAD) Headers assert.h(3HEAD)
NAME
assert.h, assert - verify program assertion
SYNOPSIS
#include <assert.h>
DESCRIPTION
The <assert.h> header defines the assert() macro. It refers to the macro NDEBUG which is not defined in the header. If NDEBUG is defined as
a macro name before the inclusion of this header, the assert() macro is defined simply as:
#define assert(ignore)((void) 0)
Otherwise, the macro behaves as described in assert(3C).
The assert() macro is redefined according to the current state of NDEBUG each time <assert.h> is included.
The assert() macro is implemented as a macro, not as a function. If the macro definition is suppressed in order to access an actual func-
tion, the behavior is undefined.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO
assert(3C), attributes(5), standards(5)
SunOS 5.10 10 Sep 2004 assert.h(3HEAD)