From owner-freebsd-bugs@freebsd.org  Sun May 29 10:09:37 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D75EB4F73B
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun, 29 May 2016 10:09:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 3A7FE10DA
 for <freebsd-bugs@FreeBSD.org>; Sun, 29 May 2016 10:09:37 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4TA9bjZ017861
 for <freebsd-bugs@FreeBSD.org>; Sun, 29 May 2016 10:09:37 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 209449] Buildworld fails because of bad flag in substitute
 command
Date: Sun, 29 May 2016 10:09:37 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: misc
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: tschweikle@gmail.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-209449-8-Wy7N1tZKvF@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-209449-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-209449-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 29 May 2016 10:09:37 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209449

--- Comment #5 from tschweikle@gmail.com ---
If sed was broken in base r299279 and reverted in base r299294. Shouldn't s=
ed
be rebuild with:

chflags -R noschg /usr/obj/*
rm -rf /usr/obj
cd /usr/src
make cleandir
make cleandir
svn up
make buildworld
make buildkernel KERNCONF=3DFBSD
make installkernel KERNCONF=3DFBSD

thus installkernel using the corrected sed? I've found a newly build sed in
./usr.bin/sed/sed seems copied to ./rescue/rescue/usr/src/usr.bin/sed but t=
his
sed seemed to have the bug too.

--=20
You are receiving this mail because:
You are the assignee for the bug.=