OK, I'll come up with a simple test case + procedure to reproduce it.
Cheers,
Nick
On Wed, Nov 12, 2014 at 1:49 AM, nick xerofo...@gmail.com wrote:
I would state so as if you need it and it doesn't work then it probably is
a bug
with bitbake.
Cheers Nick
On 14-11-11 09:37 AM, Nick D'Ademo
Seems like the best way to report any bug including ones related to YP.
Nick
On 14-11-12 08:12 PM, Nick D'Ademo wrote:
OK, I'll come up with a simple test case + procedure to reproduce it.
Cheers,
Nick
On Wed, Nov 12, 2014 at 1:49 AM, nick xerofo...@gmail.com wrote:
I would state so as
A bit of progress (found the cause of the error at least):
The script that is failing is: linux/scripts/kconfig/lxdialog/
*check-lxdialog.sh*
I added 'set -x' to the script so I could see the output as BitBake
executes it... The function within that script which is failing is *check()
*- in
That was my issue with your build, but I wasn't sure if that was going to
prevent the build from you companies requirements. I would recommend only
making the build 64 bit as it seems that there is no reason for backwards
compatibility with older 32 bit libraries for your build.
Regards Nick
Would this be classified as a BitBake bug then?
I actually have a recipe which requires 32-bit libs - I'll see if there's a
way around it.
Thanks for your help thus far.
Nick
On Wed, Nov 12, 2014 at 1:18 AM, nick xerofo...@gmail.com wrote:
That was my issue with your build, but I wasn't sure
I would state so as if you need it and it doesn't work then it probably is a bug
with bitbake.
Cheers Nick
On 14-11-11 09:37 AM, Nick D'Ademo wrote:
Would this be classified as a BitBake bug then?
I actually have a recipe which requires 32-bit libs - I'll see if there's a
way around it.
Nick,
Yes this is a issue with your custom machine and I believe this is a issue with
your your machine
conf is located in the build directories.
Cheers Nick
On 14-11-10 02:26 AM, Nick D'Ademo wrote:
menuconfig works with a core-image-minimal vanilla build:
If I do the following (from the same Terminal that *oe-init-build-env *has
been run):
1) cd
/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
2) make menuconfig
Menu config loads
On Mon, Nov 10, 2014 at 7:56 AM, Nick D'Ademo nickdad...@gmail.com wrote:
If I do the following (from the same Terminal that oe-init-build-env has
been run):
1) cd
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 =
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
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
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
On 11/09/2014 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
That would make sense and that's why I suggested running oe-init-env in order
to make sure
the path are correct before building.
Cheers Nick
On 14-11-09 08:31 PM, Bob Cochran wrote:
On 11/09/2014 08:15 PM, Nick D'Ademo wrote:
Thanks for the quick reply Nick.
Host system is Ubuntu 14.04.
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
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
Thanks Bob - glad to hear I'm not the first to see this!
Not using the ADT and 'source oe-init-build-env' is run before building.
On Mon, Nov 10, 2014 at 12:31 PM, Bob Cochran yo...@mindchasers.com wrote:
On 11/09/2014 08:15 PM, Nick D'Ademo wrote:
Thanks for the quick reply Nick.
Host
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 xerofo...@gmail.com wrote:
I tried bitbake linux-yocto -c menuconfig on my own system running the
same
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
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 xerofo...@gmail.com wrote:
Seems to after reading and doing some research a build issue with multiple
jobs or try running rm -r tmp in
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
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 xerofo...@gmail.com wrote:
Try downloading a stock kernel for kernel.org and extract it in your home
directory and run make menuconfig in
the
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
menuconfig works with a core-image-minimal vanilla build:
*Build Configuration:BB_VERSION= 1.24.0BUILD_SYS =
x86_64-linuxNATIVELSBSTRING = Ubuntu-14.04TARGET_SYS=
arm-poky-linux-gnueabiMACHINE = qemuarmDISTRO=
pokyDISTRO_VERSION=
25 matches
Mail list logo
