Build problems from $HOME

[YONETANI Tomokazu]

Hi.

On Wed, Jun 02, 2004 at 11:16:10PM -0500, William M. Grim wrote:
> Hello, everyone!
> 
> This isn't really a bug as far as I can tell, but it's related to 
> building dfly from a place other than where CVSup saves files.
> 
> Normally, when I CVSup the dfly source, it downloads to /usr/dfly/src. 
> I can do all my builds perfectly fine from this directory.
> 
> However, since I'm doing some porting work from FBSD over to DFly, I 
> place all the code into a local CVS and check it out to $HOME/src/dfly/. 
>  When I do a "make buildworld" from this directory, it goes quite well 
> for a while, and then it breaks.  I've tried deleting the /usr/obj/ 
> directory and trying again, but the same things happens.

Did you use cvs import command when you put the FreeBSD source tree
into you local CVS? Normally CVS ignores number of files with specific
suffixes when you import it. Run `info cvs' and try looking for a section
`Ignoring files via cvsignore' and you'll find that `.so' is one such
suffix that is ignored by default. You can specify -I'!' to import command
to reset the ignore list.

> I've attached my build errors from $HOME/src/dfly/ as buildworld.txt. 
> I've also attached the successfully "make buildworld" I get when doing 
> it from /usr/dfly/src.
> 
> What could be causing the problem?  The answer is not obvious to me, and 
> when I do "make buildworld" from my home directory, I always do it as 
> root, since it must write to /usr/obj/.

Either chmod 1777 /usr/obj, or set environment variable MAKEOBJDIRPREFIX
to somewhere like $HOME/obj, so that a non-root user can write to OBJDIR.
Be careful not to put MAKEOBJDIRPREFIX in make.conf, or your
buildworld/buildkernel will stop at a strange place.