Skip site navigation (1)Skip section navigation (2)
Date:      17 Apr 2005 13:28:01 -0400
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        Gary Lum <glum@SIMS.Berkeley.EDU>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: src out of sync or buildworld broken?
Message-ID:  <443btpnwim.fsf@be-well.ilk.org>
In-Reply-To: <42602097.3060207@sims.berkeley.edu>
References:  <42602097.3060207@sims.berkeley.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Gary Lum <glum@SIMS.Berkeley.EDU> writes:

> Afternoon everyone.
> 
> I track RELENG_5 using cvsup that runs nightly. Today I've been trying
> to buildworld and keep running into problems with missing directories
> and files.
>    First, build world was complaing that the /usr/src/sys/dev/ieee488
> dir was missing. Couldn't find anything on google pertaining to the
> error. I cd'd to the dev dir and it wasn't there so I created it. I
> then ran again and ran into the same thing with
> /usr/src/sys/geom/shsec dir missing, so I created that.
>    Now I'm getting an error message:
> 
> In file included from
> /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha_locl.h:133,
>                   from
> /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/sha/sha_dgst.c:70:
> /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md32_common.h:132:26:
> openssl/fips.h: No such file or directory
> mkdep: compile failed
> *** Error code 1
> 
> Stop in /usr/src/secure/lib/libcrypto.
> *** Error code 1
> 
> find can't find fips.h nor fips
> 
> Any suggestions? How can I resynch my source? I've cvsup'ed twice just
> to be sure

You were missing a directory (ieee488) that hasn't changed in a fairly
long time (the last change of *any* file in there was over a week
earlier than you started having problems), so there are definitely
problems on your end.  

I would suggest shutting down and forcing a full fsck of the partition
with your source tree on it.  Filesystem problems are rare, but they
do happen.  If that doesn't seem to be the problem, cvsup may be
confused on your system for some reason; removing its state files
might help it recover, albeit with a time cost on your next cvsup.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443btpnwim.fsf>