From: Greg KH <greg@kroah.com>
To: Shreyasi Rao <shreyasirao97@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] Compile your changes- Tutorial(make -j2)
Date: Wed, 14 Feb 2018 11:24:00 +0100 [thread overview]
Message-ID: <20180214102400.GA21954@kroah.com> (raw)
In-Reply-To: <CABwYNcVXBFj=pqj2MnbAHKZMHCpA9P=E2XgwSh5wWRTd+rMRmw@mail.gmail.com>
On Wed, Feb 14, 2018 at 03:32:37PM +0530, Shreyasi Rao wrote:
> Hi,
>
> I followed the tutorial upto modifying driver on native linux but when I
> compiled my changes with the make -j2 command it gave me this:
>
> YACC scripts/kconfig/zconf.tab.c
> /bin/sh: 1: bison: not found
You need to install the 'bison' package on your system.
> scripts/Makefile.lib:217: recipe for target 'scripts/kconfig/zconf.tab.c'
> failed
> make[2]: *** [scripts/kconfig/zconf.tab.c] Error 127
> make[2]: *** Waiting for unfinished jobs....
> LEX scripts/kconfig/zconf.lex.c
> /bin/sh: 1: flex: not found
And install 'flex'
> scripts/Makefile.lib:202: recipe for target 'scripts/kconfig/zconf.lex.c'
> failed
> make[2]: *** [scripts/kconfig/zconf.lex.c] Error 127
> Makefile:507: recipe for target 'silentoldconfig' failed
> make[1]: *** [silentoldconfig] Error 2
> make: *** No rule to make target 'include/config/auto.conf', needed by
> 'include/config/kernel.release'. Stop.
> make: *** Waiting for unfinished jobs....
>
> then I installed bison and it didn't make the error go away, now I am
> stuck. If you could please tell me where the problem is.
It doesn't look like bison is installed.
Try just doing a 'make -j1' to ensure that you are seeing the correct
error messages.
thanks,
greg k-h
next prev parent reply other threads:[~2018-02-14 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 10:02 Compile your changes- Tutorial(make -j2) Shreyasi Rao
2018-02-14 10:16 ` [Outreachy kernel] " Julia Lawall
2018-02-14 10:24 ` Greg KH [this message]
2018-02-14 11:19 ` Shreyasi Rao
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=20180214102400.GA21954@kroah.com \
--to=greg@kroah.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=shreyasirao97@gmail.com \
/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.