Subject: Re: port-vax/14238: /bin/cp produces a zero length file on port-vax
To: Chuck Cranor <chuck@xxx.research.att.com>
From: Ken Wellsch <kwellsch@tampabay.rr.com>
List: port-vax
Date: 10/13/2001 20:39:40
On Sat, Oct 13, 2001 at 08:02:05PM -0400, Chuck Cranor wrote:
>  <kwellsch@tampabay.rr.com> wrote:
> 
> >My last build, circa Sept 20th broke when I rebooted it this
> >week to build -current.  I then discovered, that the few /etc
> >files I had copied on the previous build were of zero length.
> >I track this to /bin/cp and ended up using "tar" to do copies.
> 
> hi-
> 
>     yes, this is a compiler bug.  i posted to port-vax about it in this
> message:
> 
> 	http://mail-index.netbsd.org/port-vax/2001/09/10/0010.html
> 
> as far as i know, no one is working to fix this bug.   until it is
> fixed it isn't possible to run a -current on vax without hacking the 
> source tree.

Hi Chuck,

Well, actually I should have proceeded to test my theory, that is,
recent changes to the "cp" source caused the breakage.  Okay, maybe
the changes "should just work" and do not because of a compiler bug,
but I can say that when I

	cvs checkout -D "2 months ago" basesrc/bin/cp

and built the older "cp" with yesterday's -current, this "new old"
copy of "cp" appears to work like a charm.

Looks like utils.c has had some munging on the MMAP code beyond the
Ansification changes.

Your posting referenced above does not provide any intermediate details
or hints so I've no idea if what I have tried is part of the path you
took to ultimately conclude the compiler is broken.

Cheers,

-- Ken