Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 23 Sep 2009 15:03:17 +0200
From:      Stefan Ehmann <shoesoft@gmx.net>
To:        Andriy Gapon <avg@icyb.net.ua>
Cc:        Barney Cordoba <barney_cordoba@yahoo.com>, freebsd-current@freebsd.org, pluknet <pluknet@gmail.com>
Subject:   Re: where is device_get_parent function defined
Message-ID:  <200909231503.17836.shoesoft@gmx.net>
In-Reply-To: <4ABA0DC5.6070502@icyb.net.ua>
References:  <654636.94077.qm@web63908.mail.re1.yahoo.com> <200909222244.23901.shoesoft@gmx.net> <4ABA0DC5.6070502@icyb.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 23 September 2009 14:00:05 Andriy Gapon wrote:
> on 22/09/2009 23:44 Stefan Ehmann said the following:
> > On Tuesday 22 September 2009 16:21:54 Barney Cordoba wrote:
...
> >> Except for the 50K recursive warnings from the module build directories
> >> you're correct.
> >
> > In that case, I normally use:
> > find /usr/src/ -type f | xargs grep ^device_get_parent
> >
> > Additionally specifying -name '*.c' should even be faster.
> 
> I am surprised with this whole 'recursive' issue because in a clean source
>  tree there are no recursive symlinks. They only come to be if a developer
>  forgets to run 'make obj' before doing 'make' in modules directories.
> I think that it is a good practice to never pollute the source tree with
>  build objects, they should belong to /usr/obj or equivalent.

Ok, that explains it in my case. To reduce build times/space requirements, I 
only build a small subset of modules when building the kernel.

If I need an additional module, I simply run "make install" or "make load" in 
the respective module directory.



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