Re: Very touchy eager-to-remake make or kernel makefiles?

From: Igmar Palsenberg (maillist@chello.nl)
Date: Mon Jun 19 2000 - 17:41:01 EST


On Sun, 18 Jun 2000, Russell King wrote:

> Hi,
>
> I've just noticed that yet again make seems to be building a lot of
> files for apparantly no reason.
>
> Let me explain my situation. I have one master tree. From this master
> tree, I rsync the actual kernel build trees on various machines, and then
> start each tree building.
>
> I have built these trees to completion twice thus far, and have just made
> some modifications to the following files:
>
> arch/arm/kernel/setup.c
> arch/arm/special/Makefile
> arch/arm/special/README
> drivers/acorn/char/Makefile
> drivers/acorn/char/defkeymap-acorn.c
> drivers/char/Makefile
> drivers/char/console.c
>
> So, no reason to rebuild kernel/signal.c, since no header files have
> changed, nor has the version number or anything like that. Neither
> have the compilation flags, C compiler or build environment changed.
> The times on each machine are synchronised.
>
> Yet, make seems to find a reason, and is currently rebuilding it
> along with many other files in each tree!
>
> gcc -D__KERNEL__ -I/usr/src/v2.4/linux-assabet/include -Wall -Wstrict-prototypes -O2 -fno-strict-aliasing -pipe -msoft-float -mshort-load-bytes -march=armv4 -mtune=strongarm110 -DEXPORT_SYMTAB -c signal.c
> gcc -D__KERNEL__ -I/usr/src/v2.4/linux-ebsa110/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -msoft-float -mshort-load-bytes -march=armv4 -mtune=strongarm110 -DEXPORT_SYMTAB -c signal.c
> arm-linux-gcc -D__KERNEL__ -I/usr/src/v2.4/linux-ebsa285/include -Wall -Wstrict-prototypes -O2 -pipe -msoft-float -DNO_TEXT_SECTIONS -m6 -DEXPORT_SYMTAB -c signal.c
> arm-linux-gcc -D__KERNEL__ -I/usr/src2/v2.4/linux-rpc/include -Wall -Wstrict-prototypes -O2 -pipe -msoft-float -DNO_TEXT_SECTIONS -m6 -DEXPORT_SYMTAB -c signal.c
>
> (both make 3.74 and make 3.77 appear to behave the same)
>
> I'm confused why make should behave like this. Any ideas? It's
> a shame make doesn't have an option which causes it to print just
> the reason (not its complete database) for the compilation of a
> file.

I already posted a bug report on this. The makefile is realy f*cked up
since 2.2.16.

Try changing 1 c file, do a make and see that make fails after the
System.map is created. No errors are shown.

> RK

        Regards,

                Igmar

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Jun 23 2000 - 21:00:18 EST