Date: Fri, 28 Jan 2000 10:42:47 +1300 From: "Dan Langille" <dan@freebsddiary.org> To: ports@freebsd.org Cc: dan@freebsddiary.org Subject: rsync fails to build Message-ID: <200001272142.KAA37985@ducky.nz.freebsd.org>
next in thread | raw e-mail | index | archive | help
rsync fails to build on one box, but installs on another. I have no idea
the error occurs:
cc -O -pipe -Dss_family=__ss_family -Dss_len=__ss_len -o rsync
rsync.o generator.o receiver.o cleanup.o sender.o exclude.o util.o
main.o checksum.o match.o syscall.o log.o backup.o options.o flist.o
io.o compat.o hlink.o token.o uidlist.o socket.o fileio.o params.o
loadparm.o clientserver.o access.o connection.o authenticate.o
lib/getopt.o lib/fnmatch.o lib/compat.o lib/snprintf.o lib/mdfour.o
getaddrinfo.o getnameinfo.o zlib/deflate.o zlib/infblock.o zlib/infcodes.o
zlib/inffast.o zlib/inflate.o zlib/inftrees.o zlib/infutil.o zlib/trees.o
zlib/zutil.o zlib/adler32.o
syscall.o: In function `do_mktemp':
syscall.o(.text+0x2e1): warning: mktemp() possibly used unsafely;
consider using mkstemp()
Background info:
I had this problem before, it went away, now it's back. It started with
this error I encounted this morning when trying to rsync from my server:
deflate on token returned -2 (700 bytes left)
read error: Connection reset by peer
unexpected EOF in read_timeout
Checking various archives, I found a message from David E. O'Brien
dated 2000/01/22 10:00:34 PST at
http://x31.deja.com/[ST_rn=ps]/getdoc.xp?AN=576206258&CONTEXT=9
49005217.1798438935&hitnum=0
which mentioned "We *MUST* use the supplied zlib, not our own
/usr/lib/libz.".
I tried the rsync without the -z option. It worked. So I decided my ports
were out of date and went to rebuild them on both the client and the
server. The server built fine. The client build fails.
the client (build fails):
[root@fred:/usr/ports/net/rsync] # head Makefile
# ex:ts=8
# New ports collection makefile for: rsync
# Version required: 2.3.1
# Date created: Sat Aug 3, 1996
# Whom: David O'Brien (obrien@cs.ucdavis.edu)
#
# $FreeBSD: ports/net/rsync/Makefile,v 1.32 2000/01/27 07:58:51
sumikawa Exp $
#
DISTNAME= rsync-2.3.2
[root@fred:/usr/ports/net/rsync] # uname -a
FreeBSD fred.int.nz.freebsd.org 3.3-19991207-SNAP FreeBSD 3.3-
19991207-SNAP #0: Tue Jan 25 18:13:40 NZDT 2000
root@fred.int.nz.freebsd.org:/nzmirror/src/sys/compile/FRED33S i386
the server (build succeeds):
[root@ducky:/usr/ports/net/rsync] # head Makefile
# ex:ts=8
# New ports collection makefile for: rsync
# Version required: 2.3.1
# Date created: Sat Aug 3, 1996
# Whom: David O'Brien (obrien@cs.ucdavis.edu)
#
# $FreeBSD: ports/net/rsync/Makefile,v 1.32 2000/01/27 07:58:51
sumikawa Exp $
#
DISTNAME= rsync-2.3.2
[root@ducky:/usr/ports/net/rsync] # uname -a
FreeBSD ducky.nz.freebsd.org 3.3-19991207-SNAP FreeBSD 3.3-
19991207-SNAP #0: Wed Dec 29 14:46:59 NZDT 1999
root@ducky.nz.freebsd.org:/usr/src/sys/compile/DUCKY33S i386
FWIW: I had the same problem about two weeks ago when I first
installed rsync. I left it for a few days, came back to it, and it built.
Said box sup's the ports daily.
Any ideas why one box builds it and the other doesn't?
--
Dan Langille - DVL Software Limited [I'm looking for more work]
The FreeBSD Diary - http://www.freebsddiary.org/
NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/
The Racing System - http://www.racingsystem.com/
unix @ home - http://www.unixathome.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001272142.KAA37985>