Re: [kbuild-devel] .tmp_targets failing?

2001-12-18 Thread Tom Rini

On Tue, Dec 18, 2001 at 02:55:33PM +1100, Keith Owens wrote:
 On Tue, 18 Dec 2001 14:38:05 +1100, 
 Keith Owens [EMAIL PROTECTED] wrote:
 arch_head must be defined in arch/$(ARCH)/Makefile.defs.noconfig.  The
 value of arch_head is used by pp_makefile2 to generate the global
 makefile, Makefile.defs.config is not read until after the global
 makefile is created, in fact Makefile.defs.config is only read by the
 global makefile.
 
 Damn, you need .config to define arch_head, I am going to have to think
 about this.  BTW, I think that the existing kbuild has race conditions
 in ppc, there are situations where you can change the .config but use
 the old HEAD value.

Quite possibly.  But in kbuild-2.5 terms, changing any of the processor
variables would fall under the KBUILD_CRITICIAL stuffs.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



Re: [kbuild-devel] .tmp_targets failing?

2001-12-17 Thread Tom Rini

On Tue, Dec 18, 2001 at 10:31:51AM +1100, Keith Owens wrote:
 On Mon, 17 Dec 2001 15:46:30 -0700, 
 Tom Rini [EMAIL PROTECTED] wrote:
 Hey all.  I'm trying to get PPC going again with kbuild-2.5, but I'm
 runnign into some wierd errors.  Anyone know what would cause the 
 .tmp_targets rule to fail with an error 139?  If I change:
 
 139 = 128+11 - sig 11 - SEGV.  Probably pp_makefile2 is breaking.
 
 cd $KBUILD_OBJTREE
 source .tmp_env   (sets the environment variables, except src/object)
 gdb scripts/pp_makefile2
 r
 
 Where does it break?  What is the backtrace?

It was on a for loop over arch_head.  If I put arch_head in
arch/ppc/Makefile.defs.noconfig, I got to the point of finding (I think)
problems w/ my Makefile.in's.  Is it possible to set arch_head in
arch/$(ARCH)/Makefile.defs.config?

 I get to the point of kbuild-2.5 telling me
 there's no rule to make target 'installable'.
 
 That makes no sense.  Even without selecting a kernel format, the
 installable target is defined to be at least System.map.  Check
 .tmp_global_makefile, find installable:, it should look like this.

It didn't make sense to me either, so I'll assume that w/ the prior
breakage things just went horrible.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



Re: [kbuild-devel] .tmp_targets failing?

2001-12-17 Thread Keith Owens

arch_head must be defined in arch/$(ARCH)/Makefile.defs.noconfig.  The
value of arch_head is used by pp_makefile2 to generate the global
makefile, Makefile.defs.config is not read until after the global
makefile is created, in fact Makefile.defs.config is only read by the
global makefile.

There is a bug in pp_makefile2.c, trim_arch_head() assumes that
arch_head is always set to at least one string.  If you really need an
empty arch_head, change trim_arch_head() from
for (a = arch_head; *a; ++a) {
to
for (a = arch_head; a  *a; ++a) {


___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel



Re: [kbuild-devel] .tmp_targets failing?

2001-12-17 Thread Keith Owens

On Tue, 18 Dec 2001 14:38:05 +1100, 
Keith Owens [EMAIL PROTECTED] wrote:
arch_head must be defined in arch/$(ARCH)/Makefile.defs.noconfig.  The
value of arch_head is used by pp_makefile2 to generate the global
makefile, Makefile.defs.config is not read until after the global
makefile is created, in fact Makefile.defs.config is only read by the
global makefile.

Damn, you need .config to define arch_head, I am going to have to think
about this.  BTW, I think that the existing kbuild has race conditions
in ppc, there are situations where you can change the .config but use
the old HEAD value.


___
kbuild-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kbuild-devel