compile errors with rsync 2.5.0 for RedHat linux 7.1 alpha

[Dave Dykstra]

On Sat, Dec 15, 2001 at 08:05:26AM -0800, Friedrisch Muller wrote:
> Hi,
> 
> Trying to compile rsync 2.5.0 for RedHat linux 7.1
> alpha but I get compile errors. :-( Any ideas would be
> greatly appreciated!
> 
> # uname -a
> Linux myhost 2.4.9-12 #1 Tue Oct 30 18:12:52 EST 2001
> alpha unknown
> 
> # cat /etc/redhat-release
> Red Hat Linux release 7.1 (Seawolf)
> 
> # ./configure --prefix=/usr/local/rsync-2.5.0
> configure: Configuring rsync 2.5.0
> checking build system type...
> alphaev6-unknown-linux-gnu
> checking host system type...
> alphaev6-unknown-linux-gnu
> checking target system type...
> alphaev6-unknown-linux-gnu
> checking for gcc... gcc
> checking for C compiler default output... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for executable suffix...
> checking for object suffix... o
> checking whether we are using the GNU C compiler...
> yes
> checking whether gcc accepts -g... yes
> checking how to run the C preprocessor... gcc -E
> checking for a BSD compatible install...
> /usr/bin/install -c
> checking for gcc option to accept ANSI C... none
> needed
> checking whether to include debugging symbols... yes
> checking for remsh... 0
> checking for broken largefile support... no
> checking for special C compiler options needed for
> large files... no
> checking for _FILE_OFFSET_BITS value needed for large
> files... no
> checking for _LARGE_FILES value needed for large
> files... no
> checking ipv6 stack type... linux-glibc
> checking for library containing getaddrinfo... none
> required
> checking whether byte ordering is bigendian... no
> checking for dirent.h that defines DIR... yes
> checking for opendir in -ldir... no
> checking whether time.h and sys/time.h may both be
> included... yes
> checking for sys/wait.h that is POSIX.1 compatible...
> yes
> checking for sys/fcntl.h... yes
> checking for sys/select.h... yes
> checking for fcntl.h... yes
> checking for sys/time.h... yes
> checking for sys/unistd.h... yes
> checking for unistd.h... yes
> checking for utime.h... yes
> checking for grp.h... yes
> checking for compat.h... no
> checking for sys/param.h... yes
> checking for ctype.h... yes
> checking for sys/wait.h... (cached) yes
> checking for sys/ioctl.h... yes
> checking for sys/filio.h... no
> checking for string.h... yes
> checking for stdlib.h... yes
> checking for sys/socket.h... yes
> checking for sys/mode.h... no
> checking for glob.h... yes
> checking for alloca.h... yes
> checking for mcheck.h... yes
> checking for sys/sysctl.h... yes
> checking for arpa/inet.h... yes
> checking for arpa/nameser.h... yes
> checking for netdb.h... yes
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... (cached) yes
> checking for string.h... (cached) yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... (cached) yes
> checking for int... yes
> checking size of int... 4
> checking for long... yes
> checking size of long... 8
> checking for short... yes
> checking size of short... 2
> checking for inline... inline
> checking return type of signal handlers... void
> checking for uid_t in sys/types.h... yes
> checking for mode_t... yes
> checking for off_t... yes
> checking for size_t... yes
> checking for pid_t... yes
> checking type of array argument to getgroups... gid_t
> checking for struct stat.st_rdev... yes
> checking for ino_t... yes
> checking for socklen_t... yes
> checking for errno in errno.h... yes
> checking for connect... yes
> checking for inet_ntop in -lresolv... yes
> configure: Looking in libraries: -lresolv
> checking for inet_ntop... yes
> checking for inet_pton... yes
> checking for getaddrinfo... yes
> checking for getnameinfo... yes
> checking for struct sockaddr.sa_len... no
> checking for strcasecmp... yes
> checking whether utime accepts a null argument... yes
> checking for waitpid... yes
> checking for wait4... yes
> checking for getcwd... yes
> checking for strdup... yes
> checking for strerror... yes
> checking for chown... yes
> checking for chmod... yes
> checking for mknod... yes
> checking for fchmod... yes
> checking for fstat... yes
> checking for strchr... yes
> checking for readlink... yes
> checking for link... yes
> checking for utime... yes
> checking for utimes... yes
> checking for strftime... yes
> checking for memmove... yes
> checking for lchown... yes
> checking for vsnprintf... yes
> checking for snprintf... yes
> checking for asprintf... yes
> checking for setsid... yes
> checking for glob... yes
> checking for strpbrk... yes
> checking for strlcat... no
> checking for strlcpy... no
> checking for mtrace... yes
> checking for working socketpair... yes
> checking for working fnmatch... yes
> checking for poptGetContext in -lpopt... yes
> checking whether to use included libpopt... no
> checking for long long... yes
> checking for off64_t... no
> checking for short ino_t... no
> checking for unsigned char... no
> checking for broken readdir... no
> checking for utimbuf... yes
> checking if gettimeofday takes tz argument... yes
> checking for C99 vsnprintf... yes
> checking for secure mkstemp... yes
> checking for broken inet_ntoa... no
> checking for broken inet_aton... no
> checking whether -c -o works... yes
> configure: creating ./config.status
> config.status: creating Makefile
> config.status: creating lib/dummy
> config.status: creating zlib/dummy
> config.status: creating popt/dummy
> config.status: creating shconfig
> config.status: creating config.h
> 
> # make
> gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -c rsync.c -o
> rsync.o
> In file included from rsync.c:23:
> rsync.h:574: conflicting types for `inet_ntop'
> /usr/include/arpa/inet.h:67: previous declaration of
> `inet_ntop'
> make: *** [rsync.o] Error 1



Apparently nobody else is having a problem with that.  Can you please try
the latest source under the "preview" directory to see if it still has the
problem?  If so, you'll probably need to debug it yourself and submit a
patch because nobody has quite your configuration.  There are a lot of
machines that are set up to automatically build the latest rsync sources
every day, but I don't see your exact type listed.  See http://build.samba.org.

- Dave Dykstra