Alexander Kanavin wrote:
> On 10/31/2017 09:04 AM, Craig McQueen wrote:
> > Would the following be a suitable fix? --
>
> This needs to go to oe-core list. Just one comment...
>
> > # Remove python script used to check the WHENCE file
> > - rm ${D}${nonarch_base_libdir}/firmware/ch
Ah, meta-arago sets PACCKAGECONFIG_pn-weston without xwayland.
PACKAGECONFIG_pn-weston = "egl kms launch clients"
On Wed, Nov 1, 2017 at 5:26 PM Adam Lee wrote:
> Hi Raj,
>
> These are my DISTRO_FEATURES:
>
> DISTRO_FEATURES="alsa argp bluetooth ext2 irda largefile pcmcia usbgadget
> usbhost wi
Hi Raj,
These are my DISTRO_FEATURES:
DISTRO_FEATURES="alsa argp bluetooth ext2 irda largefile pcmcia usbgadget
usbhost wifi xattr nfs zeroconf pci 3g nfc *x11 *ipv4 ipv6 libc-backtrace
libc-big-macros libc-bsd libc-cxx-tests libc-catgets libc-charsets
libc-crypt
On Wed, Nov 1, 2017 at 2:03 PM, Adam Lee wrote:
> I believe something is incorrect in my distro level configuration. Apart
> from including x11 and wayland in DISTRO_FEATURES, what else can I check to
> build core-image-weston?
>
> build@6e35408e8fa5:~/tisdk/build$ bitbake core-image-weston
> NOTE
I believe something is incorrect in my distro level configuration. Apart
from including x11 and wayland in DISTRO_FEATURES, what else can I check to
build core-image-weston?
build@6e35408e8fa5:~/tisdk/build$ bitbake core-image-weston
NOTE: Started PRServer with DBfile:
/home/build/tisdk/build/cach
On 1 November 2017 at 17:38, Alan Martinovic
wrote:
> I'm just upgrading to pyro and have some issues with u-boot-fw-utils.
>
> The error fails at do_compile stage which looks like this:
>
> do_compile () {
> oe_runmake ${UBOOT_MACHINE}
> oe_runmake env
> }
>
>
> T
On 1 November 2017 at 17:38, Alan Martinovic
wrote:
> Is there a way to run the above listed make command with the same
> environment as it is run when the error is produced?
>
$ bitbake -c devshell
This drops you in a new terminal with the same environment that bitbake
sets up, and in ../temp
I'm just upgrading to pyro and have some issues with u-boot-fw-utils.
The error fails at do_compile stage which looks like this:
do_compile () {
oe_runmake ${UBOOT_MACHINE}
oe_runmake env
}
The error is:
Log data follows:
| DEBUG: Executing shell function do_com
On 11/01/2017 06:43 PM, colin.helliw...@ln-systems.com wrote:
I need to build two slightly varying versions of our Yocto build – one
for the production units and one for development.
They differ in only a few ways – the kernel and apps are the same. But
one has Dropbear, whilst the other doesn
On 1 November 2017 at 15:58, Adam Lee wrote:
> Thanks Fabien, I definitely don't have Xwayland in my rootfs. My manifest
> is missing xserver-xorg-xwayland as well.
>
> Which image are you using? I thought including of "x11 wayland" was
> sufficient. Perhaps not..?
>
>
Are you refering to DISTRO
I need to build two slightly varying versions of our Yocto build - one for
the production units and one for development.
They differ in only a few ways - the kernel and apps are the same. But one
has Dropbear, whilst the other doesn't; and the U-Boot configs & patches are
different.
I'm wonder
Thank you I will check out core-image-weston.
On Wed, Nov 1, 2017 at 12:01 PM Fabien Lahoudere <
fabien.lahoud...@collabora.co.uk> wrote:
> On Wed, 2017-11-01 at 15:58 +, Adam Lee wrote:
> > Thanks Fabien, I definitely don't have Xwayland in my rootfs. My
> manifest is missing xserver-xorg-
>
On Wed, 2017-11-01 at 15:58 +, Adam Lee wrote:
> Thanks Fabien, I definitely don't have Xwayland in my rootfs. My manifest is
> missing xserver-xorg-
> xwayland as well.
>
> Which image are you using? I thought including of "x11 wayland" was
> sufficient. Perhaps not..?
>
The image I buil
Thanks Fabien, I definitely don't have Xwayland in my rootfs. My manifest
is missing xserver-xorg-xwayland as well.
Which image are you using? I thought including of "x11 wayland" was
sufficient. Perhaps not..?
Adam
On Wed, Nov 1, 2017 at 10:28 AM Fabien Lahoudere <
fabien.lahoud...@collabora.c
On 11/1/2017 12:11 AM, Andre McCurdy wrote:
The fetcher explicitly tries to avoid that by retrying each file only
once. See retry logic in:
http://git.openembedded.org/bitbake/commit/?id=54b1961551511948e0cbd2ac39f19b39b9cee568
However, there is a later commit which may also be related:
On Wed, 2017-11-01 at 14:10 +, Adam Lee wrote:
> Hello, how do I tell if I successfully built xwayland into my image?
>
> I looked for "xwayland" binary but to no avail.
I have this /usr/bin/Xwayland in my rootfs.
Check you manifest. It should contain xserver-xorg-xwayland.
>
> Adam
--
Fa
Hello, how do I tell if I successfully built xwayland into my image?
I looked for "xwayland" binary but to no avail.
Adam
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
On 11/1/17 8:49 AM, Mark Hatle wrote:
> On 11/1/17 4:17 AM, Pavlina Varekova wrote:
>> Hi,
>> thank you very much. It sounds good. So I tried replace fakechroot with
>> pseudo.
>> I read man pages and replace:
>>
>> FAKECHROOT_BASE="${DIR1}" fakechroot command
>>
>> with:
>>
>> %{PATH/TO/PSEUDO/}
On 11/1/17 4:17 AM, Pavlina Varekova wrote:
> Hi,
> thank you very much. It sounds good. So I tried replace fakechroot with
> pseudo.
> I read man pages and replace:
>
> FAKECHROOT_BASE="${DIR1}" fakechroot command
>
> with:
>
> %{PATH/TO/PSEUDO/}bin/pseudo -r "${DIR1}" -P %{PATH/TO/PSEUDO/}
From: André Draszik
It is currently impossible to override localstatedir,
mandir and sysconfdir during ./configure, because they
are being overriden unconditionally.
With this patch it is now possible to set above
locations as needed.
Signed-off-by: André Draszik
---
...-override-localstatedi
From: André Draszik
The combination of using start-stop-daemon and pidof is
not working reliably in all cases. Sometimes, the
tcsd daemon isn't running yet at the time pidof is being
invoked.
This results in an empty /var/run/tcsd.pid, making it
impossible to stop tcsd using the init script.
To
Hi,
thank you very much. It sounds good. So I tried replace fakechroot with
pseudo.
I read man pages and replace:
FAKECHROOT_BASE="${DIR1}" fakechroot command
with:
%{PATH/TO/PSEUDO/}bin/pseudo -r "${DIR1}" -P %{PATH/TO/PSEUDO/} command
But it does not work good. Probably some variable is se
22 matches
Mail list logo
