Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-22 Thread John Baldwin
; And simple test case proving that make v9201206140 dislike empty commands. > > Makefile: > > > > CTFCONVERT_CMD= > > all: > > echo ${MAKE_VERSION} > > ${CTFCONVERT_CMD} > > echo b > > -----

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-22 Thread Andrey Chernov
-- > CTFCONVERT_CMD= > all: > echo ${MAKE_VERSION} > ${CTFCONVERT_CMD} > echo b > -------- >> make > echo 9201206140 > 9201206140 > ${CTFCONVERT_CMD} expands to empty string >

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-22 Thread Andrey Chernov
140 9201206140 ${CTFCONVERT_CMD} expands to empty string echo b b On 22.10.2012 20:08, Andrey Chernov wrote: > On 22.10.2012 19:42, John Baldwin wrote: >> On Sunday, October 21, 2012 8:25:32 pm Andrey Chernov wrote: >>> Those lines cause this error: >>> .if ${MK_C

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-22 Thread Andrey Chernov
ed-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c /usr/src/usr.bin/ma

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-22 Thread John Baldwin
On Sunday, October 21, 2012 8:25:32 pm Andrey Chernov wrote: > Those lines cause this error: > .if ${MK_CTF} != "no" > CTFCONVERT_CMD= ${CTFCONVERT} ${CTFFLAGS} ${.TARGET} > .elif ${MAKE_VERSION} >= 520300 > CTFCONVERT_CMD= > .else > CTFCONVERT_CMD= @: > .endif > > My make version is 920120614

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-21 Thread Andrey Chernov
Those lines cause this error: .if ${MK_CTF} != "no" CTFCONVERT_CMD= ${CTFCONVERT} ${CTFFLAGS} ${.TARGET} .elif ${MAKE_VERSION} >= 520300 CTFCONVERT_CMD= .else CTFCONVERT_CMD= @: .endif My make version is 9201206140 So, either the check for >= 520300 is incorrect or change for empty make va

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-20 Thread Andrey Chernov
On 20.10.2012 16:38, John Baldwin wrote: > On Friday, October 19, 2012 09:06:55 PM Andrey Chernov wrote: >> On recent -stable I got a lots of (see subj) now due to CTF changes in >> *.mk files. >> I have >> WITHOUT_CDDL=yes >> in my /etc/src.conf and WITHOUT_CDDL have wider scope than WITHOUT_CTF >

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-20 Thread John Baldwin
On Friday, October 19, 2012 09:06:55 PM Andrey Chernov wrote: > On recent -stable I got a lots of (see subj) now due to CTF changes in > *.mk files. > I have > WITHOUT_CDDL=yes > in my /etc/src.conf and WITHOUT_CDDL have wider scope than WITHOUT_CTF > suggested, but WITHOUT_CDDL is not checked in r

Re: ${CTFCONVERT_CMD} expands to empty string

2012-10-19 Thread Andrey Chernov
recent CTF changes. > Please fix this thing. > BTW, I got that ${CTFCONVERT_CMD} expands to empty string even placing WITHOUT_CTF=yes into /etc/src.conf ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-sta

${CTFCONVERT_CMD} expands to empty string

2012-10-19 Thread Andrey Chernov
On recent -stable I got a lots of (see subj) now due to CTF changes in *.mk files. I have WITHOUT_CDDL=yes in my /etc/src.conf and WITHOUT_CDDL have wider scope than WITHOUT_CTF suggested, but WITHOUT_CDDL is not checked in recent CTF changes. Please fix this thing.