bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: "Clay D. Montgomery" <clay@montgomery1.com>,
	bitbake-devel@lists.openembedded.org
Subject: Re: Can't start menuconfig with Bitbake
Date: Thu, 12 Jul 2018 11:11:35 -0600	[thread overview]
Message-ID: <5cd8d33e-435c-a6ad-9b0a-bd64a23c0fd7@gmail.com> (raw)
In-Reply-To: <5B477CE2.2040602@montgomery1.com>


[-- Attachment #1.1: Type: text/plain, Size: 2402 bytes --]

On 7/12/18 10:08 AM, Clay D. Montgomery wrote:
> Hello,
> 
>    I am having a basic problem with trying to use Bitbake to run
> menuconfig.
> Bitbake otherwise works fine for me. I have done many large builds of
> Yocto.
> 
>  I am running on a Ubuntu 14.04 32-bit system which is up to date, but
> the RAM is limited to 4 GB.
> I have pasted a sample of the errors I get below.  I shortened this
> considerably.
> 
> I would appreciate any advice on how to resolve this.
> 
> Thanks, Clay Montgomery
> 
> 
> 
> bitbake -c menuconfig virtual/kernel
> 
> 
>   GEN     ./Makefile
>   HOSTLD  scripts/kconfig/mconf
> scripts/kconfig/mconf.o: In function `show_help':
> mconf.c:(.text+0x927): undefined reference to `stdscr'
> scripts/kconfig/lxdialog/checklist.o: In function `print_arrows':
> checklist.c:(.text+0x31): undefined reference to `wmove'
> checklist.c:(.text+0x4e): undefined reference to `acs_map'
> checklist.c:(.text+0x5a): undefined reference to `waddch'
> util.c:(.text+0x1826): undefined reference to `keypad'
> util.c:(.text+0x182e): undefined reference to `wgetch'
> util.c:(.text+0x1838): undefined reference to `wgetch'
> menubox.c:(.text+0x11db): undefined reference to `acs_map'
> menubox.c:(.text+0x11eb): undefined reference to `waddch'
> menubox.c:(.text+0x1278): undefined reference to `scrollok'
> scripts/kconfig/lxdialog/menubox.o: In function `do_print_item':
> menubox.c:(.text+0x1ab): undefined reference to `wrefresh'
> scripts/kconfig/lxdialog/menubox.o: In function `print_buttons':
> menubox.c:(.text+0x356): undefined reference to `wrefresh'
> scripts/kconfig/lxdialog/menubox.o: In function `print_arrows.constprop.0':
> menubox.c:(.text+0x478): undefined reference to `wrefresh'
> collect2: error: ld returned 1 exit status
> make[3]: *** [scripts/kconfig/mconf] Error 1
> make[2]: *** [menuconfig] Error 2
> make[1]: *** [sub-make] Error 2
> make: *** [__sub-make] Error 2
> Command failed.
> Press any key to continue...
> 
> 

it means its missing ncurses library and development headers on your
build host. this task should generally depend on ncurses-native as here

meta/classes/cml1.bbclass:do_menuconfig[depends] +=
"ncurses-native:do_populate_sysroot"

I don't know why this is not working in your case. May be another
workaround is to just install ncurses-dev on your build host.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]

  reply	other threads:[~2018-07-12 17:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-12 16:08 Can't start menuconfig with Bitbake Clay D. Montgomery
2018-07-12 17:11 ` Khem Raj [this message]
2018-07-12 22:26   ` Clay D. Montgomery

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=5cd8d33e-435c-a6ad-9b0a-bd64a23c0fd7@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=clay@montgomery1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).