Date: Thu, 27 Jan 2000 23:22:01 +1300 From: "Dan Langille" <dan@langille.org> To: questions@FreeBSD.ORG Subject: Re: mktemp() possibly used unsafely; consider using mkstemp() Message-ID: <200001271022.XAA31875@ducky.nz.freebsd.org> In-Reply-To: <20000121124814.C77623@mithrandr.moria.org> References: <200001210902.WAA73869@ducky.nz.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 Jan 00, at 12:48, Neil Blakey-Milner wrote:
> On Fri 2000-01-21 (22:02), Dan Langille wrote:
> > syscall.o: In function `do_mktemp':
> > syscall.o(.text+0x2e1): warning: mktemp() possibly used unsafely;
> > consider using mkstemp()
> >
> > Two machines, both on 3.3-19991207-SNAP, both building rsync-2.3.2,
> > one suceeds, the other gets the above. Go figure.
> >
> > Clues please.
>
> It's not a fatal error. There is most probably another reason for
> the failure.
I came back to this problem today. rsync built without problem. I
suspect a port problem which has since been fixed. That isn't to say
the problem was within the rsync port (which, BTW, had a commit on
1.31 Wed Jan 26 9:22:00 2000 UTC by sumikawa, Use ${OSVERSION}
instead of ${USE_INET6}). It may have been that and/or something
which was out ot sync within my ports tree.
cheers.
--
Dan Langille [I'm looking for more work]
http://www.langille.org/ | http://www.unixathome.org/
http://www.racingsystem.com/ | http://www.freebsddiary.org/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001271022.XAA31875>