Re: [microblaze-uclinux] Make Menuconfig - .config files

["Jim Law" <jlaw@xxxxxxxxxxxxx>]

Thanks Kris,

I've tried your suggestion of an initial use of  <make oldconfig> on a fresh 
install of the tools, .config's etc.  I get the same type of operation: 
i.e. the .config options do not seem to take effect on any first make cycle, 
but if I re-copy them back in after any initial <make oldconfig> or <make 
menuconfig>, they work fine.  The second run-through (after re-copying) I 
just have to answer a few miscelaneous menu questions (missing from the 
.config files??), and all works as advertised.  Subsequent makes run without 
these questions and all is even happier.

Obviously this in not stopping me, as I can do this work-around.  I'm just 
trying to understand the sequence of events that 'activates' these files, 
where the actual 'active' .config settings are, etc.

Thanks,
Jim Law
Iris Power


----- Original Message ----- 
From: "Kristian Chaplin" <kristian.chaplin@xilinx.com>
To: <microblaze-uclinux@itee.uq.edu.au>
Cc: "Kristian Chaplin" <kristian.chaplin@xilinx.com>
Sent: Friday, August 19, 2005 3:41 AM
Subject: RE: [microblaze-uclinux] Make Menuconfig - .config files


> Hi Jim,
>
> I've not tried the exact files you are referring to, but usually, after 
> copying across a new .config file, "make oldconfig" needs to be run to get 
> these settings to take effect.
>
> Cheers,
> Kris
>
>
> --
> ----------------------------------------------------------------------------
> / /\/ Kris Chaplin
> \ \   Applications Engineer - Embedded Processors
> / /   Xilinx Europe
> \_\/\ +44 (0)870-7356-563
>
> -----Original Message-----
> From: owner-microblaze-uclinux@itee.uq.edu.au 
> [mailto:owner-microblaze-uclinux@itee.uq.edu.au] On Behalf Of Jim Law
> Sent: 18 August 2005 20:25
> To: microblaze-uclinux@itee.uq.edu.au
> Subject: [microblaze-uclinux] Make Menuconfig - .config files
>
> Hi all,
>
> We've been struggling to understand why our menuconfig options seem to be 
> so
> far out of whack with those needed for an actual system (NuHo S3-2000 eval
> board).
>
> We've been un-tar-ing the three .config files from David Banas' release, 
> as
> instructed, after we do our source code install, patches, etc.  By 
> following
> what happens when we install on a fresh machine, it seems we've been at
> least able to characterize the behaviour:
>
> - on the first make (clean, menuconfig, dep, make), it seems that the 
> files
> are ignored, and some other set of defaults apply.
>
> - these settings are missing a bunch of stuff, have wrong flash size, 
> etc. -
> we'd been working on trying to "adjust" settings as we came across the
> individual problems they caused
>
> - if the distributed .config files are re-installed after the first make,
> and then a full make (clean, menuconfig, dep, make) is done, all the 
> option
> settings appear correctly when inspected under make menuconfig (hurray!!)
>
> Hope this helps,
>
> Jim Law
> Iris Power Engineering
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
>
>
>
> ___________________________
> microblaze-uclinux mailing list
> microblaze-uclinux@itee.uq.edu.au
> Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
> Mailing List Archive : 
> http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/
>
> 

___________________________
microblaze-uclinux mailing list
microblaze-uclinux@itee.uq.edu.au
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/