Applied.
Thanks,
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent: Friday, July 18, 2014 12:31 PM
To: Yocto discussion list
Subject: [yocto] [yocto-docs][PATCH] Grammar fix to kernel-dev manual.
Applied.
Thanks,
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Robert P. J. Day
Sent: Thursday, July 10, 2014 8:36 AM
To: Yocto discussion list
Subject: [yocto] [PATCH] Documentation: Ref Manual should use newer
On 21/07/2014 16:39, Anooj Gopi anoojg...@gmail.com wrote:
Hello All,
Could some one help me to understand how we could find the bb file which
generated particular package (rpm package for eg.)?
(In some cases the name of the package and recipe name differ drastically)
Also is there any way
On 21 July 2014 16:39, Anooj Gopi anoojg...@gmail.com wrote:
Could some one help me to understand how we could find the bb file which
generated particular package (rpm package for eg.)?
(In some cases the name of the package and recipe name differ drastically)
Also is there any way to list
Hello Joe,
Here at Enea we are preparing the steps needed for publishing the layer on the
open embedded meta layers initiative:
http://layers.openembedded.org/layerindex/branch/master/layers/
For this we started working at a web page that should contain all the relevant
information regarding
Hello Belen,
Toaster seems promising. But unfortunately I am currently with Yocto
Project 1.5
Do you see any other possibility in 1.5?
Best Regards,
Anooj
On Tue, Jul 22, 2014 at 11:07 AM, Barros Pena, Belen
belen.barros.p...@intel.com wrote:
On 21/07/2014 16:39, Anooj Gopi
Hi,
Is read-only-rootfs supported on systemd setups?
The current dev manual is not clear about this. Also in image.bbclass
there are comments that read_only_rootfs_hook supports only sysvinit
setups.
Thanks,
--
Maciej Borzęcki
Senior Software Developer at Open-RnD Sp. z o.o., Poland
Yes I am trying to track down the recipe from the rpm file. In my project
yocto builds the rpm package
nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm (by
https://github.com/meta-qt5/meta-qt5) but it is not included in my sdk
sysroot image. So I would like to see how I could include this into
A recent patch went in poky master that added command line parsing and options
to the oe-selftest script.
Changing the way oe-selftest is called by the autobuilder to account for these
changes.
Signed-off-by: Corneliu Stoicescu corneliux.stoice...@intel.com
---
i just noticed that, across the two major repos for yocto:
http://layers.openembedded.org/layerindex/branch/master/layers/
http://git.yoctoproject.org/
there's a wee bit of duplication in that the second repo above
duplicates a lot of the meta- layers found in the first location. is
that
On 22 July 2014 14:15, Robert P. J. Day rpj...@crashcourse.ca wrote:
i just noticed that, across the two major repos for yocto:
http://layers.openembedded.org/layerindex/branch/master/layers/
http://git.yoctoproject.org/
there's a wee bit of duplication in that the second repo above
On Tue, 22 Jul 2014, Burton, Ross wrote:
On 22 July 2014 14:15, Robert P. J. Day rpj...@crashcourse.ca wrote:
i just noticed that, across the two major repos for yocto:
http://layers.openembedded.org/layerindex/branch/master/layers/
http://git.yoctoproject.org/
there's a wee bit of
Hi Alex
[RE: [yocto] [OE-core] Carrier Grade layer proposal] On 14.07.22 (Tue 10:52)
Alexandru Vaduva wrote:
Hello Joe,
Here at Enea we are preparing the steps needed for publishing the layer on
the open embedded meta layers initiative:
Hello again,
The P1 compliance until in November is a best effort approach.
Regarding the move to the openembedded.org location, we intend to do that as
soon as possible after
the web page will be put on place, as to make it simple for the community to
interact with the layer and
have all the
A quick follow up to the previous e-mail:
I only mention that P1 compliance is until November is a best effort approach.
This is very much influenced by the community, the available recipes, bugs etc.
The CGL compliance is tested against the qemuppc machine, being the fact that a
real target is
Hi all,
I use the meta-selinux layer to build a core-image-selinux rootfs image, and
build kernel with following options enabled.
CONFIG_AUDIT=y
CONFIG_NETWORK_SECMARK=y
CONFIG_EXT2_FS_SECURITY=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS_SECURITY=y
CONFIG_JFS_SECURITY=y
Hi,
This is a bit obscure. In my testing, for the purpose of upstreaming, of
the glibc change to support ARM TLS descriptors in prelinked binaries (cf
upstream BZ #17078, https://sourceware.org/bugzilla/show_bug.cgi?id=17078)
I have come across a problem where all programs prelinked against
On Tue, Jul 22, 2014 at 4:43 AM, Maciek Borzecki
maciej.borze...@open-rnd.pl wrote:
Is read-only-rootfs supported on systemd setups?
The current dev manual is not clear about this. Also in image.bbclass
there are comments that read_only_rootfs_hook supports only sysvinit
setups.
Not in
Hi Anooj,
I guess you are looking at a wrong version of the recipe file, you have to
look into version number 5.2.1 and revision r1 as your package name is
suggesting but the link which you have mentioned is for 5.3.1 . Kindly,
have a look into correct version number of recipe file and if you do
Christopher,
Thanks for the information. I too have been looking for this.
It seems odd to me that this build system that is designed for an embedded
device, doesn't have this feature by default.
On Tue, Jul 22, 2014 at 10:44 AM, Christopher Larson clar...@kergoth.com
wrote:
On Tue, Jul
Alexandru,
Regarding a few packages in category CD.
I have latest samhain building as well as grsecurity (pax patches
applied against 3.14.12) in a branch in my meta-security tree. I have a
bit more testing to do before I was going to post them.
grsecurity and samhain aren't CGL specific
On 14-07-22 11:54 AM, akuster wrote:
Alexandru,
Regarding a few packages in category CD.
I have latest samhain building as well as grsecurity (pax patches
applied against 3.14.12) in a branch in my meta-security tree. I have a
bit more testing to do before I was going to post them.
And on
Thanks for the patch, I'll get it integrated later today.
(What a nasty problem for such a simple fix.)
--Mark
On 7/22/14, 9:50 AM, Maciej W. Rozycki wrote:
Hi,
This is a bit obscure. In my testing, for the purpose of upstreaming, of
the glibc change to support ARM TLS descriptors in
On 14-07-22 12:02 PM, akuster wrote:
On 07/22/2014 08:58 AM, Bruce Ashfield wrote:
On 14-07-22 11:54 AM, akuster wrote:
Alexandru,
Regarding a few packages in category CD.
I have latest samhain building as well as grsecurity (pax patches
applied against 3.14.12) in a branch in my
On 07/22/2014 08:58 AM, Bruce Ashfield wrote:
On 14-07-22 11:54 AM, akuster wrote:
Alexandru,
Regarding a few packages in category CD.
I have latest samhain building as well as grsecurity (pax patches
applied against 3.14.12) in a branch in my meta-security tree. I have a
bit more testing
Oh sorry the link I sent was wrong. The correct one is
https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/nativesdk-qtbase_5.2.1.bb
Manually searching the bb/inc file did not help until this point.
Now I enabled the build history (INHERIT += buildhistory
BUILDHISTORY_FEATURES = image
OK, thanks for the information and your contribution.
I am not opposing to your suggestion but in the same time I believe that this
recipe should appear in a properly maintained layer, in the case your layer
disappears tomorrow. As you mentioned this information should appear in the
mainline
Glad to hear that Bruce.
On Tuesday, July 22, 2014 7:09 PM, Bruce Ashfield
bruce.ashfi...@windriver.com wrote:
On 14-07-22 12:02 PM, akuster wrote:
On 07/22/2014 08:58 AM, Bruce Ashfield wrote:
On 14-07-22 11:54 AM, akuster wrote:
Alexandru,
Regarding a few packages in category CD.
On 22 July 2014 17:19, Anooj Gopi anoojg...@gmail.com wrote:
But I'm still not able to find out where in yocto PKG variable is configured
(which changes this rpm file name from the default one).
Packages containing libraries get renamed through debian.bbclass.
I'm not sure why you need to know
Hi,
you can find it under .inc file here
https://github.com/meta-qt5/meta-qt5/blob/daisy/recipes-qt/qt5/nativesdk-qtbase.inc
PACKAGES = ${PN}-tools-dbg *${PN}-tools-dev* ${PN}-tools-staticdev ${PN}-tools
Thanks,
Bharath
On Tue, Jul 22, 2014 at 11:19 AM, Anooj Gopi anoojg...@gmail.com wrote:
Hello Bharath,
This is already known to me. The confusion mainly here was because of the
name of the rpm package. From the recipe expected name was
nativesdk-qtbase-tools-dev-5.2.1-r1.i686_nativesdk.rpm but generated
package name is nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm
which
This package (nativesdk-libqt5core-dev-5.2.1-r1.i686_nativesdk.rpm) is not
installed in my sdk sysroot. So I need to add it to TOOLCHAIN_HOST_TASK and
see if it gets installed into my sdk sysroot
But it fails with below error:
Error: nativesdk-qtbase-tools-dev not found in the base feeds
Hello Bruce,
What I understand from your mail you suggest using the already available
linux-yocto tree.
As an answer to this let me assure that as much as possible the meta-cgl layer
will try to do that. If that will not be the case I will let the community know
that.
One such case could be
On 7/22/14, 10:11 AM, zhenhua@freescale.com wrote:
Hi all,
Which release are you using. The last version I used w/ meta-selinux was the
1.5 release.
We're planning on updating it to master in the 'near' future [patches welcome!],
and I've been told by a few others of success w/ 1.7.
I would like to generalize my last question
A yocto PACKAGE, yocto package generates an rpm package, rpm package
with are different names due to an inherited class setting PKG
http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#var-PKG
variable.
When I try to add such a package
On 14-07-22 01:21 PM, Alexandru Vaduva wrote:
Hello Bruce,
What I understand from your mail you suggest using the already available
linux-yocto tree.
As an answer to this let me assure that as much as possible the meta-cgl layer
will try to do that. If that will not be the case I will let the
On wto, 2014-07-22 at 08:44 -0700, Christopher Larson wrote:
On Tue, Jul 22, 2014 at 4:43 AM, Maciek Borzecki
maciej.borze...@open-rnd.pl wrote:
Is read-only-rootfs supported on systemd setups?
The current dev manual is not clear about this. Also in
i know i asked this way back when but i forget the answer -- why
does meta-yocto layer.conf prepend to BBPATH:
BBPATH =. ${LAYERDIR}:
while meta-yocto-bsp appends:
BBPATH .= :${LAYERDIR}
rday
--
Robert P. J. Day
Hi,
Just trying to found what's missing for PAM to work so ssh will stop
exiting with Broken pipe? Quick fix to solve ssh broken pipe is to
change in /etc/ssh/sshd_config UsePAM yes to UsePAM no. But this
does not remove my PAM error?
Here the log for PAM:
root@ka:~$ journalctl | grep -i PAM
Hi Mark,
Thanks for your comments.
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Mark Hatle
On 7/22/14, 10:11 AM, zhenhua@freescale.com wrote:
Hi all,
Which release are you using.
[Luo Zhenhua-B19537] I
The first milestone for the upcoming 1.7 release is now available at:
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-1.7_M1
poky a5531a2b8983318b99c119a87b78a92cf84160b8
meta-qt3 3016129d90b7ac8517a5227d819f10ad417b5b45
eclipse-poky-juno
Good day,
I have bumped into a problem when compiling from my generated SDK (-c
populate_sdk). I have archive libraries (.a) that were not reflected in my
SDK's lib dir in sysroots. However, my shared objects (.so) are present. I
needed both .a and .so to be present in my SDK. With the former
http://autobuilder.yoctoproject.org/pub/nightly/20140722-2 Unknown
bitbake 8fbffd25d42f1f2d9a85ae1d9cc4852e835730d4
eclipse-poky-juno 26bfc407781aa185f244a47ba63120343cee4a37
eclipse-poky-kepler 4a167fd662262ebdaa3cf0d332ac0debb52d7904
meta-fsl-arm d900d935e1f45a79c7116c4fd290baaa447a870d
meta
On 14-07-19 09:37 AM, Kevin Hao wrote:
From: Kevin Hao haoke...@gmail.com
Ack'd. I'll apply this shortly, I'm just sorting out some 3.16 issues
first.
Bruce
commit 1871ee134b73fb4cadab75752a7152ed2813c751 from
git://git.kernel.org/pub/scm/linux/kernel/git/tj/libata.git
The sata on fsl
Add a new config fragment enabling Industrial IO (IIO) and all the non-staging
drivers. Add this to the intel-common-standard.
Please apply to 3.14 and -dev.
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
Add a new IIO feature / config fragment which enables all the
non-staging IIO drivers as modules. I didn't bother separating these out
by class as there weren't too many of them and it's far more likely
people would select one of each class (accelerometer, adc, etc.) rather
than all of one class
Include the IIO fragment in all intel-common standard kernel
configurations.
Signed-off-by: Darren Hart dvh...@linux.intel.com
---
meta/cfg/kernel-cache/bsp/intel-common/intel-common-standard.scc | 3 +++
1 file changed, 3 insertions(+)
diff --git
Hi Darren,
Nice!
There's a typo in line 1 of iio.scc:
define KFEATURE_DESCRIPTION Enable support for Industrail IO
should be Industrial, I believe.
-mehaf
-Original Message-
From: linux-yocto-boun...@yoctoproject.org
[mailto:linux-yocto-boun...@yoctoproject.org] On Behalf Of Darren
Ah thanks John. I'll resend since I believe Bruce is MIA for a couple
hours right about now.
On 7/22/14, 14:31, Mehaffey, John john_mehaf...@mentor.com wrote:
Hi Darren,
Nice!
There's a typo in line 1 of iio.scc:
define KFEATURE_DESCRIPTION Enable support for Industrail IO
should be
Add a new config fragment enabling Industrial IO (IIO) and all the non-staging
drivers. Add this to the intel-common-standard.
Please apply to 3.14 and -dev.
v2: Correct typo in iio.scc
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
Include the IIO fragment in all intel-common standard kernel
configurations.
Signed-off-by: Darren Hart dvh...@linux.intel.com
---
meta/cfg/kernel-cache/bsp/intel-common/intel-common-standard.scc | 3 +++
1 file changed, 3 insertions(+)
diff --git
Add a new IIO feature / config fragment which enables all the
non-staging IIO drivers as modules. I didn't bother separating these out
by class as there weren't too many of them and it's far more likely
people would select one of each class (accelerometer, adc, etc.) rather
than all of one class
52 matches
Mail list logo
