On Sun, 07 Apr 2002 16:18:12 +0200,
Roman Zippel [EMAIL PROTECTED] wrote:
touch include/linux/mm.h doesn't cause a recompile of any object.
I have found a bug that is probably causing your problem. Can you
confirm that you are using a common source and object directory, i.e.
no separate object
Hi,
On Mon, 8 Apr 2002, Keith Owens wrote:
touch include/linux/mm.h doesn't cause a recompile of any object.
I have found a bug that is probably causing your problem. Can you
confirm that you are using a common source and object directory, i.e.
no separate object tree?
Yes, so far I
Is it easy to patch from release 2 from the the previous release of
kbuild-2.5 ?
ie. is it as easy as untarring everyting in the Linux source directory
that has the previous kbuild-2.5 patches applied ??
Maybe I have to remvoe the Makefile-2.5 directory and the entire scripts
directory first
I'm using a configuration management system. The kernel is in the
repository. It has some custom mods and the kbuild-2.5 (previous
release) applied. I just wanted to apply the new one over the top. I
could probably backout the the changeset that put the kbuild patches in
but I've never
On Mon, 2002-04-08 at 19:45, Brendan J Simon wrote:
Is it easy to patch from release 2 from the the previous release of
kbuild-2.5 ?
ie. is it as easy as untarring everyting in the Linux source directory
that has the previous kbuild-2.5 patches applied ??
Maybe I have to remvoe the
On Tue, 09 Apr 2002 12:45:18 +1000,
Brendan J Simon [EMAIL PROTECTED] wrote:
Is it easy to patch from release 2 from the the previous release of
kbuild-2.5 ?
ie. is it as easy as untarring everyting in the Linux source directory
that has the previous kbuild-2.5 patches applied ??
Maybe I have
On 08 Apr 2002 19:38:23 -0700,
Thomas Duffy [EMAIL PROTECTED] wrote:
I have not investigated deeply as to why this is happening, but thought
I would fire off an email to see if you might know what would be causing
it, but it seems that the new kbuild v2.0 does not work on sparc64. I
have tried