The SDK used to work differently and didn't include its own libc/loader.
In that case, these options were needed to correctly handle the different
library locations. With the modern relocatable SDK, we don't need these
options any more as the default paths in the dynamic loader are good enough.
Th
Hi all - in case folks are starting to make travel arrangements for
ELCE in Berlin this October, we are planning both a YP DevDay (paid
training event) and OEDEM (OpenEmbedded members & developers meeting).
We don't have venues yet, but these two events will likely occur on
the Monday and Friday be
"smart query glibc" or "smart info glibc" will get result as:
"error: 'glibc' matches no packages".
While "smart install glibc" can get result as:
"libc6-xxx (for glibc) is already installed".
Here change "smart query/info" to search package name in Provides too,
and one result example is: "smart q
On 06/22/2016 06:36 AM, Khem Raj wrote:
does this still happen with Qemu 2.6 ?
Yes.
I just did some testing and the problem was still there with qemu2.6.
Regards,
Chen Qi
On Mon, May 30, 2016 at 7:00 PM, ChenQi wrote:
On 05/30/2016 06:48 PM, Alexander Kanavin wrote:
On 05/30/2016 11:02 A
On 06/21/2016 11:42 AM, Martin Jansa wrote:
> xfce4-terminal and toscoterm are broken since vte upgrade in oe-core,
> there is some discussion about re-introducing older version, but no
> patches for meta-oe yet.
>
> poco is pending review which I'll drop from master-next
>
> == Number of issue
While e2fsprogs upgraded to 1.43, it dropped the patch
Revert-mke2fs-enable-the-metadata_csum-and-64bit-fea.patch,
we get it back and rebase for 1.43 to fix invoking grub-probe
failed.
Without the fix:
...
root@localhost:~# mkfs.ext4 /dev/sda3
[skip]
root@localhost:~# grub-probe --target=fs -d /de
does this still happen with Qemu 2.6 ?
On Mon, May 30, 2016 at 7:00 PM, ChenQi wrote:
> On 05/30/2016 06:48 PM, Alexander Kanavin wrote:
>>
>> On 05/30/2016 11:02 AM, Chen Qi wrote:
>>>
>>> Disable gobject-introspection on mips64 to avoid do_compile failure.
>>> +
>>> +# qemu: uncaught target sig
On 21 June 2016 at 17:08, Kucharczyk, Bartlomiej (Nokia - PL/Wroclaw) <
bartlomiej.kucharc...@nokia.com> wrote:
> I have encountered the following issue when trying to add Bash to the SDK
> (meta-toolchain).
> After SDK is installed, bash is not accessible in PATH.
>
Why do you want to install ba
> On Jun 21, 2016, at 9:08 AM, Kucharczyk, Bartlomiej (Nokia - PL/Wroclaw)
> wrote:
>
> Hello!
>
> I have encountered the following issue when trying to add Bash to the SDK
> (meta-toolchain).
> After SDK is installed, bash is not accessible in PATH.
Are you needing bash on sdkhost or on the
Hello!
I have encountered the following issue when trying to add Bash to the SDK
(meta-toolchain).
After SDK is installed, bash is not accessible in PATH.
_Why_
The bash binary is installed in ${base_bindir}, which is not part of PATH
variable in SDK environment script.
_Possible solution_
I c
On Tue, Jun 21, 2016 at 11:48 AM, akuster wrote:
>
>
> On 06/21/2016 08:59 AM, Khem Raj wrote:
>> Can you also see if usermode qemu needs to be changed for ppc64 as well
>
> It has one issue. It wont display input from keyboard. it over runs the
> usb-kbd buffer. This is why I sent this series fir
The impetus for this was that puzzles-extra contains /usr/bin/net which
conflicts with Samba. Hopefully it's not controversial to say that Samba has
priority here, so rename the binary in this recipe to puzzles-net.
Also fix the out-of-tree build problems (just run mkfiles in ${S}) so
autotools-b
xfce4-terminal and toscoterm are broken since vte upgrade in oe-core,
there is some discussion about re-introducing older version, but no
patches for meta-oe yet.
poco is pending review which I'll drop from master-next
== Number of issues - stats ==
{| class='wikitable'
!|Date !!col
On 21 June 2016 at 19:09, srikanth krishnakar wrote:
> I have noticed latest OE core build of sato image fails to build If the
> image is installing "puzzles" and "samba" simultaneously. The below error
> is seen during build of core-image-sato:
>
Sigh... I'll send a quick patch to rename that
Hi All,
I have noticed latest OE core build of sato image fails to build If the
image is installing "puzzles" and "samba" simultaneously. The below error
is seen during build of core-image-sato:
Collected errors:
* check_data_file_clashes: Package puzzles wants to install file
/home/ubuntu/oe/ls
> On Jun 20, 2016, at 7:48 AM, André Draszik wrote:
>
> Hi Khem,
>
> On Mi, 2016-06-15 at 17:20 -0700, Khem Raj wrote:
>> On Fri, Jun 10, 2016 at 8:12 AM, André Draszik wrote:
>>> From: André Draszik
>>>
>>> This doesn't work, as the initial gcc that is used for compiling
>>> uclibc doesn't
On 21 June 2016 at 16:59, Khem Raj wrote:
> Can you also see if usermode qemu needs to be changed for ppc64 as well
>
It needs enabling entirely - qemu-ppc64 doesn't exist currently so every
build-time postinst fails.
Ross
--
___
Openembedded-core mai
Can you also see if usermode qemu needs to be changed for ppc64 as well
On Jun 21, 2016 7:39 AM, "Armin Kuster" wrote:
> This is step 1 in support of Yocto bug 9778
>
> Boot tested on Ubuntu 14.04 (qemu 2.0)
>
> Armin Kuster (3):
> machine: add qemuppc64 machine
> linux-yocto: add qemuppc64
>
This is just an RFC and is only build tested.
When using the multiple u-boot build feature, several directories are created,
one per machine being built. These directories have the same name as its
corresponding defconfig, for example machine_defconfig.
The result is that when a "make machine_def
When building multiple u-boots they get compiled externally into a
directory named after machine defconfigs.
Once there is a directory with the same name as a defconfig it is not
possible to run the defconfig make target.
Signed-off-by: Alex Gonzalez
---
meta/recipes-bsp/u-boot/u-boot.inc | 18
On Tue, Jun 21, 2016 at 11:38 AM, akuster wrote:
>
>
> On 06/21/2016 08:01 AM, Bruce Ashfield wrote:
> > On Tue, Jun 21, 2016 at 10:39 AM, Armin Kuster
> wrote:
> >
> >> From: Armin Kuster
> >>
> >
> > Is this for master ? If so, can you drop the SRCREV updates ? I have an
> > entire series
> >
Backporting the following mainline support for enhanced/improved support
on BXT based platforms.
spi: pxa2xx: Fix too early chipselect deassert
spi: pxa2xx: Update comment in int_transfer_complete()
spi: pxa2xx: Print actual DMA/PIO transfer mode in debug messages
spi: atmel: remove warnin
> What version are you using?
I'm using poky, the latest krogoth branch
> Are you using rm_work?
No rm_work is not used.
>
> Check https://bugzilla.yoctoproject.org/show_bug.cgi?id=9352
I think the issue is relate but not the same. For me the simplest solution i
found was to make sure do_make_sc
Backporting the following mainline commits to make additional sensor
drivers available:
iio: st-accel: add support for lis2dh12
iio: accel: add Freescale MMA7455L/MMA7456L 3-axis accelerometer driver
Signed-off-by: Bruce Ashfield
---
meta/recipes-kernel/linux/linux-yocto-tiny_4.4.bb | 2 +-
Backporting the following pstate changes:
fb0153332a1f intel_pstate: Add SKY-S support
7eb5c7e382a8 intel_pstate: enable HWP per CPU
d73ee41f9786 x86/mm: Decouple from
f447e3d661f7 intel_pstate: Force setting target pstate when required
7db69b864737 intel_pstate: change some inconsiste
Backporting the following changes from the mainline kernel for improved
power, driver core and mmc support:
x86 tsc_msr: Remove irqoff around MSR-based TSC enumeration
x86 tsc_msr: Add Airmont reference clock values
x86 tsc_msr: Correct Silvermont reference clock values
x86 tsc_msr: Update
Backporting the following changes from the mainline kernel to enhance/add
support for tpm2, pinctrl, powercap and watchdog:
634eecdb20b watchdog: omap_wdt: fix null pointer dereference
79dcc6dabe63 Watchdog: Fix parent of watchdog_devices
94a2e8f1d47e watchdog: st_wdt: Update IP layout in
Hi all,
Here's the latest set of changes to the 4.1 and 4.4 linux-yocto
kernel's. Nothing particularly exciting, mainline backports and
minor fixups.
Cheers,
Bruce
The following changes since commit 84cce1d49ddb75025ec454d758fbc8d369920122:
e2fsprogs: remove the extra dot from the recipe fil
first time building a qemu image (qemux86) with an initramfs-based
recipe, core-image-testmaster-initramfs, and i guess i shouldn't have
been surprised to see:
$ runqemu qemux86
Couldn't find a qemux86 rootfs image in
/home/rpjday/oe/builds/testx86/tmp/deploy/images/qemux86.
$
which makes pe
On 21 June 2016 at 17:39, Ross Burton wrote:
> This application needs GTK+ 2 which we're trying to move away from for Sato
> images.
>
> Signed-off-by: Ross Burton
> ---
> meta/lib/oeqa/sdk/buildsudoku.py | 26 --
> 1 file changed, 26 deletions(-)
> delete mode 100644 m
On Tue, Jun 21, 2016 at 10:39 AM, Armin Kuster wrote:
> From: Armin Kuster
>
Is this for master ? If so, can you drop the SRCREV updates ? I have an
entire series
under test that bumps all the versions.
What is listed here, isn't ready to go yet.
Bruce
>
> Signed-off-by: Armin Kuster
> ---
On 06/17/2016 05:10 PM, Richard Purdie wrote:
On Fri, 2016-06-17 at 14:42 -0700, Christopher Larson wrote:
On Fri, Jun 17, 2016 at 8:31 AM, Jolley, Stephen K <
stephen.k.jol...@intel.com> wrote:
·There is a multilib issue related to the layout of the
host libraries leaking into python
On Tue, Jun 21, 2016 at 04:36:32PM +0200, Pascal Bach wrote:
> Hello
>
> I ran into an issue when working with kernel modules that are not part of the
> kernel source tree.
>
> The issue manifests itself as follows:
>
> 1. Build an image containing virtual/kernel and kernel-module-a
>
> 2. Do
This is a GTK+3 application, so we don't need to ship GTK+ 2 in Sato just for
the SDK test suite.
[ YOCTO #9780 ]
Signed-off-by: Ross Burton
---
meta/lib/oeqa/sdk/buildgalculator.py | 23 +++
1 file changed, 23 insertions(+)
create mode 100644 meta/lib/oeqa/sdk/buildgalcula
We added gtk+ to core-image-sato for M1 solely because the SDK self test was
building an application (sudoku) that links to GTK+ 2.
Now that sukoku has been replaced with galculator this workaround can be
removed.
This reverts commit 282d5f7f8573551b94c6b610370db15665cf4bdf.
Signed-off-by: Ross
This application needs GTK+ 2 which we're trying to move away from for Sato
images.
Signed-off-by: Ross Burton
---
meta/lib/oeqa/sdk/buildsudoku.py | 26 --
1 file changed, 26 deletions(-)
delete mode 100644 meta/lib/oeqa/sdk/buildsudoku.py
diff --git a/meta/lib/oeqa/sd
Signed-off-by: Armin Kuster
---
meta/conf/machine/qemuppc64.conf | 13 +
1 file changed, 13 insertions(+)
create mode 100644 meta/conf/machine/qemuppc64.conf
diff --git a/meta/conf/machine/qemuppc64.conf b/meta/conf/machine/qemuppc64.conf
new file mode 100644
index 000..5501101
From: Armin Kuster
Signed-off-by: Armin Kuster
---
meta/recipes-kernel/linux/linux-yocto_4.1.bb | 22 --
meta/recipes-kernel/linux/linux-yocto_4.4.bb | 22 --
2 files changed, 24 insertions(+), 20 deletions(-)
diff --git a/meta/recipes-kernel/linux/linux
From: Armin Kuster
Signed-off-by: Armin Kuster
---
scripts/runqemu | 9 ++---
scripts/runqemu-internal | 24 ++--
2 files changed, 24 insertions(+), 9 deletions(-)
diff --git a/scripts/runqemu b/scripts/runqemu
index de05035..9c73e25 100755
--- a/scripts/runqe
This is step 1 in support of Yocto bug 9778
Boot tested on Ubuntu 14.04 (qemu 2.0)
Armin Kuster (3):
machine: add qemuppc64 machine
linux-yocto: add qemuppc64
runqemu: Add qemuppc64
meta/conf/machine/qemuppc64.conf | 13 +
meta/recipes-kernel/linux/linux-yocto_4.1.
Hello
I ran into an issue when working with kernel modules that are not part of the
kernel source tree.
The issue manifests itself as follows:
1. Build an image containing virtual/kernel and kernel-module-a
2. Do a `bitbake virtual/kernel -c clean`
3. Rebuild the above image again. This cause
Order is not preserved in dict() and this code depends on the order of
these lists of package architectures used when multilibs are enabled.
This caused 'random' breakage where sometimes the correct order was present
and sometimes it wasn't.
Use collections.OrderedDict() to avoid this problem.
K
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/e2fsprogs/{e2fsprogs_1.43..bb => e2fsprogs_1.43.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-devtools/e2fsprogs/{e2fsprogs_1.43..bb =>
e2fsprogs_1.43.bb} (100%)
diff --git a/meta/recipes-devtools/e2fspro
43 matches
Mail list logo