Re: Annoying problem with "cvs update -Pd" in /usr/src building current

[Johnny Billquist <bqt%softjar.se@localhost>]

Yes.

And that is because your build is leaving files behind in the source directories, which then conflicts with cvs checkouts.

The solution is to build with a separate object directory.

  Johnny

pimin inwa <pimininca%gmail.com@localhost> skrev: (21 mars 2017 15:55:47 CET)

Should have included the commands:

cd /usr/src
cvs update -Pd
 ./build.sh -U -u -o -O BUILD_OBJ -T BUILD_TOOL release

This will occasionally blowup in the cvs command with the problem.

Paul N.

On Tue, Mar 21, 2017 at 5:15 AM, Johnny Billquist <bqt%softjar.se@localhost> wrote:

Run your builds with an object directory set up. Looks like you get your output files in the same directory as the source.

Johnny

pimin inwa <pimininca%gmail.com@localhost> skrev: (21 mars 2017 05:08:55 CET)

I'm seeing this annoying situation with cvs, especially after a failed build (as described in another thread).  

cvs update: Updating usr.bin/ktrace/kdump

cvs [update aborted]: could not chdir to usr.bin/ktrace/ktrace: Not a directory

I find I have to remove these files in order to proceed:

 rm -fr  usr.bin/ktrace/ktrace  usr.bin/man/man usr.sbin/mrouted/mrouted  usr.sbin/racoon/racoon

Where am I going wrong?

Paul

--
Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.

-- 
Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.