Hi
I am using yocto Krogoth build for imx6q Sabreauto board.
What is the rate at which data is read from SD card? Can we configure it for
higher speed from Uboot or Kernel
Awaiting your favorable reply
Regards,
Nishina
Confidentiality Statement / Disclaime
On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute wrote:
> Hello list,
>
> I try to compile yocto jethro environment which is working
> on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04.
>
> The compilations stops on gettext-native.
>
> bitbake -k fsl-image-mfgtool-initramfs
>
> make[5]: En
Oliver,
Sorry for stealing your show... Did not want to. :-(
Floor all yours.
Zoran
___
On Wed, Apr 25, 2018 at 10:55 PM, Zoran Stojsavljevic
wrote:
>> Jethro doesn't support Yocto 16.* because it is very old (released
>> 2015...)...
>
> Now, I must admit, I have learned something new. Ne
> Jethro doesn't support Yocto 16.* because it is very old (released 2015...)...
Now, I must admit, I have learned something new. Never gave any
consideration to these releases: example: Pyro 17.0.3.
But now I understand: it has direct link with Ubuntu 17... Even, YOCTO
Pyro, as given example, ca
On 2018-04-25 03:50 PM, Burton, Ross wrote:
Jethro doesn't support Yocto 16.* because it is very old (released
Err, Jethro doesn't support _Ubuntu_ 16.*
(Yocto 16.* is a ways off! :) )
2015, it's been unmaintained for six months now). If you want to use
Jethro despite the known serious securi
Jethro doesn't support Yocto 16.* because it is very old (released
2015, it's been unmaintained for six months now). If you want to use
Jethro despite the known serious security problems then you'll need to
dig out the relevant fixes from the newer releases.
Ross
On 25 April 2018 at 20:36, Olive
On 25/04/18, Zoran Stojsavljevic wrote:
> > I try to compile yocto jethro environment which is working
> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 .
>
> What would be the benefit for the successful compiling of YOCTO Jethro on
> Kubuntu 16.04 over Ubuntu 14.04???
I tried to get
Would like to know if anyone is using rdiff-backup in a yocto system. Does it
work well. (We are using Jethro). Please share any experiences you may have.
Thanks, srini
CONFIDENTIALITY NOTICE: This email message and any attachments are confidential
and may be
> The benefit of the successful compiling of YOCTO Jethro on Kubuntu 16.04
over Ubuntu 14.04 would be the
> full understanding of the yocto system and its interaction with the host
system.
I do buy this argument just for the sole/only one use case: if you try to
become YOCTO distro developer by yo
> I try to compile yocto jethro environment which is working
> on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04 .
What would be the benefit for the successful compiling of YOCTO Jethro on
Kubuntu 16.04 over Ubuntu 14.04???
Zoran
___
On Wed, Apr 25, 2018 at 5:03 PM, Oliver Graute
w
You can specify a set of ptests to be excluded, it will not fail
if some ptest excluded isn't found in the list of execution.
$ ./ptest-runner -e "hang glibc" -d tests/data
Signed-off-by: Aníbal Limón
---
main.c | 38 +++---
utils.h | 1 +
2 files changed, 36 i
Fix usage of relative paths in -d argument.
$ ./ptest-runner -d ./tests/data
Signed-off-by: Aníbal Limón
---
main.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/main.c b/main.c
index 505829c..593aff1 100644
--- a/main.c
+++ b/main.c
@@ -19,6 +19,7 @@
* Aníbal Limó
That file is generated from your kernel's input.h, so I suspect this
is a problem with your kernel. If my hunch is right, building eudev
with MACHINE=qemux86 will work (and if that fails you've found a bug).
Ross
On 25 April 2018 at 16:04, Victor Palacio
wrote:
> Hello,
>
> Building a core-mini
Hello,
After compiling core-image-minimal, bitbake cannot create root filesystem.
...
ERROR: core-image-minimal-1.0-r0 do_rootfs: Index creation command
'/media/vpalacio/LINUX_DEV/morty-imxulevk/build_mx6ul_fslcx11/tmp/sysroots/x86_64-linux/usr/bin/createrepo
--dbpath
/media/vpalacio
Hello,
Building a core-minimal-image, compilation fails at eudev when using gperf.
/media/vpalacio/LINUX_DEV/morty-imxulevk/build_mx6ul_fslcx11/tmp/sysroots/x86_64-linux/usr/bin/gperf
-L ANSI-C -t -N keyboard_lookup_key -H hash_key_name -p -C <
keyboard-keys-from-name.gperf > keyboard-ke
Hello list,
I try to compile yocto jethro environment which is working
on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04.
The compilations stops on gettext-native.
bitbake -k fsl-image-mfgtool-initramfs
make[5]: Entering directory
'/home/us/build-imx6ulevk-mfgtool/tmp/work/x86_64-li
Hi Joshua,
I do now, they're in poky-contrib:ross/gcc8. The commit messages need
rewriting before merging to master.
Ross
On 25 April 2018 at 14:05, Joshua Watt wrote:
> On Wed, 2018-04-25 at 13:11 +0100, Burton, Ross wrote:
>> Hi,
>>
>> Just thought I'd say that GCC 8 is going to start appear
On Wed, 2018-04-25 at 13:11 +0100, Burton, Ross wrote:
> Hi,
>
> Just thought I'd say that GCC 8 is going to start appearing in the
> wild, I believe the first distro to ship with it will be Fedora 28.
> As usual there are changes in behaviour so there are several
> problems.
> So far I've identif
Hi Kévin,
On Wed 2018-04-25 @ 10:46:28 AM, Kévin Carli wrote:
> Hi,
>
> I would like to signal a typo in the
> meta/recipes-extended/tzdata/tzdata/tzdata_2018c.bb
> (https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-extended/
> tzdata/tzdata_2018c.bb?h=morty) file.
>
> At this lin
On 25 April 2018 at 13:18, Uwe Geuder wrote:
> On Wed, Apr 25, 2018 at 1:48 PM, Burton, Ross wrote:
>> So my hunch is that you've a modern system with glibc 2.27 on the
>> host, so that old buildtools won't work. Try this buildtools:
>>
>> http://downloads.yoctoproject.org/releases/yocto/milesto
On 25 April 2018 at 09:59, ChenQi wrote:
> After checking it again, I think removing the '/' would be sufficient.
>
> do_unpack[cleandirs] = "${@d.getVar('S') if d.getVar('S') !=
> d.getVar('WORKDIR') else os.path.join('${S}', 'patches')}"
To protect against this I'm running a test build with thi
On Wed, Apr 25, 2018 at 1:48 PM, Burton, Ross wrote:
> So my hunch is that you've a modern system with glibc 2.27 on the
> host, so that old buildtools won't work. Try this buildtools:
>
> http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.5_M3/buildtools/
Ah, buildtools come wi
Hi,
Just thought I'd say that GCC 8 is going to start appearing in the
wild, I believe the first distro to ship with it will be Fedora 28.
As usual there are changes in behaviour so there are several problems.
So far I've identified the following issues:
* Python 2 crashes on startup
* Kernel too
you can find in the oe-core
openembedded-core/meta/classes/useradd.bbclass and
openembedded-core/meta/classes/useradd_base.bbclass
Thanks!
Prakash
On Tue, Apr 24, 2018 at 4:45 AM, Greg Wilson-Lindberg
wrote:
> I'm trying to understand adding a user in a recipe and in the
> documentation it sa
So my hunch is that you've a modern system with glibc 2.27 on the
host, so that old buildtools won't work. Try this buildtools:
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-2.5_M3/buildtools/
Ross
On 24 April 2018 at 19:04, John Smith wrote:
> bitbake stops with this error
Correcting myself...
On Wed, Apr 25, 2018 at 10:41 AM, Uwe Geuder wrote:
[...]
>
> Bitbake uses Python. To make things more confusing the locales in Python
> are not necessarily named the same way as in your underlying distro and
> there can be aliases.
>
> In the end this code needs to run witho
On 25 April 2018 at 11:00, Burton, Ross wrote:
> Good work Chen, the trailing slash was making me wonder but I didn't
> check. Best normalise both of those paths before comparing.
Yeah, I will make that change and we will see in a couple of days if
still produces any errors.
--
Med Vänliga Häl
Good work Chen, the trailing slash was making me wonder but I didn't
check. Best normalise both of those paths before comparing.
Ross
On 25 April 2018 at 09:59, ChenQi wrote:
> After checking it again, I think removing the '/' would be sufficient.
>
> do_unpack[cleandirs] = "${@d.getVar('S') if
On 25 April 2018 at 10:39, Burton, Ross wrote:
> Is the build tree deleted after it fails? It would be interesting to
> see if the compiler is present in the sysroot, or if it has a
> different name, or something else weird.
Isn't it weird that it does not have a log for "prepare_recipe_sysroot?
After checking it again, I think removing the '/' would be sufficient.
do_unpack[cleandirs] = "${@d.getVar('S') if d.getVar('S') !=
d.getVar('WORKDIR') else os.path.join('${S}', 'patches')}"
Best Regards,
Chen Qi
On 04/25/2018 04:38 PM, Burton, Ross wrote:
Plenty of recipes do that though...
On 25 April 2018 at 10:39, Burton, Ross wrote:
> Is the build tree deleted after it fails? It would be interesting to
> see if the compiler is present in the sysroot, or if it has a
> different name, or something else weird.
I have lost the "state" tinkering around, but before I did that
checked
Hi,
I would like to signal a typo in the
meta/recipes-extended/tzdata/tzdata/tzdata_2018c.bb
(https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-extended/tzdata/tzdata_2018c.bb?h=morty)
file.
At this line: "${datadir}/zoneinfo/Asia/Bankok \"
I think that Bankok shoul
Hello again forum.
I plan using a PR service on different build scenarios (i.e. development,
production).
I think the right way to proceed is running a different PR server instance
listening on a different port for each scenary. So, a PR server instance
listening on port X for development and ano
Is the build tree deleted after it fails? It would be interesting to
see if the compiler is present in the sysroot, or if it has a
different name, or something else weird.
Do you have any global classes that do anything interesting/special?
Ross
On 25 April 2018 at 09:24, Mirza Krak wrote:
> H
Plenty of recipes do that though...
On 25 April 2018 at 09:36, ChenQi wrote:
> I guess the problem is caused by the following line.
>
> S = "${WORKDIR}/"
>
> Try setting it to some dir under ${WORKDIR}, and make sure source file is
> under it.
> Check if the problem is still there after the above
I guess the problem is caused by the following line.
S = "${WORKDIR}/"
Try setting it to some dir under ${WORKDIR}, and make sure source file
is under it.
Check if the problem is still there after the above change.
Best Regards,
Chen Qi
On 04/25/2018 04:24 PM, Mirza Krak wrote:
Hi.
I have
Hi.
I have come across a somewhat strange error that I can not explain to
my self, why it is occurring and hopefully someone on the list can
provide some insight.
I am currently on "rocko" on all my layers and the recipe that I
having issues with is brcm-patchram-plus[1]. And even though this
rec
On Tue, Apr 24, 2018 at 9:04 PM, John Smith :
> bitbake stops with this error message: "Your system needs to support the
> en_US.UTF-8 locale."
>
> export LC_ALL=en_US.UTF-8 has no effect. Do you know how to fix that
> error?
Use "locale -a" to show what locales your system supports at the
moment
38 matches
Mail list logo
