Re: possible build system oddity
- From: Sam Ravnborg <sam@xxxxxxxxxxxx>
- Date: Fri, 31 Aug 2007 18:30:44 +0200
On Fri, Aug 31, 2007 at 11:00:27AM -0400, Valdis.Kletnieks@xxxxxx wrote:
On Fri, 31 Aug 2007 10:42:29 +0200, Adrian Bunk said:
On Fri, Aug 31, 2007 at 10:37:28AM +0200, Oliver Neukum wrote:
Hi,
I only touched sound/usb/usbaudio.c
Nevertheless the whole subtree und sound/ is recompiling. What's
happening?
The only file that gets compiled (CC) should be sound/usb/usbaudio.c
It seems you are confused by the fact that this recompilation results in
several relinks (LD)?
Or something else changed that he didn't realize. Just the other day, I
applied a one-line patch that hit one .c file, and *the entire kernel*
started rebuilding.
Took me a while to figure out that I'd been looking for something else, and
done a 'vi Makefile' in the top level, and exited with 'ZZ' rather than ':q' ;)
That should not result in a full rebuild, but you would see at least stuff in
kernel/ being compiled.
kbuild try to track all dependencies and sometimes people have a few suprises.
But the important part is that people *trust* that kbuild does the right thing
when they touch something - and so it is these days.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- possible build system oddity
- From: Oliver Neukum
- Re: possible build system oddity
- From: Adrian Bunk
- Re: possible build system oddity
- From: Valdis . Kletnieks
- possible build system oddity
- Prev by Date: Re: [PATCH] Fix a lock problem in generic phy code
- Next by Date: Re: [RFC][PATCH] detect & print stack overruns at oops time
- Previous by thread: Re: possible build system oddity
- Next by thread: Re: possible build system oddity
- Index(es):
Relevant Pages
|
|
