On Mon, 27 Apr 2009, Jeffrey Cao wrote:

> On 2009-04-26, Robert P. J. Day <[email protected]> wrote:
> >
> >   with the latest "git pull," i configured with "make allyesconfig"
> > and got:
> >
> > include/linux/mmzone.h:18:26: error: linux/bounds.h: No such file or 
> > directory
> > include/linux/mmzone.h:256:5: warning: "MAX_NR_ZONES" is not defined
> > include/linux/mmzone.h:258:7: warning: "MAX_NR_ZONES" is not defined
> > include/linux/mmzone.h:260:7: warning: "MAX_NR_ZONES" is not defined
> >
> >   i'm confused -- that <linux/bounds.h> header file certainly seems to
> > be there.  what am i missing?

> Add V=1 to your make command to show the verbose build options.
> Check if the inclusion path is correct.

> BTW, the latest kernel source code in git is not guaranteed to be
> compilable.

  no, my mistake, i don't know what i did wrong but it's all right
now.  that header file is actually generated by the build, so i'm
thinking i somehow did a partial build, a clean, then tried to pick
up where i left off and that's what caused the problem.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

        Linux Consulting, Training and Annoying Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Linked In:                             http://www.linkedin.com/in/rpjday
Twitter:                                       http://twitter.com/rpjday
========================================================================

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [email protected]
Please read the FAQ at http://kernelnewbies.org/FAQ

Reply via email to