[scponly] Unable to compile when using specific configure options

jim at aegis-corp.org jim at aegis-corp.org
Mon Dec 6 13:37:13 EST 2004


Hi list,

I've found the following issue with the release 4.0 of scponly.

If you try to compile the program with "--disable-winscp-compat --disable-scp-compat" at the same time when running configure, you'll get an error.

Eg:
./configure --disable-scp-compat --disable-winscp-compat
gcc -g -O2 -I. -I. -DHAVE_CONFIG_H -DDEBUGFILE='"/usr/local/etc/scponly/debuglevel"' -o scponly.o -c scponly.c
scponly.c:79: `PROG_SCP' undeclared here (not in a function)
scponly.c:79: initializer element is not constant
scponly.c:79: (near initialization for `dangerous_args[0].name')
scponly.c:79: initializer element is not constant
scponly.c:79: (near initialization for `dangerous_args[0]')
scponly.c:80: initializer element is not constant
scponly.c:80: (near initialization for `dangerous_args[1]')
scponly.c:87: initializer element is not constant
scponly.c:87: (near initialization for `dangerous_args[2]')
scponly.c:90: initializer element is not constant
scponly.c:90: (near initialization for `dangerous_args[3]')
make: *** [scponly.o] Error 1

This was working fine with the previous release (3.11).

Regards, JiM.



More information about the scponly mailing list