On Mon, May 16, 2005 at 11:16:41PM +0100, Steven Hartland wrote: > Doing a make buildworld from a directory other than /usr/src > results in the following: > [log] > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libl.a -> > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libln.a > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libfl.a -> > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libln.a > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libl_p.a -> > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libln_p.a > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libfl_p.a -> > /usr/obj/.usr/amd64/src/lib32/usr/lib32/libln_p.a > ===> usr.sbin/pcvt/keycap > Warning: Object directory not changed from original > /.usr/amd64/src/usr.sbin/pcvt/keycap > make: don't know how to make /usr/obj/usr/src/lib32/usr/include/stdio.h. > Stop > *** Error code 2 > > Stop in /.usr/amd64/src. > *** Error code 1 > > Stop in /.usr/amd64/src. > *** Error code 1 > > Stop in /.usr/amd64/src. > *** Error code 1 > > Stop in /.usr/amd64/src. > [/log] > > My /usr is a symlink to /.usr/amd64/ which shouldnt cause any > issues but buildworld get most upset. I first thought it was bad > source set but booting to single user and moving things around > so /usr is a real dir with the contents of /.usr/amd64 in works > just fine. Anyone got any ideas why and how to fix?
You need to make sure you don't have stale object files (the pathnames are recorded), so try removing /usr/obj/ and then running 'make cleandir' from your source tree. Kris
pgpOUnm0mt0Y0.pgp
Description: PGP signature
