Greetings,
What is the minimal image from the poky yocto recipes that has ssh enabled by
default or is it just better to enable it in the core minimal image on system
startup.
Thanks,
Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https
is called smp.cfg and this the file's content:
#Disable SMP
CONFIG_SMP=n
This is my bbappend called linux-yocto-4.1.8.bbappend:
# Include kernel configuration fragment
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URL += "file://smp.cfg"
If anyone has ideas than
Greetings All,
What is the best way to put a image on the 8mb of Yocto onboard flash or is
this not possible with the Yocto Project.
Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_Bugs
>
>
>
> Thanks,
>
>
>
> Stephen K. Jolley
>
> Yocto Project Program Manager
>
> INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
>
> *Cell: (
in the layer's folder:
ERROR: hello-1.0-r0 do_package_qa: QA Issue: No GNU_HASH in the elf binary:
'/home/nick/poky/build/tmp/work/i586-poky-linux/hello/1.0-r0/packages-split/hello/usr/bin/hello'
[ldflags]
WARNING: hello-1.0-r0 do_package_qa: QA Issue: hello rdepends on glibc, but it
isn't a build depen
Greetings All,
I am wondering why this error is occuring:
yocto-layer: command not found
as I already sourced into my build with oe-init script and therefore add
wondering why it's not found. I checked the current developer manual and
that should work cleanly.
Thanks,
Nick
rm -rf ${WORKDIR}/${P}
rm -f ${TMPDIR}/stamps/*
}
addtask clean
And am working why this error is occuring:
ERROR: ParseError at /tmp/bbhello/meta-hello/recipes-editor/nano/nano.bb:15:
unparsed line: 'LIC_FILES_CHKSUM =
"${SITE}/v${PV_MAJOR}.${PV_MINOR}/COPYING;md5=f27defe1e96c2e1ecd4e0c9be8967949'
I
bitbake show package size can be very useful for trimming down
your
packages before the build is done or even before debugging storage
requirements. It
should also support telling what shared libraries are used by each package.
Nick
--
___
yocto
bitbake builds on. How do I do that?
I've read the documentation:
http://www.yoctoproject.org/docs/latest/toaster-manual/toaster-manual.html, but
can't seem to find the answer there.
Cheers,
Nick
Toaster User Manual - Yocto
Project<http://www.yoctoproject.org/docs/latest/toaster-manual/toas
ages could not be configured offline and rootfs is
read-only: ['mozroot-certdata']
My question is: is their a way to get these mozroot certs installed and
configured with mono during the build process, such that the root file system
does not need to be modified at boot/run time?
Che
If people are interested in my input I would be glad to share
it.
Nick
> 2016-09-02 18:00 GMT-03:00 nick <xerofo...@gmail.com>:
>> Greetings All,
>> I am interested in helping out here. In addition I do have some experience
>> with the project
>> so just givi
Greetings All,
I am interested in helping out here. In addition I do have some experience with
the project
so just giving me a heads up on where to start or what is the current focus
would be great.
Nick
--
___
yocto mailing list
yocto
And list of tags can be found here:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/refs/tags
Nick Pongratz
Singlewire Software
On Tue, May 3, 2016 at 10:32 AM, Christopher Larson <clar...@kergoth.com>
wrote:
>
> On Tue, May 3, 2016 at 3:31 PM, Mark T <mtl1nux...@gmail.com&
nfigured to make iso/vmware images as I find this very useful
plus from what
I known Toaster needs to be run with a browser can it be made to run as a non
browser based
service similar to Hob if not already done so.
Just my thoughts,
Nick
P.S. Sorry if anybody gets a second email as I was not subscribed to
openembedded architecture.
>> Cheers,
>> Paul
>>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
nfigured to make iso/vmware images as I find this very useful
plus from what
I known Toaster needs to be run with a browser can it be made to run as a non
browser based
service similar to Hob if not already done so.
Just my thoughts,
Nick
>> Cheers,
>> Paul
>>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On Thursday 11 Feb 2016 14:32:50 Burton, Ross wrote:
> On 11 February 2016 at 14:21, Nick Leverton <n...@leverton.org> wrote:
> > Possibly a little early - Debian 7 will be going onto LTS security support
> > for
> > two years, starting some time this mon
On Thursday 11 Feb 2016 14:32:50 Burton, Ross wrote:
> On 11 February 2016 at 14:21, Nick Leverton <n...@leverton.org> wrote:
> > Possibly a little early - Debian 7 will be going onto LTS security support
> > for
> > two years, starting some time this mon
starting some time this month. Quoting from
https://wiki.debian.org/LTS
"Debian 6 “Squeeze” until February 2016
Debian 7 “Wheezy” from February 2016 to May 2018
Debian 8 “Jessie“ from May 2018 to April/May 2020"
Nick
--
___
yocto m
ntk in kernel and see if you actually reach the kernel
initialization
routines I am not sure if ARM supported early printk but it should for printing
before serial
console is completely initialized. This would allow me/you to see if the kernel
actually starts
and whether u-boot or the ker
a error in my opinion.
Cheers,
Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
is for one of two reasons in my
experience either
it's on custom hardware and written by a vendor supporting that hardware or
people want to
run a long term supported kernel. I am wondering of the two which one are you
under Parthiban.
Nick
--
___
yocto
for elfutils as I am pretty
certain that you can put your gcc compiler flags to work around this
issue inside
that particular bitbake recipe file.
Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
or think
of some way to allow me to known what happened during the meeting.
Thanks,
Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Simon,
Your right is this probably an issue with your boot partition config.
Regards Nick
On 2015-01-09 04:20 AM, Simon Bolek wrote:
Hi Nick, attached is my kernel .bbappend and .cfg files of linux kernel
recipe of my own layer. In original meta layer nothing was changed.
However, I spent
Simon,
Please send me your kernel bb recipes as there is probably an issue in
them.
Regards,
Nick
On 2015-01-08 03:58 PM, Simon Bolek wrote:
NIck, thank you. what do you mean by that? I followed the instructions from
here:
http://www.yoctoproject.org/docs/1.7/kernel-dev/kernel-dev.html
Simon,
Why are you not linking your kernels to the core-image-sato build.
This seems to be the issue.
Regards Nick
On 2015-01-08 05:59 AM, Simon Bolek wrote:
Thank you Nick. I will try that, but this is not the point. I am trying to
figure out why
*bitbake core-image-sato *
does not create
it.
Cheers Nick
On 2014-12-28 09:23 PM, ChenQi wrote:
Hi Schwab,
What do you mean by distro recipe?
I can see your initial problem is that you want different config details for
the same image recipe (maybe for different HW, I guess?).
Now we would like to create an installer image, i.e
Boris,
I am thinking of at least 32 cores or 2 e5 xeons and 64 GB of ram.
Is this enough or should I accept for even more CPU cores?
Nick
On 2014-12-22 03:07 PM, Burton, Ross wrote:
On 22 December 2014 at 18:41, nick xerofo...@gmail.com wrote:
I am wondering if a build server is a good idea
as much ram as possible
too, 64 GB as a minimum.
If there are any other ideas on specs for a build server that would be greatly
appreciated.
Regards Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
get a bug report opened.
Thanks!
Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
pulled from meta-custom.
Is there something I'm missing, like some sort of decreased priorty for
bbappend files with a wildcard? Or is this a bug?
Thanks for any help!
Nick Stevens
--
___
yocto mailing list
yocto@yoctoproject.org
https
Have you read the yocto docs on ADT for building correctly your development kit,
seems to me rather trivial error in either your build or bitbake
recipe for hello world.
Cheers Nick
On Thu, Nov 13, 2014 at 4:43 AM, neil...@emerson.com wrote:
Hi all :
I have installed
loader in order
to instruct the kernel
how to boot your respected device.
Cheers Nick
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Hey Jim,
I had a stressful day with other things so I would like some time to unwind but
I will try and help out
later if that's OK.
Nick
On 14-11-13 03:13 PM, Jim Rafert wrote:
Hi folks,
I'm trying to put together a recipe to include llvm and clang in the yocto
toolchain. My goal
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
()
*- in particular the following is failing:
*$cc -x c - -o $tmp 2/dev/null 'EOF'#include CURSES_LOCmain() {}EOF*
*Script output:*
*gcc -isystem/home/nick/poky/build/tmp/sysroots/x86_64-linux/usr/include
-O2 -pipe -L/home/nick/poky/build/tmp/sysroots/x86_64-linux/usr/lib
-L/home/nick/poky/build/tmp
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
I am too interesting in helping out Yocto but more with kernel work on Yocto rt
and
standard kernel recipes. If someone would like to point me in the right
direction to
aid in helping out in this area of the Yocto project that would be very helpful.
Thanks Nick
On 14-11-11 10:46 AM, John
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
/home/nick/poky/build/tmp/work/corei7-64-intel-common-poky-linux/linux-yocto/3.17.1+gitAUTOINC+b86dd5c6f4_0caf16d385-r0/linux
John,
Hob is not meant to be like Suse Studios. Further more you are right about the
interface sucking
hard for certain things, I would recommend you start cleaning that up first and
then afterwards
move on to other areas of interest with YP.
Cheers Nick
On 14-11-10 06:58 PM, John Unland
-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
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
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 libncurses5
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 oe-init
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
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
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
machine.
On Mon, Nov 10, 2014 at 2:43 PM, nick xerofo...@gmail.com wrote:
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
library implementation as static versions of
Busybox can easily be less then 10
megabytes from my reading and experience.
Regards Nick
On 14-11-08 01:03 PM, Diego Sueiro wrote:
Take a look at poky-tiny distro:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/distro/poky
That's fine Samuel,
I haven't the time to see if it works not due to being busy with school and
kernel programming.
Cheers Nick
On 14-11-05 07:52 AM, Samuel Stirtzel wrote:
2014-10-31 19:41 GMT+01:00 nick xerofo...@gmail.com:
Thanks Sven,
I will git pull later and see if it's up again just
I am getting a failing build with the log below. If anyone knows how to fix
this it would be very helpful.
Cheers Nick
nick@nick-System-Product-Name:/media/nick/Build_Drive/setup-scripts$ time
MACHINE=beagleboard ./oebb.sh bitbake systemd-gnome-image
Using environment-angstrom-v2013.12 to setup
This isn't a network issue as I can fetch Yocto sources from other servers
without
any problems.
Cheers Nick
On 14-11-01 04:54 PM, Paul Eggleton wrote:
On Saturday 01 November 2014 19:55:47 Sven Ebenfeld wrote:
Looks like problems with gitorious.org again.
You should either find a mirror
Greetings,
I am getting a failing build after cloning the angstrom build scripts. My build
log is pasted below.
Cheers Nick
nick@nick-System-Product-Name:/media/nick/Build_Drive/setup-scripts$
MACHINE=beaglebone ./oebb.sh update
Processing bitbake: Current branch 1.20 is up to date.
Processing
Thanks Sven,
I will git pull later and see if it's up again just wasn't sure if this was
a network error or a misconfiguration on my part.
Cheers Nick
On 14-10-31 02:29 PM, Sven Ebenfeld wrote:
It looks like meta-kde on gitorious is currently down. Manually cloning its
mirror on github
I tried that and it didn't work.
Cheers Nick
On 14-10-24 04:34 AM, Richard Purdie wrote:
On Thu, 2014-10-23 at 22:46 -0400, nick wrote:
Greetings Fellow Yocto Developers and Users,
I am getting a failing build with bitbake core-image-rt-sdk on qemux86 or
qemux86_64 machine builds.
I'm
Thanks Ross,
Sorry about not reading the manual first, I thought it was a misconfiguration
but wasn't sure.
Cheers Nick
On 14-10-24 07:14 AM, Burton, Ross wrote:
On 24 October 2014 12:12, Burton, Ross ross.bur...@intel.com wrote:
On 24 October 2014 12:00, Mihail, StanciuX stanciux.mih
.
Cheers and Thanks for the Help,
Nick
/media/nick/Build_Drive/poky/build/tmp/sysroots/qemux86/usr/src/kernel/lib/cordic.c
Matched in manifest-qemux86-linux-yocto.populate_sysroot
/media/nick/Build_Drive/poky/build/tmp/sysroots/qemux86/usr/src/kernel/lib/cpu-notifier-error-inject.c
Matched
I am wondering from your experience how long is the largest build you have ever
seen and what was it building. I am
considering a high powered build system for Yocto and want to known about build
times in order to help me with
purchasing decisions.
Cheers Nick
Thanks Chris,
I was wondering if a i7 was worth it seems it is and yes for the matter, I did
have issues with the kernel
community and trying to work then out.
Nick
On 14-10-22 03:59 PM, Chris Tapp wrote:
On 20 Oct 2014, at 21:44, nick xerofo...@gmail.com wrote:
I am wondering from your
-- Forwarded message --
From: Nick D'Ademo nickdad...@gmail.com
Date: Wed, May 7, 2014 at 8:26 AM
Subject: Re: [meta-security][PATCH] nmap: inherit autotools-brokensep to
allow B=S build.
To: Yocto list discussion yocto@yoctoproject.org
This is a resubmission - added required
---
recipes-security/nmap/nmap_6.25.bb |5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/recipes-security/nmap/nmap_6.25.bb
b/recipes-security/nmap/nmap_6.25.bb
index aff5c63..0c70fd3 100644
--- a/recipes-security/nmap/nmap_6.25.bb
+++
---
recipes-security/nmap/nmap_6.25.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/nmap/nmap_6.25.bb
b/recipes-security/nmap/nmap_6.25.bb
index aff5c63..5efcc70 100644
--- a/recipes-security/nmap/nmap_6.25.bb
+++ b/recipes-security/nmap/nmap_6.25.bb
@@
Signed-off-by: Nick D'Ademo nickdad...@gmail.com
---
recipes-security/nmap/nmap_6.25.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/nmap/nmap_6.25.bb
b/recipes-security/nmap/nmap_6.25.bb
index aff5c63..5efcc70 100644
--- a/recipes-security/nmap
This is a resubmission - added required blank line between subject and SOB.
On Wed, May 7, 2014 at 8:24 AM, Nick D'Ademo nickdad...@gmail.com wrote:
Signed-off-by: Nick D'Ademo nickdad...@gmail.com
---
recipes-security/nmap/nmap_6.25.bb |2 +-
1 file changed, 1 insertion(+), 1 deletion
Forwarded to Yocto List
-- Forwarded message --
From: Nick D'Ademo nickdad...@gmail.com
Date: Sun, Jan 12, 2014 at 3:32 PM
Subject: autogen-native recipe compilation error (since upgrade to 5.18.2)
To: p...@yoctoproject.org
Cc: liezhi.y...@windriver.com, richard.pur
,
Nick
On Wed, Jan 8, 2014 at 12:24 AM, Nicolas Dechesne
nicolas.deche...@linaro.org wrote:
On Tue, Jan 7, 2014 at 2:19 PM, Nick D'Ademo nickdad...@gmail.com wrote:
Can't seem to get the build process to create a EXT4 filesystem - I've
tried the following:
in general, more details about
to do this?
Many thanks.
Nick
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
: Logfile
of failure stored in:
/home/nick/poky/test/tmp/work/x86_64-poky-linux/x264/r2265+gitAUTOINC+585324fee3-r0/temp/log.do_package.11458ERROR:
Task 4913 (/home/nick/poky/meta/recipes-multimedia/x264/x264_git.bb
http://x264_git.bb, do_package) failed with exit code '1' ERROR: Function
failed
variable
As you can see from the above fixes, the issue was that the configure step
was passing usr/lib instead of usr/lib64 which ultimately caused the
installed but not shipped errors.
Are these actually bugs which should be patched in the recipes?
Nick
On Sun, Nov 24, 2013 at 8:53 PM, Nick
MULTILIBS = multilib:lib32
DEFAULTTUNE_virtclass-multilib-lib32 = x86
However, running BitBake with the above added to local.conf results in a
large number of build errors. To name a few:
grub_2.0.0.bb:
...
| checking whether the C compiler works... no
| configure: error: in
`/home/nick/poky
What is the latest combination of Yocto/Pocky that supports 3.2? I
noticed that 3.4 is the minimum supported in the latest.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
83 matches
Mail list logo
