From: nick <xerofoify@gmail.com>
To: Nick D'Ademo <nickdademo@gmail.com>
Cc: Yocto list discussion <yocto@yoctoproject.org>
Subject: Re: Unable to find the ncurses libraries when running menuconfig
Date: Sun, 09 Nov 2014 22:43:39 -0500 [thread overview]
Message-ID: <5460346B.1080207@gmail.com> (raw)
In-Reply-To: <CANR6C57+VqbBTT1UwE-JNqdaqt4+tg2J9OPqs+u=i-z98NgsOQ@mail.gmail.com>
Nick,
Then this is an issue with your machine conf or paths required for kernel building. Are you able
to build a poky distro with a working kernel and this is just a issue with you building the yocto
kernel alone or can you also not build poky too?
Cheers Nick
On 14-11-09 10:36 PM, Nick D'Ademo wrote:
> Just tried with the latest 3.17.2 kernel. 'make menuconfig' works fine and
> loads the interactive kernel config.
>
>
> On Mon, Nov 10, 2014 at 2:01 PM, nick <xerofoify@gmail.com> wrote:
>
>> Try downloading a stock kernel for kernel.org and extract it in your home
>> directory and run make menuconfig in
>> the root of the kernel source tree, if this works then I am assuming
>> either ncurses or your machine conf is wrong
>> somewhere.
>> Cheers Nick
>>
>> On 14-11-09 09:51 PM, Nick D'Ademo wrote:
>>> Hi Nick,
>>>
>>> I removed build/tmp/ and performed a rebuild - I'm still experiencing the
>>> same error message unfortunately.
>>>
>>>
>>> On Mon, Nov 10, 2014 at 12:58 PM, nick <xerofoify@gmail.com> wrote:
>>>
>>>> Seems to after reading and doing some research a build issue with
>> multiple
>>>> jobs or try running rm -r tmp in your
>>>> build and then rebuild as it may be an issue with out of date temp
>> files.
>>>> Cheers Nick
>>>>
>>>> On 14-11-09 08:51 PM, Nick D'Ademo wrote:
>>>>> Thanks for trying that out Nick.
>>>>>
>>>>> Issue is present on both 3.14 and 3.17 for me.
>>>>> All paths in the require lines are correct too.
>>>>>
>>>>> Any other ideas?
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Nov 10, 2014 at 12:46 PM, nick <xerofoify@gmail.com> wrote:
>>>>>
>>>>>> I tried bitbake linux-yocto -c menuconfig on my own system running the
>>>>>> same distro and it seems to my
>>>>>> default use kernel 3.14 not 3.17 otherwise this seems be fine from my
>>>>>> understanding. Also check all the
>>>>>> paths in your require lines as there may be an issue with your builds
>>>> and
>>>>>> the path set up by these files
>>>>>> that you are linking to for your kernel build.
>>>>>> Nick
>>>>>> On 14-11-09 08:40 PM, Nick D'Ademo wrote:
>>>>>>> Thanks Nick.
>>>>>>>
>>>>>>> Machine conf is as follows (it's actually nearly identical to
>> nuc.conf
>>>> -
>>>>>>> however, BT support, multilib, and preferred providers have been
>>>> added):
>>>>>>>
>>>>>>> #@TYPE: Machine
>>>>>>> #@NAME: chiefriver
>>>>>>>
>>>>>>> #@WEBTITLE: Intel Next Unit of Computing (NUC) Model: DC3217IYE
>>>>>>>
>>>>>>> #@DESCRIPTION: Machine configuration for Intel NUC model DC3217IYE
>>>>>>> # i.e. Ivy Bridge + Panther Point
>>>>>>>
>>>>>>> PREFERRED_VERSION_linux-yocto ?= "3.17%"
>>>>>>> MACHINE_FEATURES += "va-impl-intel wifi efi bluetooth"
>>>>>>> MACHINE_FEATURES += "intel-ucode"
>>>>>>>
>>>>>>> require conf/machine/include/meta-intel.inc
>>>>>>> require conf/machine/include/intel-corei7-64-common.inc
>>>>>>> require conf/machine/include/intel-common-pkgarch.inc
>>>>>>> require multilib.conf
>>>>>>>
>>>>>>> MACHINE_HWCODECS ?= "va-intel gst-va-intel"
>>>>>>>
>>>>>>> XSERVER ?= "${XSERVER_X86_BASE} \
>>>>>>> ${XSERVER_X86_EXT} \
>>>>>>> ${XSERVER_X86_I965} \
>>>>>>> "
>>>>>>>
>>>>>>> MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-iwlwifi-6000g2b-6 lms8"
>>>>>>>
>>>>>>> # disable the serial port configuration
>>>>>>> SERIAL_CONSOLE = ""
>>>>>>>
>>>>>>> PREFERRED_PROVIDER_jpeg = "jpeg"
>>>>>>> PREFERRED_PROVIDER_jpeg-native = "jpeg-native"
>>>>>>> PREFERRED_PROVIDER_virtual/fftw = "fftw"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Nov 10, 2014 at 12:36 PM, nick <xerofoify@gmail.com> wrote:
>>>>>>>
>>>>>>>> Hey Nick,
>>>>>>>> This seems to then be an issue with incorrect paths or build
>>>> information
>>>>>>>> in your nuc.conf
>>>>>>>> as the most likely culprit. If you can post your machine's conf
>> file I
>>>>>>>> will be glad to see
>>>>>>>> if there are any issues I can spot.
>>>>>>>> Nick
>>>>>>>>
>>>>>>>> On 14-11-09 08:33 PM, Nick D'Ademo wrote:
>>>>>>>>> 1) source oe-init-build-env is run before building.
>>>>>>>>> 2) We are actually using a custom machine .conf based on nuc.conf,
>> so
>>>>>>>>> actually: MACHINE = "custom_machine_name". I replaced it with "nuc"
>>>> in
>>>>>>>> this
>>>>>>>>> post to avoid confusion.
>>>>>>>>>
>>>>>>>>> On Mon, Nov 10, 2014 at 12:25 PM, nick <xerofoify@gmail.com>
>> wrote:
>>>>>>>>>
>>>>>>>>>> Do you run source oe-init-build-env before building and why is
>> your
>>>>>>>> machine
>>>>>>>>>> set to nuc seems this may be an issue?
>>>>>>>>>> Nick
>>>>>>>>>>
>>>>>>>>>> On 14-11-09 08:15 PM, Nick D'Ademo wrote:
>>>>>>>>>>> Thanks for the quick reply Nick.
>>>>>>>>>>>
>>>>>>>>>>> Host system is Ubuntu 14.04. ncurses is already installed:
>>>>>>>>>>>
>>>>>>>>>>> sudo apt-get install libncurses5-dev
>>>>>>>>>>> Reading package lists... Done
>>>>>>>>>>> Building dependency tree
>>>>>>>>>>> Reading state information... Done
>>>>>>>>>>> libncurses5-dev is already the newest version.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Nov 10, 2014 at 12:09 PM, nick <xerofoify@gmail.com>
>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Check to see if you actuality have it installed on your host
>>>> system
>>>>>>>> for
>>>>>>>>>>>> your package manager.
>>>>>>>>>>>> The library for ncurses for compiling the kernel is different
>>>> based
>>>>>> on
>>>>>>>>>>>> your distro, check
>>>>>>>>>>>> your distro's installer and install the correct ncurses package
>>>>>> first.
>>>>>>>>>> If
>>>>>>>>>>>> this is still an
>>>>>>>>>>>> issue please reply with a newer error message.
>>>>>>>>>>>> Cheers Nick
>>>>>>>>>>>>
>>>>>>>>>>>> On 14-11-09 08:05 PM, Nick D'Ademo wrote:
>>>>>>>>>>>>> Getting a strange error when attempting to configure the Yocto
>>>>>> Linux
>>>>>>>>>>>> kernel
>>>>>>>>>>>>> via: bitbake linux-yocto -c menuconfig.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Does anyone have any ideas? (error message below)
>>>>>>>>>>>>> Much appreciated.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Build Configuration:
>>>>>>>>>>>>> BB_VERSION = "1.24.0"
>>>>>>>>>>>>> BUILD_SYS = "x86_64-linux"
>>>>>>>>>>>>> NATIVELSBSTRING = "Ubuntu-14.04"
>>>>>>>>>>>>> TARGET_SYS = "x86_64-poky-linux"
>>>>>>>>>>>>> MACHINE = "nuc"
>>>>>>>>>>>>> DISTRO = "poky"
>>>>>>>>>>>>> DISTRO_VERSION = "1.7"
>>>>>>>>>>>>> TUNE_FEATURES = "m64 corei7"
>>>>>>>>>>>>> TARGET_FPU = ""
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> *make[1]: Entering directory
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>> `/home/nick/poky/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto/3.17.1+gitAUTOINC+b86dd5c6f4_0caf16d385-r0/linux-corei7-64-intel-common-standard-build'
>>>>>>>>>>>>> GEN ./Makefile *** Unable to find the ncurses libraries or
>>>> the
>>>>>>>> ***
>>>>>>>>>>>>> required header files. *** 'make menuconfig' requires the
>> ncurses
>>>>>>>>>>>>> libraries. *** *** Install ncurses (ncurses-devel) and try
>>>> again.
>>>>>>>> ***
>>>>>>>>>>>>> make[3]: *** [scripts/kconfig/dochecklxdialog] Error 1make[2]:
>>>> ***
>>>>>>>>>>>>> [menuconfig] Error 2make[1]: *** [sub-make] Error 2make: ***
>>>>>>>>>> [__sub-make]
>>>>>>>>>>>>> Error 2Command failed.Press any key to continue... *
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
next prev parent reply other threads:[~2014-11-10 3:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 1:05 Unable to find the ncurses libraries when running menuconfig Nick D'Ademo
2014-11-10 1:09 ` nick
2014-11-10 1:15 ` Nick D'Ademo
2014-11-10 1:25 ` nick
[not found] ` <CANR6C57voYqR9t-7P-=qUuudn6t7u=PFgGcWTy92xUUOy4H-Kw@mail.gmail.com>
2014-11-10 1:36 ` nick
2014-11-10 1:40 ` Nick D'Ademo
[not found] ` <546018F8.2030201@gmail.com>
2014-11-10 1:51 ` Nick D'Ademo
2014-11-10 1:58 ` nick
2014-11-10 2:51 ` Nick D'Ademo
2014-11-10 3:01 ` nick
2014-11-10 3:36 ` Nick D'Ademo
2014-11-10 3:43 ` nick [this message]
2014-11-10 7:26 ` Nick D'Ademo
2014-11-10 11:11 ` nick
2014-11-10 12:56 ` Nick D'Ademo
2014-11-10 15:10 ` Nick Krause
2014-11-11 11:23 ` Nick D'Ademo
2014-11-11 14:18 ` nick
2014-11-11 14:37 ` Nick D'Ademo
2014-11-11 14:49 ` nick
2014-11-13 1:12 ` Nick D'Ademo
2014-11-13 1:15 ` nick
2014-11-10 1:31 ` Bob Cochran
2014-11-10 1:33 ` nick
2014-11-10 1:42 ` Nick D'Ademo
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=5460346B.1080207@gmail.com \
--to=xerofoify@gmail.com \
--cc=nickdademo@gmail.com \
--cc=yocto@yoctoproject.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.