Hello all,
I have the latest wireshark 1.12.0-rc2 building and working with gtk2.
Is anyone else working on this? if not I can submit patches.
I am not sure which layer wireshark should swim in, meta-networking or
meta-security ?
- Armin
--
___
y
[[meta-selinux][PATCH] swig: use pkg-config for pcre detection.] On 14.07.15
(Tue 22:03) Joe MacDonald wrote:
> Adapted from the original patch submitted to meta-oe for swig 2.0.12.
>
>OE-core commit 5870bd272b0b077d0826fb900b251884c1c05061 sabotaged the
>binconfig way.
>
> Signed-off-b
Adapted from the original patch submitted to meta-oe for swig 2.0.12.
OE-core commit 5870bd272b0b077d0826fb900b251884c1c05061 sabotaged the
binconfig way.
Signed-off-by: Koen Kooi
Signed-off-by: Joe MacDonald
---
Building swig-native has been broken for about the last month, the medium-t
On Mon, Jul 14, 2014 at 8:53 AM, jags gediya wrote:
> Exception: OSError: [Errno 13] Permission denied
>
> ERROR: Function failed: do_rootfs
> ERROR: Logfile of failure stored in:
> /home/jags/Projects/asai_iotg/asai_iotg/src/build/tmp/work/imx6slevk-poky-linux-gnueabi/core-image-minimal/1.0-r0/te
On Jul 15, 2014 6:08 AM, "atulkumar singh" wrote:
>
> Hi All,
>
> Please let me know what I need to be updated for SDKMACHINE, when I am
building meta-toolchain with MACHINE as “qemux86-64” in local.conf
nothing else unless you want to run sdk on different (64bit) host
>
> For qemux86, we are men
On Jul 15, 2014 3:30 AM, "zhenhua@freescale.com" <
zhenhua@freescale.com> wrote:
>
> Hi all,
>
> The git tree of several kernel version is maintained in the Yocto
official git repository, 3.4, 3,8, 3.10 and 3.14, is there any reason to
skip kernel 3.12 which is a LTS version?
usually lates
On Jul 15, 2014 6:17 AM, "Stoicescu, CorneliuX" <
corneliux.stoice...@intel.com> wrote:
>
> Hello,
>
> Here is the documentation for the test-remote-image script. This was one
of the resulted changes derived from feature
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6254 .
>
> If you think more
On Jul 15, 2014 8:19 AM, "Bharath Chandra"
wrote:
>
> Hi,
>
> I would like to analyze the startup process of gumstix board. What
happens when we boot a gumstix board, for eg: first the MLO will be called
and then it will call u-boot.img I would like to know what does MLO do
and functionalities
On 7/15/14, 12:29 PM, Flanagan, Elizabeth wrote:
On Tue, Jul 15, 2014 at 9:53 AM, Mark Hatle wrote:
I think the YP 1.7 build tags are missing in the Poky repository.
It looks to me (based on the test reports) that the following tags should be
created:
We've actually stopped doing rc build ta
On Tue, Jul 15, 2014 at 9:53 AM, Mark Hatle wrote:
> I think the YP 1.7 build tags are missing in the Poky repository.
>
> It looks to me (based on the test reports) that the following tags should be
> created:
We've actually stopped doing rc build tags as of 1.6_M2, as there were
community compl
I think the YP 1.7 build tags are missing in the Poky repository.
It looks to me (based on the test reports) that the following tags should be
created:
1.7_M1.rc1: 68824d9b8f6e290da078383316b3f4b732585f2b
1.7_M1.rc2: a5531a2b8983318b99c119a87b78a92cf84160b8
--Mark
--
_
Hi,
I would like to analyze the startup process of gumstix board. What happens
when we boot a gumstix board, for eg: first the MLO will be called and then
it will call u-boot.img I would like to know what does MLO do and
functionalities of other files. Can anyone of you provide any pointer whe
Attendees: Bruce, Armin, Jefro, Stephen, Alex V., Matthew, Michael, Tom Z,
Denys, Zhenhua, Belen, Richard, Saul, Ross, Alex D., Nitin,
* Opens collection - 5 min (Stephen)
* Yocto 1.7 status - 5 min (Stephen/team)
https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.7_Status
https://wiki.yoc
On 15 July 2014 14:30, Daniel BORNAZ wrote:
> +++ b/meta/recipes-devtools/qemu/files/pcie_better_hotplug_support.patch
> @@ -0,0 +1,74 @@
> +The current code is broken: it does surprise removal which crashes guests.
> +
> +Reimplemented the steps:
> + - Hotplug triggers both 'present detect change
Qemu PCIe bus support is vulnerable to a use-after-free flaw. It could
occur via guest, when it tries to hotplug/hotunplug devices on the
guest.
A user able to add & delete Virtio block devices on a guest could use
this flaw to crash the Qemu instance resulting in DoS.
Originated-by: Marcel Apfel
Hello,
Here is the documentation for the test-remote-image script. This was one of the
resulted changes derived from feature
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6254 .
If you think more documentation is needed, please reply so I can add to the
wiki :)
Regards,
Corneliu
Yocto QA
On 14-07-15 06:14 AM, zhenhua@freescale.com wrote:
Hi all,
The git tree of several kernel version is maintained in the Yocto official git
repository, 3.4, 3,8, 3.10 and 3.14, is there any reason to skip kernel 3.12
which is a LTS version?
What's the policy of kernel selection of kernel th
Hi All,
Please let me know what I need to be updated for SDKMACHINE, when I am
building meta-toolchain with MACHINE as “qemux86-64” in local.conf
For qemux86, we are mentioning it as SDKMACHINE ?= "i686-mingw32".
Thanks and Regards,
ATUL KUMAR SINGH
--
_
Hi all,
The git tree of several kernel version is maintained in the Yocto official git
repository, 3.4, 3,8, 3.10 and 3.14, is there any reason to skip kernel 3.12
which is a LTS version?
What's the policy of kernel selection of kernel that is supported by Yocto?
Best Regards,
Zhenhua
--
Remove PR, since oe-core has a new version.
Signed-off-by: Chong Lu
---
recipes-support/gnupg/gnupg_2.%.bbappend |2 --
1 file changed, 2 deletions(-)
diff --git a/recipes-support/gnupg/gnupg_2.%.bbappend
b/recipes-support/gnupg/gnupg_2.%.bbappend
index 945..12571b4 100644
--- a/recipe
Remove PR, since oe-core has a new version.
Signed-off-by: Chong Lu
---
recipes-devtools/rpm/rpm_5.4.14.bbappend |2 --
1 file changed, 2 deletions(-)
diff --git a/recipes-devtools/rpm/rpm_5.4.14.bbappend
b/recipes-devtools/rpm/rpm_5.4.14.bbappend
index f2a82e1..df5dcef 100644
--- a/recipe
21 matches
Mail list logo
