* in some cases we might set QB_DEFAULT_KERNEL to the real filename
instead of symlink and then this whole readlink work around actually
breaks the build, because os.readlink fails on normal files:
>>>
os.readlink('deploy/images/qemux86/bzImage-linux-yocto-qemux86-master-20160927084848.bin'
On 09/28/2016 03:03 PM, Martin Jansa wrote:
* in some cases we might set QB_DEFAULT_KERNEL to the real filename
instead of symlink and then this whole readlink work around actually
breaks the build, because os.readlink fails on normal files:
>>>
os.readlink('deploy/images/qemux86/bzImag
* in some cases we might set QB_DEFAULT_KERNEL to the real filename
instead of symlink and then this whole readlink work around actually
breaks the build, because os.readlink fails on normal files:
>>>
os.readlink('deploy/images/qemux86/bzImage-linux-yocto-qemux86-master-20160927084848.bin'
* in some cases we might set QB_DEFAULT_KERNEL to the real filename
instead of symlink and then this whole readlink work around actually
breaks the build, because os.readlink fails on normal files:
>>>
os.readlink('deploy/images/qemux86/bzImage-linux-yocto-qemux86-master-20160927084848.bin'
With the change of crosssdk to use SDK_SYS, we need to update the script
to match.
Signed-off-by: Richard Purdie
diff --git a/scripts/cleanup-workdir b/scripts/cleanup-workdir
index 86eae37..98769f6 100755
--- a/scripts/cleanup-workdir
+++ b/scripts/cleanup-workdir
@@ -50,12 +50,12 @@ def run_co
If we don't do this, the sstate checksums vary for dpkg-native depending
on which MACHINE is set and this is clearly incorrect. It leads
to dpkg-native rebuilding far too often.
Signed-off-by: Richard Purdie
diff --git a/meta/recipes-devtools/dpkg/dpkg.inc
b/meta/recipes-devtools/dpkg/dpkg.inc
Currently we weren't testing the deb backaned for sstate correctness
and there was a bug that had crept in. Ensure we cover all package
backends with the test regardless of what the distro/conf sets.
Signed-off-by: Richard Purdie
diff --git a/meta/lib/oeqa/selftest/sstatetests.py
b/meta/lib/oeq
QEMU produces a warning if drive format is not specified:
WARNING: Image format was not specified for
'tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64.wic'
and probing guessed raw.
Automatically detecting the format is dangerous for raw images,
write operations on block 0 wi
Added 'native' convenience shell script to run native tools.
Example of usage:
> bitbake bmap-tools-native
> native bmaptool --version
Signed-off-by: Ed Bartosh
---
scripts/native | 48
1 file changed, 48 insertions(+)
create mode 100755 scri
On 26 September 2016 at 16:42, André Draszik wrote:
> ++static int progress_callback_new(void *ptr, curl_off_t dltotal,
> curl_off_t dlnow, curl_off_t ultotal, curl_off_t ulnow)
> ++{
> ++(void) ultotal;
> ++(void) ulnow;
> ++
> ++struct percent_t *percent = (struct percen
Ups, sorry for that... :-(
Should I send a patch against master-next, or against master?
a.
On Mi, 2016-09-28 at 11:54 +0100, Burton, Ross wrote:
> On 26 September 2016 at 16:42, André Draszik wrote:
>
> >
> > ++static int progress_callback_new(void *ptr, curl_off_t dltotal,
> > curl_off_t dl
On 28 September 2016 at 12:56, André Draszik wrote:
> Ups, sorry for that... :-(
>
> Should I send a patch against master-next, or against master?
>
Happens to the best of us :) Edit your patch and resend it against master.
Ross
--
___
Openembedded
This will allow us to easily incorporate progress support
via bb.process.run()
Signed-off-by: André Draszik
---
.../cve-check-tool/cve-check-tool_5.6.4.bb | 45 +-
1 file changed, 19 insertions(+), 26 deletions(-)
diff --git a/meta/recipes-devtools/cve-check-tool/cve
We add a patch to report the progress, and at the same time
inform bitbake that progress can be extracted via the simple
'percent' progress handler.
Signed-off-by: André Draszik
---
.../cve-check-tool/cve-check-tool_5.6.4.bb | 2 +
...ogress-in-percent-when-downloading-CVE-db.patch | 1
On 28 Sep 2016, at 1:22, Robert Yang wrote:
meta/recipes-devtools/pseudo/files/0001-pseudo_server.c-add-prefix-for-log-and-make-log-cons.patch
I don't think this produces desireable behavior in the command-line use
case; so far as I can tell, this would result in getting no messages at
all n
Arm is unusual in that we force it to "linux-gnueabi" and "linux" doesn't
build. This was causing problems for multilib configurations which were assuming
"linux" was the default compiler rather than linux-gnueabi.
This change does two things, ensures symlinks are generated for linux-gnueabi
and a
On Wed, Sep 28, 2016 at 2:55 AM, Ed Bartosh
wrote:
> Added 'native' convenience shell script to run native tools.
> Example of usage:
> > bitbake bmap-tools-native
> > native bmaptool --version
>
> Signed-off-by: Ed Bartosh
>
‘add new script’ is not a useful commit message summary. You don’
On 09/27/2016 08:24 PM, Khem Raj wrote:
> On Tue, Sep 27, 2016 at 4:44 PM, Aníbal Limón
> wrote:
>> For apply this patch we need to host the db-6.0.35 tarball into yp
>> sources mirror because oracle page ask for login in order to download
>> the source.
>
> why do they ask for login ? is there
We need to understand that disclaimer may be its requiring every one who is
distributing it to accept it.
On Sep 28, 2016 8:04 AM, "Aníbal Limón"
wrote:
>
>
> On 09/27/2016 08:24 PM, Khem Raj wrote:
> > On Tue, Sep 27, 2016 at 4:44 PM, Aníbal Limón
> > wrote:
> >> For apply this patch we need t
Seems fine
On Sep 28, 2016 8:00 AM, "Richard Purdie" <
richard.pur...@linuxfoundation.org> wrote:
> Arm is unusual in that we force it to "linux-gnueabi" and "linux" doesn't
> build. This was causing problems for multilib configurations which were
> assuming
> "linux" was the default compiler rat
On 09/28/2016 10:26 AM, Khem Raj wrote:
> We need to understand that disclaimer may be its requiring every one who is
> distributing it to accept it.
There is no LICENSE changes in that upgrade the last license changes was
in the version 6.0.20 to AGPL-3 [1].
Also another option is to point to
On 9/28/16 10:26 AM, Khem Raj wrote:
> We need to understand that disclaimer may be its requiring every one who is
> distributing it to accept it.
It is purely Oracle wanting to stop people from automatically downloading from
them, also so they can harvest sales contacts. (nothing wrong with that
On 09/28/2016 06:44 PM, Mark Hatle wrote:
On 9/28/16 10:26 AM, Khem Raj wrote:
We need to understand that disclaimer may be its requiring every one who is
distributing it to accept it.
It is purely Oracle wanting to stop people from automatically downloading from
them, also so they can harvest
The SRC_URI was changed to point gentoo distfiles because now Oracle
request authorization for download the source code [1], there are no changes
in the LICENSE since version 6.0.20 when the LICENSE changes to AGPL-3
[2], also the md5sum was review to be sure that is the same.
This minor upgrade f
On 9/28/16 10:44 AM, Alexander Kanavin wrote:
> On 09/28/2016 06:44 PM, Mark Hatle wrote:
>> On 9/28/16 10:26 AM, Khem Raj wrote:
>>> We need to understand that disclaimer may be its requiring every one who is
>>> distributing it to accept it.
>>
>> It is purely Oracle wanting to stop people from a
On 28 September 2016 at 17:06, Aníbal Limón
wrote:
> @@ -18,16 +18,15 @@ RCONFLICTS_${PN} = "db3"
> PR = "r1"
>
Remove this PR please.
> # Note, when upgraded to 6.1.x, a patch in RPM will need to be removed to
> activate db 6.1 support.
> -
> -SRC_URI = "http://download.oracle.com/berkeley-
On 09/28/2016 11:30 AM, Julien Gueytat wrote:
> Related to the db recipe. There are also the patches that needs to be
> regenerated as the same patches are applied for the two current versions.
> At least on Ubuntu 16.06 the same patch can't be applied anymore on the
> two versions as the lines w
The SRC_URI was changed to point gentoo distfiles because now Oracle
request authorization for download the source code [1], there are no changes
in the LICENSE since version 6.0.20 when the LICENSE changes to AGPL-3
[2], also the md5sum was review to be sure that is the same.
This minor upgrade f
The SRC_URI was changed to point gentoo distfiles because now Oracle
request authorization for download the source code [1], there are no changes
in the LICENSE since version 6.0.20 when the LICENSE changes to AGPL-3
[2], also the md5sum was review to be sure that is the same.
This minor upgrade f
Related to the db recipe. There are also the patches that needs to be
regenerated as the same patches are applied for the two current versions.
At least on Ubuntu 16.06 the same patch can't be applied anymore on the
two versions as the lines where to apply the patches differs too much.
Le 28/0
On 09/28/2016 11:24 AM, Burton, Ross wrote:
> On 28 September 2016 at 17:06, Aníbal Limón
> wrote:
>
>> @@ -18,16 +18,15 @@ RCONFLICTS_${PN} = "db3"
>> PR = "r1"
>>
>
> Remove this PR please.
>
>
>> # Note, when upgraded to 6.1.x, a patch in RPM will need to be removed to
>> activate db 6.
Alright! I'm giving you that quickly.
Sent from my WIKO RAINBOW LITE 4GLe 28 sept. 2016 18:58, Aníbal Limón
a écrit :
>
>
>
> On 09/28/2016 11:30 AM, Julien Gueytat wrote:
> > Related to the db recipe. There are also the patches that needs to be
> > regenerated as the same patches are applied
From: "Davis, Michael"
Pulseaudio unit tests create a dependency on check not in the recipe.
Since unit tests are not used they are disabled to eliminate build race
condition.
Backported from master commit 92cfdb2ba7e04e2b70986c6569f500dd2a48b5d1
Signed-off-by: Michael Davis
Signed-off-by: Ro
$ bitbake -c patch db-native
WARNING: Host distribution "Ubuntu-16.04" has not been validated with
this version of the build system; you may possibly experience unexpected
failures. It is recommended that you use a tested distribution.
Loading cache: 100%
|###
Trying to start getty on a non-existent console will spew I/O errors
into auth.log on some hardware. Avoid this behavior by checking that
ttyS0 is a console that exists.
Fixes [YOCTO #10291].
Signed-off-by: California Sullivan
---
meta-yocto-bsp/conf/machine/genericx86-64.conf | 2 ++
1 file ch
On Wed, 2016-09-28 at 16:27 -0700, California Sullivan wrote:
> Trying to start getty on a non-existent console will spew I/O errors
> into auth.log on some hardware. Avoid this behavior by checking that
> ttyS0 is a console that exists.
>
> Fixes [YOCTO #10291].
>
> Signed-off-by: California Sul
From: Armin Kuster
LICENSE md5sum changed do to rewording some text not released to the license.
see https://github.com/eggert/tz/commit/8c143a2b65fdfd43a7911be6fdb700c9c4553f58
Changes to future time stamps
Turkey switched from EET/EEST (+02/+03) to permanent +03,
effective 2016-09-0
From: Armin Kuster
LICENSE file checksum changed do to a verbage change.
Changes to code
zic no longer generates binary files containing POSIX TZ-like
strings that disagree with the local time type after the last
explicit transition in the data. This fixes a bug with
Africa/C
Alrighty. I will resend there.
Thanks,
Cal
On 09/28/2016 04:39 PM, Saul Wold wrote:
On Wed, 2016-09-28 at 16:27 -0700, California Sullivan wrote:
Trying to start getty on a non-existent console will spew I/O errors
into auth.log on some hardware. Avoid this behavior by checking that
ttyS0 is a
This check seems to have gone in recently and doesn't appear to work
very well.
ERROR: linux-xlnx-3.14-xilinx+gitAUTOINC+2b48a8aeea-r0
do_kernel_version_sanity_check: Package Version
(3.14-xilinx+gitAUTOINC+2b48a8aeea) does not match of kernel being built
(4.6). Please update the PV variable to ma
On Mon, May 23, 2016 at 10:35:05AM +0100, Richard Purdie wrote:
> On Mon, 2016-05-23 at 10:07 +0200, Patrick Ohly wrote:
> > On Wed, 2016-05-18 at 12:38 -0700, Khem Raj wrote:
> > > This fix was not sufficient and there has to be extra fix done to
> > > also
> > > consider the case
> > > when sysro
On Wed, Sep 28, 2016 at 08:59:23PM -0400, Denys Dmytriyenko wrote:
> On Mon, May 23, 2016 at 10:35:05AM +0100, Richard Purdie wrote:
> > On Mon, 2016-05-23 at 10:07 +0200, Patrick Ohly wrote:
> > > On Wed, 2016-05-18 at 12:38 -0700, Khem Raj wrote:
> > > > This fix was not sufficient and there has
From: Richard Purdie
http://git.openembedded.org/openembedded-core-contrib/commit/?id=642c6cf0b6a0371de476513162bd0cefa9c438b3
introduces a problem if the USERADD_PARAM variable has trailing
whitespace as the code infinitely loops causing build hangs.
Add a similar sed expression to $remaining t
On Wed, Sep 28, 2016 at 09:07:19PM -0400, Denys Dmytriyenko wrote:
> On Wed, Sep 28, 2016 at 08:59:23PM -0400, Denys Dmytriyenko wrote:
> > On Mon, May 23, 2016 at 10:35:05AM +0100, Richard Purdie wrote:
> > > On Mon, 2016-05-23 at 10:07 +0200, Patrick Ohly wrote:
> > > > On Wed, 2016-05-18 at 12:3
Richard,
Can you please merge this ASAP to unbreak krogoth. Thanks a lot!
On Wed, Sep 28, 2016 at 09:27:35PM -0400, Denys Dmytriyenko wrote:
> From: Richard Purdie
>
> http://git.openembedded.org/openembedded-core-contrib/commit/?id=642c6cf0b6a0371de476513162bd0cefa9c438b3
> introduces a probl
Hi Peter,
Thanks for the reply, I tested your patch from git repo, it doesn't work,
the message goes to the terminal:
Child process exit status 4: lock_held
diff --git a/pseudo_server.c b/pseudo_server.c
index 8731d20..7c2db2f 100644
--- a/pseudo_server.c
+++ b/pseudo_server.c
@@ -162,6 +162,9
On 28 Sep 2016, at 21:31, Robert Yang wrote:
Hi Peter,
Thanks for the reply, I tested your patch from git repo, it doesn't
work,
the message goes to the terminal:
Child process exit status 4: lock_held
Huh. I'll have to look more closely, then.
$ kill -9 `ps aux | grep /usr/bin/pseud | aw
On 28 Sep 2016, at 21:31, Robert Yang wrote:
Thanks for the reply, I tested your patch from git repo, it doesn't
work,
the message goes to the terminal:
Child process exit status 4: lock_held
This, it turns out, is a result of a much worse bug which somehow
previously evaded detection,
and
Thanks, it works for me now, I will send a V2 with your patch sooner.
How about the prefix issues? Which ones should be prefixed do you think
please ?
Yocto 2.2 may not need the prefix, but we can treat it as an enhancement
for YP 2.3.
// Robert
On 09/29/2016 11:15 AM, Seebs wrote:
On 28 Sep
On 28 Sep 2016, at 22:34, Robert Yang wrote:
Thanks, it works for me now, I will send a V2 with your patch sooner.
How about the prefix issues? Which ones should be prefixed do you
think
please ?
Yocto 2.2 may not need the prefix, but we can treat it as an
enhancement
for YP 2.3.
I don't
On 09/29/2016 11:36 AM, Seebs wrote:
On 28 Sep 2016, at 22:34, Robert Yang wrote:
Thanks, it works for me now, I will send a V2 with your patch sooner.
How about the prefix issues? Which ones should be prefixed do you think
please ?
Yocto 2.2 may not need the prefix, but we can treat it as
Hi All,
Yocto version: yocto-2.1
Target: ARM imx6
Graphics: X11 (core-image-sato)
I am trying to use psplash with systemd and have come across the service
files prepared by Eric:
http://lists.busybox.net/pipermail/buildroot/2014-May/097233.html
Although the splash comes up for a split second an
* V2
- Backport Peter's patches, thanks Peter.
- Drop adding prefix for pseudo log after talked with Peter, we don't
need that since the log should go into pseudo.log.
* V1
- pseudo: add prefix for log and make log consistent
// Robert
The following changes since commit cdaafc372970077
When the client spawns a pseudo server, it starts out sending diagnostics
to stderr. This can be spammy in some cases with races during startup;
everything resolves, but we get scary-looking diagnostics. So shove
those into a log file.
Signed-off-by: Robert Yang
---
...t-diagnostics-during-start
54 matches
Mail list logo
