All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Aruna Hewapathirane <aruna.hewapathirane@gmail.com>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: make menuconfig and make j$(nproc) throwing errors
Date: Thu, 24 Feb 2022 07:46:36 +0100	[thread overview]
Message-ID: <YhcpzPsUxPnD/krx@kroah.com> (raw)
In-Reply-To: <CAFSeFg_QOiqoKEe9Z9tz32nddEGvEmcF56nnr5dVL0mPUa=Uuw@mail.gmail.com>

On Wed, Feb 23, 2022 at 10:58:45PM -0500, Aruna Hewapathirane wrote:
> And I tried to build without make menuconfig and make is telling me I
> need 'bison' ? Why do I need bison ? Since when
> did we need bison ? See below for details.
> 
> aruna@debian:/media/aruna/linux-next/home/linux-5.16.10$ make -j$(nproc)
>   DESCEND objtool
>   HOSTCC  scripts/asn1_compiler
>   YACC    scripts/genksyms/parse.tab.[ch]
> /bin/sh: 1: bison: not found

You need bison to build the kernel, sorry, please install it.

> make[2]: *** [scripts/genksyms/Makefile:21:
> scripts/genksyms/parse.tab.c] Error 127
> make[1]: *** [scripts/Makefile.build:549: scripts/genksyms] Error 2
> make[1]: *** Waiting for unfinished jobs....
> <stdin>:1:10: fatal error: libelf.h: No such file or directory

You also need libelf.

thanks,

greg k-h

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2022-02-24  6:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24  3:58 make menuconfig and make j$(nproc) throwing errors Aruna Hewapathirane
2022-02-24  6:46 ` Greg KH [this message]
2022-02-24 10:40   ` Aruna Hewapathirane
2022-02-24 11:37     ` Greg KH
2022-02-24 12:02       ` Aruna Hewapathirane
2022-02-24 13:28         ` Constantine Shulyupin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YhcpzPsUxPnD/krx@kroah.com \
    --to=greg@kroah.com \
    --cc=aruna.hewapathirane@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.