|
From: Julián M. P. <dar...@gm...> - 2010-12-28 07:10:03
|
Hi Mij,
Now I am working in a daemon for Debian, but when I try to compile sshguard
1.5 rc4 in my kfreebsd system does not work:
make[1]: se sale del directorio `/home/junix/sshguard/sshguard-1.5rc4'
dh_auto_build
make[1]: se ingresa al directorio `/home/junix/sshguard/sshguard-1.5rc4'
Making all in src
make[2]: se ingresa al directorio `/home/junix/sshguard/sshguard-1.5rc4/src'
make all-recursive
make[3]: se ingresa al directorio `/home/junix/sshguard/sshguard-1.5rc4/src'
Making all in parser
make[4]: se ingresa al directorio
`/home/junix/sshguard/sshguard-1.5rc4/src/parser'
make all-am
make[5]: se ingresa al directorio
`/home/junix/sshguard/sshguard-1.5rc4/src/parser'
gcc -DHAVE_CONFIG_H -I. -I../../src -I. -I.. -Wall -std=c99
-D_POSIX_C_SOURCE=200112L -g -O2 -c attack_parser.c
gcc -DHAVE_CONFIG_H -I. -I../../src -I. -I.. -Wall -std=c99
-D_POSIX_C_SOURCE=200112L -g -O2 -c attack_scanner.c
attack_scanner.c:11736: warning: ‘yyunput’ defined but not used
attack_scanner.c:11786: warning: ‘input’ defined but not used
rm -f libparser.a
ar cru libparser.a attack_parser.o attack_scanner.o
ranlib libparser.a
make[5]: se sale del directorio
`/home/junix/sshguard/sshguard-1.5rc4/src/parser'
make[4]: se sale del directorio
`/home/junix/sshguard/sshguard-1.5rc4/src/parser'
Making all in fwalls
make[4]: se ingresa al directorio
`/home/junix/sshguard/sshguard-1.5rc4/src/fwalls'
gcc -DHAVE_CONFIG_H -I. -I../../src -I. -I.. -Wall -std=c99
-D_POSIX_C_SOURCE=200112L -g -O2 -c command.c
rm -f libfwall.a
ar cru libfwall.a command.o
ranlib libfwall.a
make[4]: se sale del directorio
`/home/junix/sshguard/sshguard-1.5rc4/src/fwalls'
make[4]: se ingresa al directorio `/home/junix/sshguard/sshguard-1.5rc4/src'
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
seekers.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard_whitelist.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard_log.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard_procauth.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard_blacklist.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard_options.c
gcc -DHAVE_CONFIG_H -I. -I. -std=c99 -Wall -D_XOPEN_SOURCE -g -O2 -c
sshguard_logsuck.c
sshguard_logsuck.c:67: error: ‘PATH_MAX’ undeclared here (not in a function)
sshguard_logsuck.c: In function ‘logsuck_getline’:
sshguard_logsuck.c:245: warning: format ‘%lu’ expects type ‘long unsigned
int’, but argument 3 has type ‘uintptr_t’
make[4]: *** [sshguard_logsuck.o] Error 1
make[4]: se sale del directorio `/home/junix/sshguard/sshguard-1.5rc4/src'
make[3]: *** [all-recursive] Error 1
make[3]: se sale del directorio `/home/junix/sshguard/sshguard-1.5rc4/src'
make[2]: *** [all] Error 2
make[2]: se sale del directorio `/home/junix/sshguard/sshguard-1.5rc4/src'
make[1]: *** [all-recursive] Error 1
make[1]: se sale del directorio `/home/junix/sshguard/sshguard-1.5rc4'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
This FTBFS could be avoided if is added in src/sshguard_logsuck.c :
#ifndef PATH_MAX
# define PATH_MAX 4096
#endif
But I don't know if PATH_MAX value to KfreeBSD is right.
Any suggestion for this ?
Kind regards,
--
Julián Moreno Patiño
.''`. Debian GNU/{Linux,KfreeBSD}
: :' : Free Operating Systems
`. `' http://debian.org/
`- PGP KEY ID 6168BF60
Registered GNU Linux User ID 488513
|