Folks, I think I've encountered a bug in Makefile.in.append file
handling.
I am using shadow trees with kbuild-2.5 v2.0 i386 2.4.18.
Seems that pp_makefile1 tries to create the merged Makefile.in but the
directory doesn't exist.
E.g Shadow tree has fs/Makefile.in.append
pp_makefile1 tries t
On 07 Apr 2002 21:31:06 +0800,
Richard Chan <[EMAIL PROTECTED]> wrote:
>Seems that pp_makefile1 tries to create the merged Makefile.in but the
>directory doesn't exist.
Yes, pp_makefile1 needs to do mkdir before copying files to the object
directory. I will fix that in kbuild-2.5-core-2, out to
Hi,
Keith Owens wrote:
> kbuild 2.5:
> make -j8 oldconfig installable 8:51 (no make dep needed :)
> make -j8 oldconfig installable :14 (second run, no changes)
These 14 seconds (or 37 seconds on my machine) are always needed
whatever I try, e.g. "make foo/bar.o" also needs that time.
Some
On Sun, 07 Apr 2002 16:18:12 +0200,
Roman Zippel <[EMAIL PROTECTED]> wrote:
>Keith Owens wrote:
>
>> kbuild 2.5:
>> make -j8 oldconfig installable 8:51 (no make dep needed :)
>> make -j8 oldconfig installable :14 (second run, no changes)
>
>These 14 seconds (or 37 seconds on my machine) are
Hi,
Keith Owens wrote:
> >These 14 seconds (or 37 seconds on my machine) are always needed
> >whatever I try, e.g. "make foo/bar.o" also needs that time.
>
> make NO_MAKEFILE_GEN=1 foo/bar.o. Very low overhead for quick and
> dirty testing of changes, but if you want an accurate kernel build,
On Sun, 07 Apr 2002 16:51:36 +0200,
Roman Zippel <[EMAIL PROTECTED]> wrote:
>Keith Owens wrote:
>> make NO_MAKEFILE_GEN=1 foo/bar.o. Very low overhead for quick and
>> dirty testing of changes, but if you want an accurate kernel build, you
>> have to take the overhead. kbuild 2.4 overhead for a
Hi,
Keith Owens wrote:
> It takes time to do all the analysis to work out what has changed and
> what has been affected. You might know that you only changed one file
> but kernel build and make don't know that until they have checked
> everything. Changing one file or specifying a command ove
Keith Owens wrote:
>It takes time to do all the analysis to work out what has changed and
>what has been affected. You might know that you only changed one file
>but kernel build and make don't know that until they have checked
>everything. Changing one file or specifying a command override m
