[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [microblaze-uclinux] command line use of auto-config.in?
Exactly what I was after--that's pretty cool that oldconfig picks up the
auto-config.in info.
I've figured out that a "make clean" is usually required to make sure the
new changes actually take effect. However, I do it before "make dep" not
after??
Paul
Quoting John Williams <jwilliams@itee.uq.edu.au>:
> Hi Paul,
>
> Paul Hartke wrote:
>
> > I've been successfully building microblaze uclinux kernels for a while
> now.
> >
> > I'd like to be able to avoid the interactive step where "make
> menuconfig" is
> > run and then the "Customize Kernel Settings" new config must be saved.
> >
> > Any recommended methods of doing this? The eventual goal is to fully
> build
> > hardware designs and kernels via a script.
>
> you want "make oldconfig" - it will pick up any changes in the presently
> selected auto-config.in, and apply them.
>
> The following line automates the whole thing:
>
> $ yes "" | make oldconfig dep clean all
>
> The clean is for safety - not always necessary but helps avoid
> hard-to-debug wierdness. e.g. if you change CPU support for MUL/DIV,
> that effects the libraries as well, but the auto-dependencies aren't
> quite clever enough to figure that out.
>
> Cheers,
>
> John
> ___________________________
> 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/