[scponly] Unable to compile when using specific configure options

[Hideyuki KURASHINA]

Hi,

>>> On Mon, 6 Dec 2004 19:37:13 +0100, jim at aegis-corp.org said:

> 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

It looks like the problem I've encountered.  To resolve this issue,
apply a patch reported at

  https://lists.ccs.neu.edu/pipermail/scponly/2004-December/000655.html

-- rushani