Make-question - redefine a macro, using another macro..?

Applications Programming
1

I think there is no problem to use any macro in a new macro definishion, but I have a problem with that.
I can not understand why?

I have a *.mak file that inludes file with many definitions and rules.

##############################################
include dstndflt.mak
...

One of the declarations I need to change, adding some options
Thant is

PCFLAGS=MODE=ANSI RELEASE_CURSOR=NO LTYPE=$(LIST) IRECLEN=255 -xs \
ORECLEN=255 DEF_SQLCODE=YES $(PCADD)

In my make-file on begining I do that:

...
PCFLAGS=SQLCHECK=SEMANTICS $(PCFLAGS)  
...

and proces it. - Have an error:

> make -f t_7713_DB.mak
mksh: Fatal error in reader: Loop detected when expanding macro value `SQLCHECK=SEMANTICS $(PCFLAGS)'

What is wrong?
I have tryed with temporary reassigning, but the same result:

tmp=$(PCFLAGS)
PCFLAGS=SQLCHECK=SEMANTICS $(tmp)   
...
 #in shell, executing
> make -f t_7713_DB.mak
mksh: Fatal error in reader: Loop detected when expanding macro value `SQLCHECK=SEMANTICS $(tmp)'

Upreciate your help!

2

With GNU make you can use a "simply expanded" variable, e.g.

PCFLAGS := SQLCHECK=SEMANTICS $(PCFLAGS)

to prepend a string to a variable, or

PCFLAGS += SQLCHECK=SEMANTICS

to append it.

3

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!