|
[PATCH 0/1][meta-intel] Add a custom Image recipe
From: Kishore Bodke <kishore.k.bodke@...>
This patch adds the custom build Image recipe to install
all the corpus files into the image.
Please pull them into meta-intel/master.
From: Kishore Bodke <kishore.k.bodke@...>
This patch adds the custom build Image recipe to install
all the corpus files into the image.
Please pull them into meta-intel/master.
|
By
kishore.k.bodke@...
·
#9681
·
|
|
[meta-baryon][PATCH 4/4] talloc: specify the version of LGPL and include the license text
talloc is made available under version 3 (or later) of the LGPL.
This change fixes the following warning:
"WARNING: talloc: No generic license file exists for: LGPL in any provider"
Signed-off-by:
talloc is made available under version 3 (or later) of the LGPL.
This change fixes the following warning:
"WARNING: talloc: No generic license file exists for: LGPL in any provider"
Signed-off-by:
|
By
Kevin Strasser <kevin.strasser@...>
·
#9679
·
|
|
[meta-baryon][PATCH 3/4] orc: specify the generic licenses being used
With the exception of source that contains the Mersenne Twister algorithm,
the majority of orc source code is made available under the BSD 2-Clause
license. The source that contains the Mersenne
With the exception of source that contains the Mersenne Twister algorithm,
the majority of orc source code is made available under the BSD 2-Clause
license. The source that contains the Mersenne
|
By
Kevin Strasser <kevin.strasser@...>
·
#9680
·
|
|
[meta-baryon][PATCH 2/4] samba: remove unused directories after install
Some of the directories that are created during installation are left
empty and not shipped in the image.
Removing them clears up the following QA warning:
"WARNING: QA Issue: samba:
Some of the directories that are created during installation are left
empty and not shipped in the image.
Removing them clears up the following QA warning:
"WARNING: QA Issue: samba:
|
By
Kevin Strasser <kevin.strasser@...>
·
#9677
·
|
|
[meta-baryon][PATCH 1/4] proftpd: remove unused directories after install
Some of the directories that are created during installation are left
empty and not shipped in the image.
Removing them clears up the following QA warning:
"WARNING: QA Issue: proftpd:
Some of the directories that are created during installation are left
empty and not shipped in the image.
Removing them clears up the following QA warning:
"WARNING: QA Issue: proftpd:
|
By
Kevin Strasser <kevin.strasser@...>
·
#9678
·
|
|
[meta-baryon][PATCH 0/4] clear up build warnings
This patch set clears up some of the warnings that are generated when
building baryon against the tip of the 1.3_M3 branch of poky.
The following changes since commit
This patch set clears up some of the warnings that are generated when
building baryon against the tip of the 1.3_M3 branch of poky.
The following changes since commit
|
By
Kevin Strasser <kevin.strasser@...>
·
#9676
·
|
|
Re: build failure on current
Yeah, it's just a warning :)
This issue is rather perplexing. We're supposed to not be using the host tar
if it is older than 1.24 due to another bug in earlier versions - if an older
version is
Yeah, it's just a warning :)
This issue is rather perplexing. We're supposed to not be using the host tar
if it is older than 1.24 due to another bug in earlier versions - if an older
version is
|
By
Paul Eggleton
·
#9675
·
|
|
Re: build failure on current
Fair enough. And I should mention that the error I reported occurs on
Ubuntu 10.04. It's not like I wasn't warned. :-}
WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated
with
Fair enough. And I should mention that the error I reported occurs on
Ubuntu 10.04. It's not like I wasn't warned. :-}
WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated
with
|
By
Evade Flow <evadeflow@...>
·
#9674
·
|
|
Re: build failure on current
I was told that I hit the server at a busy time thus causing the fetch to fail. I just re-ran it and ran error free. I was also told this was a rare occurrence but it does happen.
Scott
I was told that I hit the server at a busy time thus causing the fetch to fail. I just re-ran it and ran error free. I was also told this was a rare occurrence but it does happen.
Scott
|
By
Rifenbark, Scott M <scott.m.rifenbark@...>
·
#9673
·
|
|
Re: build failure on current
Something was bugging me about this, so I dug up my notes. I was wrong when I
said switching to denzil fixed my problem---it did NOT. I simply cannot
untar/uncompress the perl archive from CPAN with
Something was bugging me about this, so I dug up my notes. I was wrong when I
said switching to denzil fixed my problem---it did NOT. I simply cannot
untar/uncompress the perl archive from CPAN with
|
By
Evade Flow <evadeflow@...>
·
#9672
·
|
|
Re: build failure on current
I'm new to Yocto, but I've seen similar errors that seem to be due to
differences in the version of tar on the build server. Everything's
fine on this machine:
good% tar --version
tar (GNU tar)
I'm new to Yocto, but I've seen similar errors that seem to be due to
differences in the version of tar on the build server. Everything's
fine on this machine:
good% tar --version
tar (GNU tar)
|
By
Evade Flow <evadeflow@...>
·
#9671
·
|
|
build failure on current
I am running through the build example for the QS and hit a failure when trying to access git://git.yoctoproject.org/libowl;protocol=git. I started with the tarball here:
I am running through the build example for the QS and hit a failure when trying to access git://git.yoctoproject.org/libowl;protocol=git. I started with the tarball here:
|
By
Rifenbark, Scott M <scott.m.rifenbark@...>
·
#9670
·
|
|
Re: Python 3 Recipe
I have recipes for if 3.3 actually I will publish it after 1.3 release it needs some fine touches
I have recipes for if 3.3 actually I will publish it after 1.3 release it needs some fine touches
|
By
Khem Raj
·
#9669
·
|
|
Python 3 Recipe
Hi all,
Are there any plans for Yocto to includePython 3.2.3 as an alternative to the Python 2.7.3 recipes? I mightneed to use it at some point, so I was wondering if it was on the
Hi all,
Are there any plans for Yocto to includePython 3.2.3 as an alternative to the Python 2.7.3 recipes? I mightneed to use it at some point, so I was wondering if it was on the
|
By
daniel_norris@...
·
#9668
·
|
|
Re: Cannot do atom-pc build with meta-cedartrail
Yeah, looks like the other SRC_URIs do that, but it's missing from that
SRC_URI - I just pushed a fix for this one to meta-intel/master.
Tom
Yeah, looks like the other SRC_URIs do that, but it's missing from that
SRC_URI - I just pushed a fix for this one to meta-intel/master.
Tom
|
By
Tom Zanussi <tom.zanussi@...>
·
#9667
·
|
|
Autogen and libopts/Autoopts - native package that generates the source for a target package.
Hi,
I have a recipe that uses GNU autoopts, which generates a dependency on libopts. This is the library that is required for any package using autoopts to compile.
GNU autoopts is a tool that is
Hi,
I have a recipe that uses GNU autoopts, which generates a dependency on libopts. This is the library that is required for any package using autoopts to compile.
GNU autoopts is a tool that is
|
By
Tim O'Callaghan <tocallaghan@...>
·
#9666
·
|
|
Re: Cannot do atom-pc build with meta-cedartrail
That's a bug alright.
It seems the overall SRC_URI of linux-yocto is overwritten by meta-cedartrail layer, when included. Should be fixed by using SRC_URI_cedartrail instead.
--
Mihai Lindner
That's a bug alright.
It seems the overall SRC_URI of linux-yocto is overwritten by meta-cedartrail layer, when included. Should be fixed by using SRC_URI_cedartrail instead.
--
Mihai Lindner
|
By
Mihai Lindner <mihaix.lindner@...>
·
#9665
·
|
|
Cannot do atom-pc build with meta-cedartrail
Hi,
If I add meta-intel and meta-cedartrail to my bblayers, when I try and
do an atom-pc build (which I thought should still work, right?) I get
the following error:
NOTE: Error during finalise
Hi,
If I add meta-intel and meta-cedartrail to my bblayers, when I try and
do an atom-pc build (which I thought should still work, right?) I get
the following error:
NOTE: Error during finalise
|
By
Burton, Ross <ross.burton@...>
·
#9664
·
|
|
Re: Yocto Bug Trend ww38
Hello,
Yes they can be separated from the Medium bugs (now they are all counted together).
Also if we want their “weight” to differ from the Medium ones we can change that too (I would suggest
Hello,
Yes they can be separated from the Medium bugs (now they are all counted together).
Also if we want their “weight” to differ from the Medium ones we can change that too (I would suggest
|
By
Serban, Laurentiu <laurentiu.serban@...>
·
#9663
·
|
|
Re: Yocto info
Hi Joy and Kishore,
2 things you need to fix/check:
1. Please extract your toolchain to /opt/poky, basically go to your root directory “/” and run “sudo tar –xvjf path to your
Hi Joy and Kishore,
2 things you need to fix/check:
1. Please extract your toolchain to /opt/poky, basically go to your root directory “/” and run “sudo tar –xvjf path to your
|
By
Zhang, Jessica
·
#9662
·
|