Re: Automated report: NetBSD-current/i386 build failure

[David Holland <dholland-current%netbsd.org@localhost>]

On Sat, Jul 12, 2014 at 10:51:00PM +0000, NetBSD Test Fixture wrote:
 > This is an automatically generated notice of a NetBSD-current/i386
 > build failure.
 > 
 >     --- dependall-libexec ---
 >     
 > /tmp/bracket/build/2014.07.12.20.31.04-i386/src/sbin/fsck_lfs/lfs.c:88:20: 
 > fatal error: fsutil.h: No such file or directory
 >      #include "fsutil.h"

% grep fsutil.h sbin/fsck_lfs/*.c
sbin/fsck_lfs/dir.c:#include "fsutil.h"
sbin/fsck_lfs/inode.c:#include "fsutil.h"
sbin/fsck_lfs/lfs.c:#include "fsutil.h"
sbin/fsck_lfs/main.c:#include "fsutil.h"
sbin/fsck_lfs/pass0.c:#include "fsutil.h"
sbin/fsck_lfs/pass1.c:#include "fsutil.h"
sbin/fsck_lfs/pass2.c:#include "fsutil.h"
sbin/fsck_lfs/pass4.c:#include "fsutil.h"
sbin/fsck_lfs/pass5.c:#include "fsutil.h"
sbin/fsck_lfs/pass6.c:#include "fsutil.h"
sbin/fsck_lfs/setup.c:#include "fsutil.h"
sbin/fsck_lfs/utilities.c:#include "fsutil.h"

All of those except for lfs.c have been there for years. Anyone want
to suggest what's different about lfs.c?

-- 
David A. Holland
dholland%netbsd.org@localhost