possible build system oddity

possible build system oddity

[Oliver Neukum]

Hi,

I only touched sound/usb/usbaudio.c
Nevertheless the whole subtree und sound/ is recompiling. What's
happening?

	Regards
		Oliver

Re: possible build system oddity

[Adrian Bunk]

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)?

> 	Regards
> 		Oliver

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: possible build system oddity

[Alexey Dobriyan]

On 8/31/07, Oliver Neukum <oliver@neukum.org> wrote:
> I only touched sound/usb/usbaudio.c
> Nevertheless the whole subtree und sound/ is recompiling. What's
> happening?

Not here. Do make V=2, it should say why it's recompiling.

Re: possible build system oddity

[Sam Ravnborg]

On Fri, Aug 31, 2007 at 01:14:26PM +0400, Alexey Dobriyan wrote:
> On 8/31/07, Oliver Neukum <oliver@neukum.org> wrote:
> > I only touched sound/usb/usbaudio.c
> > Nevertheless the whole subtree und sound/ is recompiling. What's
> > happening?
> 
> Not here. Do make V=2, it should say why it's recompiling.

And if the problem persist then do a make V=1 and post output here.
This information combined should tell what goes wrong.

	Sam

Re: possible build system oddity

[Oliver Neukum]

Am Freitag 31 August 2007 schrieb Sam Ravnborg:
> On Fri, Aug 31, 2007 at 01:14:26PM +0400, Alexey Dobriyan wrote:
> > On 8/31/07, Oliver Neukum <oliver@neukum.org> wrote:
> > > I only touched sound/usb/usbaudio.c
> > > Nevertheless the whole subtree und sound/ is recompiling. What's
> > > happening?
> > 
> > Not here. Do make V=2, it should say why it's recompiling.
> 
> And if the problem persist then do a make V=1 and post output here.
> This information combined should tell what goes wrong.

Not reproducible. Sorry.

	Regards
		Oliver

Re: possible build system oddity

[Jan Engelhardt]

On Aug 31 2007 11:51, Oliver Neukum wrote:
>Am Freitag 31 August 2007 schrieb Sam Ravnborg:
>> On Fri, Aug 31, 2007 at 01:14:26PM +0400, Alexey Dobriyan wrote:
>> > On 8/31/07, Oliver Neukum <oliver@neukum.org> wrote:
>> > > I only touched sound/usb/usbaudio.c
>> > > Nevertheless the whole subtree und sound/ is recompiling. What's
>> > > happening?
>> > 
>> > Not here. Do make V=2, it should say why it's recompiling.
>> 
>> And if the problem persist then do a make V=1 and post output here.
>> This information combined should tell what goes wrong.
>
>Not reproducible. Sorry.

NFS/etc. involved?


	Jan
-- 

Re: possible build system oddity

[Oliver Neukum]

Am Freitag 31 August 2007 schrieb Jan Engelhardt:
> On Aug 31 2007 11:51, Oliver Neukum wrote:
> >Am Freitag 31 August 2007 schrieb Sam Ravnborg:
> >> On Fri, Aug 31, 2007 at 01:14:26PM +0400, Alexey Dobriyan wrote:
> >> > On 8/31/07, Oliver Neukum <oliver@neukum.org> wrote:
> >> > > I only touched sound/usb/usbaudio.c
> >> > > Nevertheless the whole subtree und sound/ is recompiling. What's
> >> > > happening?
> >> > 
> >> > Not here. Do make V=2, it should say why it's recompiling.
> >> 
> >> And if the problem persist then do a make V=1 and post output here.
> >> This information combined should tell what goes wrong.
> >
> >Not reproducible. Sorry.
> 
> NFS/etc. involved?

No, exclusively on reiserfs.

	Regards
		Oliver

Re: possible build system oddity

[Oliver Neukum]

Am Freitag 31 August 2007 schrieben Sie:
> 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)?
> 
> >       Regards
> >               Oliver
> 
> cu
> Adrian

Nope, it recompiled everything under sound/ and a lot of stuff under
net/. I'll check the system for odd scripts running at night touching stuff.

	Regards
		Oliver

Re: possible build system oddity

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 756 bytes --]

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' ;)


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: possible build system oddity

[Sam Ravnborg]

On Fri, Aug 31, 2007 at 11:00:27AM -0400, Valdis.Kletnieks@vt.edu 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

Re: possible build system oddity

[Jan Engelhardt]

On Aug 31 2007 11:00, Valdis.Kletnieks@vt.edu wrote:
>> 
>> 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' ;)

Changing the top makefile (where your version info is) should only 
result in rebuilding the .mod.c, .mod.o and .ko files.


	Jan
--