On Thu, 2014-05-01 at 18:16 -0300, Otavio Salvador wrote:
> On Thu, May 1, 2014 at 6:14 PM, Richard Purdie
> wrote:
> > On Thu, 2014-05-01 at 16:38 -0300, Otavio Salvador wrote:
> >> The metadata started using the bb.utils.contains_any which has been
> >> add in the BitBake 1.23.0 release, set thi
On Thu, 2014-05-01 at 16:38 -0300, Otavio Salvador wrote:
> The metadata started using the bb.utils.contains_any which has been
> add in the BitBake 1.23.0 release, set this as the minimal version to
> ensure parsing compatibility.
>
> Signed-off-by: Otavio Salvador
> ---
> meta/conf/sanity.conf
On Thu, May 1, 2014 at 6:14 PM, Richard Purdie
wrote:
> On Thu, 2014-05-01 at 16:38 -0300, Otavio Salvador wrote:
>> The metadata started using the bb.utils.contains_any which has been
>> add in the BitBake 1.23.0 release, set this as the minimal version to
>> ensure parsing compatibility.
>>
>> S
Apparently the bug was observed
http://sourceforge.net/p/curl/bugs/1350/
and fixed
https://github.com/bagder/curl/commit/38d582ff5
If not too late, I'll test and send a patch for this tomorrow.
Tudor.
> -Original Message-
> From: openembedded-core-boun...@lists.openembedded.org
> [mailto
The class itself currently does nothing. The idea is to mark all recipes that
make use of the texinfo utilities. In the future, this class could be used to
suppress the generation/formatting of documentation for performance,
explicitly track dependencies on these utilities, and eliminate Yocto's
cu
Hello list,
As per discussion with Richard Purdie and others, I'm submitting a patch to add
a class inherited by any recipe whose upstream package invokes the texinfo
utilities at build-time. The class currently does nothing; the purpose of this
commit is just to identify for future reference the
On Thu, May 1, 2014 at 3:10 AM, Martin Jansa wrote:
> On Wed, Apr 30, 2014 at 05:40:53PM -0300, Otavio Salvador wrote:
>> Signed-off-by: Otavio Salvador
>
> This should include required bitbake version bump.
Sent a new patch for it.
--
Otavio Salvador O.S. Systems
h
The metadata started using the bb.utils.contains_any which has been
add in the BitBake 1.23.0 release, set this as the minimal version to
ensure parsing compatibility.
Signed-off-by: Otavio Salvador
---
meta/conf/sanity.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/met
Hello,
We found this in our autobuilder for master:
| curl-tool_operate.o: In function `operate':
|
.../build-framebuffer/tmp/work/armv5te-poky-linux-gnueabi/curl/7.36.0-r0/curl-7.36.0/src/tool_operate.c:1798:
undefined reference to `hugehelp'
| collect2: error: ld returned 1 exit status
| make[
davest throws in his two cents below...
On 5/1/14, 10:02 AM, "Richard Purdie"
wrote:
>I was asked what I thought were things that needed discussion at OEDAM.
>Sadly I won't be there but I thought it might help to write down my
>thoughts in a few areas.
>
>Developer Workflow
>--
>
I was asked what I thought were things that needed discussion at OEDAM.
Sadly I won't be there but I thought it might help to write down my
thoughts in a few areas.
Developer Workflow
--
Firstly, I think the big piece we need to address as a project is
"developer workflow" as this
Within the OE build environment, we supply the correct fpu settings. These
only need to be spelt out for the on-target gcc.
Doing this means the checksums for the core compiler don't depend on the fpu
settings. We exclude the compiler tunes for similar reasons, it doesn't need
to influence the com
Since we no longer build target libs within gcc-cross, we can drop the
TARGET_CC_ARCH flags and hence make it independent of tune.
Signed-off-by: Richard Purdie
---
diff --git a/meta/recipes-devtools/gcc/gcc-cross.inc
b/meta/recipes-devtools/gcc/gcc-cross.inc
index ef88d3f..0bf29e3 100644
--- a/
The PKG_CONFIG definitions should now more closely match those from
native.bbclass.
We can't use ${libdir} here since it contains the target arch prefix.
Signed-off-by: Richard Purdie
---
diff --git a/meta/classes/cross.bbclass b/meta/classes/cross.bbclass
index a8f3b60..28fd211 100644
--- a/met
Unfortunately expandKeys() notices overlap between the SDK and TARGET
PREFERRED_PROVIDERS entries when we set things up for the SDK recipes.
To avoid this, delete one of the sets of keys to avoid supurious warnings.
Signed-off-by: Richard Purdie
---
diff --git a/meta/classes/base.bbclass b/meta/
gcc-cross technically depends on the C library however we can use
one toolchain for multiple different tunes within a given architecture.
Manually remove these dependencies so that gcc-cross isn't rebuild with
every tune change.
Signed-off-by: Richard Purdie
---
diff --git a/meta/conf/layer.conf
We should be explicit about the providers for the SDK toolchain so
add entries to do this.
Signed-off-by: Richard Purdie
---
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 1afc94d..03742d8 100644
--- a/meta/conf/distro/include/tcmode-
On Wed, Apr 30, 2014 at 06:39:31PM +0300, Valentin Popa wrote:
> Newer versions of gnutls depends on nettle.
> [OE-core] [PATCH 1/3] nettle: add nettle to poky
This isn't poky.
>
> Signed-off-by: Valentin Popa
> ---
> meta/recipes-support/nettle/nettle_2.7.1.bb | 22 ++
>
Signed-off-by: Fathi Boudra
---
meta/recipes-kernel/systemtap/systemtap_git.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-kernel/systemtap/systemtap_git.inc
b/meta/recipes-kernel/systemtap/systemtap_git.inc
index c280313..78439c1 100644
--- a/meta/recipes-k
Hi Valentin,
On Wednesday 30 April 2014 18:39:31 Valentin Popa wrote:
> Newer versions of gnutls depends on nettle.
>
> Signed-off-by: Valentin Popa
> ---
> meta/recipes-support/nettle/nettle_2.7.1.bb | 22 ++
> 1 file changed, 22 insertions(+)
> create mode 100644 meta/rec
20 matches
Mail list logo
