Paths

Table of Contentst

null
ClosedPublic
Actions

Authored by brd on Jul 27 2018, 10:05 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Mon, Nov 10, 4:28 AM

	Unknown Object (File)
	Sat, Nov 8, 5:29 PM

	Unknown Object (File)
	Sat, Nov 8, 5:17 PM

	Unknown Object (File)
	Fri, Nov 7, 5:26 PM

	Unknown Object (File)
	Fri, Nov 7, 6:40 AM

	Unknown Object (File)
	Sun, Nov 2, 12:57 PM

	Unknown Object (File)
	Sat, Nov 1, 1:17 AM

	Unknown Object (File)
	Tue, Oct 28, 2:23 AM

Subscribers

Details

Reviewers

allanjude
bapt
will

Commits

rS336794: Avoid a install(1) crash by not using -C when the source is /dev/null

Summary

Apparently when the file already exists, the /dev/null handling in install(1)
is not sufficient. So this works around it, and does not use -C when /dev/null
is the source.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

brd created this revision.Jul 27 2018, 10:05 PM

Herald added subscribers: emaste, imp, bdrewery. · View Herald TranscriptJul 27 2018, 10:05 PM

Harbormaster completed remote builds in B18385: Diff 45930.Jul 27 2018, 10:05 PM

Approved By: allanjude

This revision is now accepted and ready to land.Jul 27 2018, 10:39 PM

make distribution no longer crashes with this.

Closed by commit rS336794: Avoid a install(1) crash by not using -C when the source is /dev/null (authored by brd). · Explain WhyJul 27 2018, 10:47 PM

This revision was automatically updated to reflect the committed changes.

This seems like a bug that should be fixed in install(1), not here. It's unclear from the description what the actual bug is.

Revision Contents
Changeset List

Path

Size

head/

share/

mk/

bsd.confs.mk

8 lines

Diff 45931

View Options

head/share/mk/bsd.confs.mk

Handle a bug with install(1) -C and /dev/nullClosedPublicActions