Hi Trevor,
On Friday, 4 May 2018 3:26:18 PM NZST Trevor Woerner wrote:
> On Wed, May 2, 2018 at 5:19 PM, Paul Eggleton > wrote:
> > 1) If you want the cppzmq development files to be available *within* the
> > eSDK
> > (so you can write code to use them using the eSDK), even if they are not
> > br
On Wed, May 2, 2018 at 5:19 PM, Paul Eggleton wrote:
> 1) If you want the cppzmq development files to be available *within* the
> eSDK
> (so you can write code to use them using the eSDK), even if they are not
> brought in by way of the image containing a package from the cppzmq
> recipe,
> you c
Hi Vincent,
I'd recently gone through similar issue that you're experiencing. The "Waiting
for Removable Media" hang had been there for at least 7-8 years. A workaround
was put in around 2013. See here:
https://patchwork.openembedded.org/patch/42291/
Add "debugshell=30" (30 is in second,
Hello Ross,
Seems that you are correct. I have checked on my host Fedora 27:
[vuser@localhost bin]$ pwd
/usr/bin
[vuser@localhost bin]$ uname -r
4.16.5-200.fc27.x86_64
[vuser@localhost bin]$ ls -al pyth*
lrwxrwxrwx. 1 root root 7 Mar 14 14:36 python -> python2
lrwxrwxrwx. 1 root root 9 Ma
Hi,
We want to deploy image created with Yocto (Rocko) via PXE.
The target board is a Intel-based SBC (AAEON GENE BT05).
At first, we tried with a ISO from Archlinux and the target-board successfully
booted.
Then we create a ISO using Yocto but boot hangs with a message “Waiting for
removable
I suggest you have a look through the feed that you link to and see if it
provides a package which has /usr/bin/python3 in, and if it doesn't then
just make a python3 -> python3.6 symlink (which is all you need).
Ross
On 2 May 2018 at 20:28, Raymond Yeung wrote:
> Thanks Zoran.
>
>
> My Linux b
Thanks Zoran.
My Linux build machine uses Centos 7. I thought I'd done the installation to
Python 3.6.5. If this is not Python3 > 3.4.0, then I'm confused. The link I
follow for installation is here:
https://janikarhunen.fi/how-to-install-python-3-6-1-on-centos-7.html
> python3.6 -V
Pyt
On 05/03/2018 04:37 PM, Peter Kjellerstedt wrote:
# Have dnf always print in verbose mode and print the output to
bb.debug instead of bb.note.
I think this is the best solution actually.
I disagree with changing bb.note to bb.debug for this. It is very good
to be able to look in log.do_rootfs
What is the best way to search for existing driver support (in particular,
driver for TLK10031) in YP? I search my own Poky source and its build tree,
but find nothing. I saw on google returned result mentioning of one instance
for a similar chip (TLK10232), but don't know which branch/repo it
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] On Behalf Of Alexander Kanavin
> Sent: den 3 maj 2018 15:04
> To: Paulo Neves ; Yocto list discussion
>
> Subject: Re: [yocto] ROOTFS_RPM_DEBUG undocumented
>
> On 05/03/2018 01:42 PM, P
On 05/03/2018 01:42 PM, Paulo Neves wrote:
# Add ROOTFS_RPM_DEBUG to the documentation;
I'd rather get rid of it, the less variables the better :)
# Detect if we are running with debug output and enable the debugging
output. This is the most elegant solution but I do not know how to
detect if
Hello all,
I recently had the problem where the do_rootfs task seemed to hang.
The output where it hang looked like [1] and stayed that way for the
better part of an hour.
When I ran bitbake with -vD arguments not more relevant output was
given [2], also hanging for a lot of time.
As noted in an
On 1 May 2018 at 21:43, Raymond Yeung wrote:
> I'd just git cloned Rocko and meta-ti. When I try to source
> oe-init-build-env, I got errors:
>
>
> -bash: python3: command not found
>
> BitBake requires Python 3.4.0 or later as 'python3'. "python -V" gives
> "Python 2.7.9". "python3" is not in
13 matches
Mail list logo
