is this mean I don't need meta-intel anymore? (but still can be found in
the git)
just choose to use meta-dpdk and/or meta-intel-qat
2017-09-28 11:27 GMT+08:00 Saul Wold :
>
> In an effort to create more consistency in Yocto Project layer, we are
> splitting the meta-intel to remove some applicat
I have build a yocto 1.7.1 mohonpeak target, (with sdk)
and tried to build open-iscsi source code
(http://www.open-iscsi.org/bits/open-iscsi-2.0-873.tar.gz )
got error : x86_64-poky-linux/bin/ld: cannot find -lc
is there any library missed in my build?
-
I want to use iscsi initiator on my yocto/mohonpeak target,
so I tried open-iscsi-kernel and iscsi-initiator-utils inside
meta-cloud-servcies
but the iscsid doesnt working on the target,
how to setup a working iscsi initiator for yocto/ i7m64 target?
--
___
got error when compiling binutils with poky 1.7.1 / mohonpeak bsp,
have tried cleanall then build again , but the same result,
looks like a link error, how can I resolve this?
Build Configuration:
BB_VERSION= "1.24.0"
BUILD_SYS = "x86_64-
>
> I can not reproduce this using daisy branch of yocto and opemembeded-core.
> Libtest does not exist in the daisy branch of meta-perl. Can you provide me
> with the Build Configuration when you first start to build and hoe you
> appended nmap to your image
>
> - Armin
>
>
build with yocto 1.6.1 on Ubuntu 12.04,
have add extra dep. to local.conf according to REAME
/poky/openembedded-core/meta \
/poky/meta-openembedded/meta-oe \
/poky/meta-openembedded/meta-perl \
/poky/meta-security \
but got following error message:
$ bitbake -k core-image-full-cmdline
ERR
I want to debug the kernel module loaded in the x86_64 (jasperforest)
linux-yocto target,
so I load the 'vmlinux' with gdb on the host PC (CentOS 6.4_x64) ,
but looks like the gdb failed to connect the target,
should I add any 'kernel boot parameters' to enable the kgdb use ttyS0 ?
my target boot
Thanks Jessica,
why I tried to use "-c populate-sdk" is because that I can find
"core-image-sato-sdk" but no "core-image-basic-sdk" available, and my
hardware is a samll jasperforest x86_64 target with 2 serial port and 1
ethernet port only, no display interface.
I'm trying to find if any of foll
follow the Yocto wiki "Poky NFS Root"
https://wiki.yoctoproject.org/wiki/Poky_NFS_Root
I tried to build the usb image with "EMBEDDED_IMAGE=../chainload.gpxe make
bin/gpxe.usb" but got following error.
my build environment is Yocto 13 + jasperforest BSP on Ubuntu 12.04 x86_64
how can I fix this prob
Thanks Gary,
after download and extract the ti cortex A8 BSP . there's only binary image
inside, what MACHINE to use to build a beagleboard yocto image?
On 2012-12-25 16:31, Lai Eddy wrote:
> in the "Reference Manual "How do I make sure connected network interfaces
> are
in the "Reference Manual "How do I make sure connected network interfaces
are brought up by default?" said 2 files need to be added to enable
network interfaces, where can I find template files?
---
> got errors during "bitbake core-image-minimal" on yacto 1.3 + jasperforest
> BSP
> how can I just clean everything then re-build all?
> since I don't modify any kernel code before make the build, will this
> error caused by build environment settings problem?
> message from
> "tmp/work/x86_64-lin
got errors during "bitbake core-image-minimal" on yacto 1.3 + jasperforest
BSP
how can I just clean everything then re-build all?
since I don't modify any kernel code before make the build, will this error
caused by build environment settings problem?
message from
"tmp/work/x86_64-linux/gettext-nat
Hi,
I’m using yocto 1.3 (poky-8.0) with jasperforest BSP,
sometimes “bitbake core-image-minimal” did create files in
/tmp/work/xxx-poky-linux/linux-yocto-xxx/linux-xxx-standard-build , but
always create new image in /tmp/deploy/image folder (file date time is new)
every “bitbake core-image-minimal
14 matches
Mail list logo