rvinterf/etmsync/fsnew.c: cast 0 to (char *) for execl sentinel I generally don't use NULL and use plain 0 instead, based on a "NULL considered harmful" discussion on the classiccmp mailing list many aeons ago (I couldn't find it, and I reason that it must have been 2005 or earlier), but a recent complaint by a packager sent me searching, and I found this: https://ewontfix.com/11/ While I don't give a @#$% about "modern" systems and code-nazi tools, I realized that passing a plain 0 as a pointer sentinel in execl is wrong because it will break on systems where pointers are longer than the plain int type. Again, I don't give a @#$% about the abomination of x86_64 and the like, but if anyone ever manages to port my code to something like a PDP-11 (16-bit int, 32-bit long and pointers), then passing a plain 0 as a function argument where a pointer is expected most definitely won't work: if the most natural stack slot and SP alignment unit is 16 bits, fitting an int, with longs and pointers taking up two such slots, then the call stack will be totally wrong with a plain 0 passed for a pointer. Casting the 0 to (char *) ought to be the most kosher solution for the most retro systems possible.

CC=	gcc
CFLAGS=	-O2
PROGS=	rvtdump rvinterf tfc139
INSTBIN=/opt/freecalypso/bin
LIBS=	../../libserial/libserial.a ../libg23/libg23.a

RVTDUMP_OBJS=	format.o format_fc.o output.o packetrx.o rvtdump.o

RVINTERF_OBJS=	clientcmd.o format.o format_fc.o localsock.o logsent.o \
		output.o packetrx.o packettx.o pktfwd.o rviflcd.o \
		rvifmain.o

TFC139_OBJS=	format.o output.o packetrx.o packettx.o tfc139.o

all:	${PROGS}

rvtdump:	${RVTDUMP_OBJS} ${LIBS}
	${CC} ${CFLAGS} -o $@ ${RVTDUMP_OBJS} ${LIBS}

rvinterf:	${RVINTERF_OBJS} ${LIBS}
	${CC} ${CFLAGS} -o $@ ${RVINTERF_OBJS} ${LIBS}

tfc139:		${TFC139_OBJS} ${LIBS}
	${CC} ${CFLAGS} -o $@ ${TFC139_OBJS} ${LIBS}

install:	${PROGS}
	mkdir -p ${INSTBIN}
	install -c ${PROGS} ${INSTBIN}

clean:
	rm -f *.o *.out *errs ${PROGS}