date:20150601

Re: [yocto] Issue with toaster

2015-06-01 Thread Raghavendra Kakarla

Hi Alex,

Do you have any updates on this issue?

Regards,

Raghavendra K.

From: Damian, Alexandru 
Sent: Friday, May 15, 2015 7:38 PM
To: Raghavendra Kakarla
Cc: Barros Pena, Belen; yocto@yoctoproject.org
Subject: Re: [yocto] Issue with toaster

I'm still investigating these bugs.

There is something funny going on, but I didn't figure out the root cause yet.

Alex

On Fri, May 8, 2015 at 10:42 AM, Raghavendra Kakarla 
mailto:raghavendra.kaka...@inedasystems.com>>
 wrote:

Hi Alex,

I attached the Toaster Web logs with this mail.

Please find the attachments.

Thanks and Regards,

Raghavendra K.

From: Damian, Alexandru 
mailto:alexandru.dam...@intel.com>>
Sent: Friday, May 8, 2015 2:24 PM
To: Raghavendra Kakarla
Cc: Barros Pena, Belen; yocto@yoctoproject.org

Subject: Re: [yocto] Issue with toaster

Hello,

Is there any error message displayed on screen ?

Can you please paste bin your latest toaster_web.log file  and send us the link 
?
You can find your latest toaster_web.log file by looking in /tmp/toaster_* and 
take most recent one. One way to do this is:

$ find /tmp/toaster_* -printf '%T@ %p\0' | sort -zk 1nr | xargs -0n1 | cut -d " 
" -f 2 | head -1

Thank you,
Alex

On Fri, May 8, 2015 at 6:14 AM, Raghavendra Kakarla 
mailto:raghavendra.kaka...@inedasystems.com>>
 wrote:
Hi Belen,

I am using yocto fido.

I am entered the my custom layer git repository url(Which is our local git 
repository where our product corresponding recipe layers re there),a unique 
layer name and our git repository revision number.

We entered these data but the import layer version is not respond.

Thanks and Regards,

Raghavendra K.

From: Barros Pena, Belen 
mailto:belen.barros.p...@intel.com>>
Sent: Thursday, May 7, 2015 6:17 PM
To: Raghavendra Kakarla; yocto@yoctoproject.org
Subject: Re: [yocto] Issue with toaster

On 07/05/2015 10:18, "Raghavendra Kakarla"
mailto:raghavendra.kaka...@inedasystems.com>>
 wrote:

>Hi,
>
>I have an issue while importing custom layer in toaster. When i gave the
>all layer information for importing the layer and click on the import
>layer button in toaster itwont respond.
>Could you please help for resolving this issue.

Hi Raghavendra,

We would need a bit more information to understand what's happening:

* Which branch are you using (fido or master). If you are using master,
which commit?
* Which data are you entering in the import layer form? Keep in mind that
you must provide a git url, a unique layer name and a revision. Without
that information, the "import layer" button will remain stubbornly
inactive and nothing will happen when you click on it.

Cheers

Belén

>
>
>
>Thanks in advance.
>
>
> Regards,
> Raghavendra K.
>

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--
Alex Damian
Yocto Project
SSG / OTC

--
Alex Damian
Yocto Project
SSG / OTC
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Question regarding python, _sysconfigdata.py, and building C extension modules on the target...

2015-06-01 Thread Bob Cochran


Hi,

While building a python 2.7 C extension module on the target (e.g., 
python setup.py build) I found that I needed to modify 
/usr/lib64/python2.7/_sysconfigdata.py to successfully build the module.


I modified both CC and LDSHARE.  For both, I removed 
--sysroot=/build/yocto//tmp/sysroots/'.  And for 
LDSHARE, I added -L/lib64, so gcc_s could be found.


I'm wondering whether this is expected behavior or perhaps a bug. 
Perhaps I should have setup my environment differently for building a C 
extension module on the target?


I would appreciate any advice on the best way to rectify this so I can 
use a non-modified, generated rootfs to build C extension modules on my 
target.


I'm using poky fido (508c4cac320d) and building with a Freescale t1040 
64bit (meta-fsl-ppc).


Thanks

Bob
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, June 2, 2015 8:00 AM US Pacific Time

2015-06-01 Thread Jolley, Stephen K

Tuesday, June 2, 2015 8:00 AM US Pacific Time



Agenda:



* Opens collection - 5 min (Stephen)

* Yocto Project status - 5 min (Stephen/team)

https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.9_Status

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_1.9_Features

* SWAT team rotation: Juro -> Anibal

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

* Opens - 10 min

* Team Sharing - 10 min





We encourage people attending the meeting to logon the Yocto Project IRC 
chancel during the meeting (optional):



Yocto IRC: http://webchat.freenode.net/?channels=#yocto

IRC Tutorial: http://www.irchelp.org/irchelp/irctutorial.html



Conference Details:

Company:   WIND RIVER SYS

Ready-Access Number: 8007302996/9139049836

Access Code: 2705751


For International numbers see: 
https://www.yoctoproject.org/tools-resources/community/monthly-technical-call


Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][layerindex-web] Add support for inherit field in recipes

2015-06-01 Thread Aníbal Limón

From: Alex Franco 

Modified: models.py, update.py, recipes.html, detail.html,
recipedetail.html, additional.css

To identify image recipes and provide inheritance data for recipes, an
inherits field was added to the recipe model, and then populated using
refactored data from __inherit_cache. Finally the field was also added
to Toaster templates, along with style changes proposed in attachment.

[YOCTO #7575]

Signed-off-by: Alex Franco 
Signed-off-by: Aníbal Limón 
---
 layerindex/models.py   |  1 +
 layerindex/static/css/additional.css   | 11 ++-
 layerindex/update.py   |  2 ++
 templates/layerindex/detail.html   |  4 +++-
 templates/layerindex/recipedetail.html |  4 
 templates/layerindex/recipes.html  |  4 +++-
 6 files changed, 23 insertions(+), 3 deletions(-)

diff --git a/layerindex/models.py b/layerindex/models.py
index dd291a3..d56565f 100644
--- a/layerindex/models.py
+++ b/layerindex/models.py
@@ -242,6 +242,7 @@ class Recipe(models.Model):
 bugtracker = models.URLField(blank=True)
 provides = models.CharField(max_length=255, blank=True)
 bbclassextend = models.CharField(max_length=100, blank=True)
+inherits = models.CharField(max_length=255, blank=True)
 
 updated = models.DateTimeField(auto_now = True)
 
diff --git a/layerindex/static/css/additional.css 
b/layerindex/static/css/additional.css
index 0703257..0d74db3 100644
--- a/layerindex/static/css/additional.css
+++ b/layerindex/static/css/additional.css
@@ -198,4 +198,13 @@ padding: 8px;
 
 .buttonblock-btn {
 margin-left: 8px;
-}
\ No newline at end of file
+}
+
+.icon-hdd {
+   margin-left: 2px;
+}
+
+.icon-hdd:hover {
+   cursor: pointer;
+}
+
diff --git a/layerindex/update.py b/layerindex/update.py
index a56507b..24e7960 100755
--- a/layerindex/update.py
+++ b/layerindex/update.py
@@ -65,6 +65,8 @@ def update_recipe_file(data, path, recipe, layerdir_start, 
repodir):
 recipe.bugtracker = envdata.getVar("BUGTRACKER", True) or ""
 recipe.provides = envdata.getVar("PROVIDES", True) or ""
 recipe.bbclassextend = envdata.getVar("BBCLASSEXTEND", True) or ""
+rlist = envdata.getVar("__inherit_cache", True) or []
+recipe.inherits = ' '.join(sorted([(split_recipe_fn(r)[0]) for r in 
rlist])) or ""
 recipe.save()
 
 # Get file dependencies within this layer
diff --git a/templates/layerindex/detail.html b/templates/layerindex/detail.html
index e013e4c..c9439b3 100644
--- a/templates/layerindex/detail.html
+++ b/templates/layerindex/detail.html
@@ -198,7 +198,7 @@
 
 {% for recipe in layerbranch.sorted_recipes %}
 
-{{ recipe.name }}
+{{ recipe.name }}{% if 'image' in recipe.inherits %}{% endif %}
 {{ recipe.pv }}
 {{ recipe.short_desc 
}}
 
@@ -321,6 +321,8 @@
 e.preventDefault();
 $(this).tab('show');
 })
+
+$('.icon-hdd').tooltip({title:"Inherits image"});
 });
 });
 
diff --git a/templates/layerindex/recipedetail.html 
b/templates/layerindex/recipedetail.html
index 658694e..cde8e50 100644
--- a/templates/layerindex/recipedetail.html
+++ b/templates/layerindex/recipedetail.html
@@ -83,6 +83,10 @@
 Layer
 {{ 
recipe.layerbranch.layer.name }} ({{ recipe.layerbranch.branch.name}} 
branch)
 
+
+Inherits
+{{ recipe.inherits }}
+
 
 
 
diff --git a/templates/layerindex/recipes.html 
b/templates/layerindex/recipes.html
index 6777ed2..f1a7834 100644
--- a/templates/layerindex/recipes.html
+++ b/templates/layerindex/recipes.html
@@ -52,7 +52,7 @@
 
 {% for recipe in recipe_list %}
  0 
%}class="muted"{% endif %}>
-{{ 
recipe.name }}
+{{ 
recipe.name }}{% if 'image' in recipe.inherits %}{% 
endif %}
 {{ recipe.pv }}
 {{ recipe.short_desc }}
 {{ recipe.layerbranch.layer.name }}
@@ -82,6 +82,8 @@
 firstfield = $("#filter-form input:text").first()
 if( ! firstfield.val() )
 firstfield.focus()
+
+$('.icon-hdd').tooltip({title:"Inherits image"});
 });
 
 {% endblock %}
-- 
1.9.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ERROR: Multiple .bb files

2015-06-01 Thread Joel (Xi Zhou) Zhou

Updated.
If I bypass the "packagedata" error,  the new kernel recipe runs into "ERROR: 
Multiple .bb files ..."
Anyone has suggestion for this issue?

Thanks,
Joel
---
NOTE: Compute totals (have 1 endpoint(s))
ERROR: Multiple .bb files are due to be built which each provide virtual/kernel 
(/projects/poky/build64/../meta-brcm/recipes-kernel/linux/linux-brcm-nand_3.14.29.bb
 
/projects/poky/build64/../meta-brcm/recipes-kernel/linux/linux-brcm_3.14.29.bb).
This usually means one provides something the other doesn't and should.


From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Joel (Xi Zhou) Zhou
Sent: Monday, June 01, 2015 10:48 AM
To: yocto@yoctoproject.org
Subject: [yocto] Multi recipes for different defconfig on the same kernel source

Hi all,

I need to create multiple recipes for different kernel config based on the same 
kernel source.
In my experiment, I create a new recipe linux-brcm-nand based on linux-brcm, 
the only different is the kernel defconfig file.
>From the following error message, it looks like the idea of multi-kernel 
>providers.

What is the correct way to different kernel config on the same kernel source?

Thanks,
Joel
--
ERROR: The recipe linux-brcm-nand is trying to install files into a shared area 
when those files already exist. Those files and their manifest location are:
   /projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel
Matched in manifest-brcm-linux-brcm.packagedata
/projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel.packaged
Matched in manifest-brcm-linux-brcm.packagedata
...
/projects/poky/build64/tmp/sysroots/brcm/pkgdata/kernel-depmod/System.map-3.14.29
Matched in manifest-brcm-linux-brcm.packagedata
Please verify which recipe should provide the above files.
The build has stopped as continuing in this scenario WILL break things, if not 
now, possibly in the future (we've seen builds fail several months later). If 
the system knew how to recover from this automatically it would however there 
are several different scenarios which can result in this and we don't know 
which one this is. It may be you have switched providers of something like 
virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you 
need to execute the clean task for both recipes and it will resolve this error. 
It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. 
Cleaning those recipes should again resolve this error however switching 
DISTRO_FEATURES on an existing build directory is not supported, you should 
really clean out tmp and rebuild (reusing sstate should be safe). It could be 
the overlapping files detected are harmless in which case adding them to 
SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is 
including two different conflicting versions of things (e.g. bluez 4 and bluez 
5 and the correct solution for that would be to resolve the conflict. If in 
doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: If the above message is too much, the simpler version is you're advised 
to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix 
things in most (but not all) cases.
ERROR: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /projects/poky/build64/tmp/work/brcm 
-poky-linux/linux-brcm-nand/3.14.29-r6/temp/log.do_packagedata.40045
NOTE: recipe linux-brcm-nand-3.14.29-r6: task do_packagedata: Failed
ERROR: Task 11 
(/projects/poky/build64../meta-brcm/meta/recipes-kernel/linux/linux-brcm-nand_3.14.29.bb,
 do_packagedata) failed with exit code '1'
NOTE: Tasks Summary: Attempted 447 tasks of which 445 didn't need to be rerun 
and 2 failed.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Recipe reporting system] Upgradable recipe name list

2015-06-01 Thread recipe-report

This mail was sent out by Recipe reporting system.

This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade this time, they can fill in
RECIPE_NO_UPDATE_REASON_pn-"xxx" in upstream_tracking files to ignore this
recipe remainder until newer upstream version was detected.

Example:
RECIPE_NO_UPDATE_REASON_pn-"xxx" = "Not upgrade to 2.0 is unstable"

You can check the detail information at:

http://packages.yoctoproject.org/

Package   Version  Upstream version  Maintainer 
  NoUpgradeReason
  ---    
---  --
nfs-utils 1.3.11.3.2 Alejandro Hernandez
midori0.5.80.5.10Alejandro Hernandez
python-smmap  0.8.20.9.0 Alejandro Hernandez
python3   3.4.33.5.0b1   Alejandro Hernandez
python2.7.93.5.0b1   Alejandro Hernandez
cronie1.4.12   1.5.0 Alejandro Hernandez
which 2.20 2.21  Alejandro Hernandez
gnome-icon-theme  2.31.0   3.12.0Alejandro Hernandez
jpeg  8d   9aAníbal Limón   
  webkit-gtk 1.8.3 doesn't wo...
dpkg  1.17.25  1.18.1Aníbal Limón
sqlite3   3.8.10.0 3.8.10.2. Aníbal Limón
mc4.8.13   4.8.14Aníbal Limón
screen4.0.34.2.1 Aníbal Limón
nettle2.7.13.1rc3Armin Kuster   
  3.0.0 breaks gnutls, api ch...
lz4   128+gitX r123  Armin Kuster
linux-libc-headers3.19 3.19.8Bruce Ashfield
console-tools 0.3.21999.03.02Chen Qi
dbus-test 1.8.10   1.9.16Chen Qi
dbus  1.8.16   1.9.16Chen Qi
systemd   219-stable+gitX  21522eade6dd8422b...  Chen Qi
util-linux2.26.1   2.26.2Chen Qi
gawk  4.1.14.1.3 Chen Qi
iproute2  3.17.0   4.0.0 Cristian Iorga
libpcap   1.6.21.7.3 Cristian Iorga
libvorbis 1.3.41.3.5 Cristian Iorga
libatomics-ops7.2  7.4.0 Cristian Iorga
speex 1.2rc1   1.2rc2Cristian Iorga
db6.0.30   6.1.23.NC Cristian Iorga 
  API compatibility issue
libical   1.0.01.0.1 Cristian Iorga
libtirpc  0.2.50.3.1 Cristian Iorga
linux-yocto-rt3.14.36+gitX 3.14.39+gitAUTOIN...  Darren Hart
u-boot-fw-utils   v2015.01+gitXv2015.04+gitAUTOI...  Denys Dmytriyenko
u-boot-mkimagev2015.01+gitXv2015.04+gitAUTOI...  Denys Dmytriyenko
u-bootv2015.01+gitXv2015.04+gitAUTOI...  Denys Dmytriyenko
ncurses   5.9  20150530  Hongxu Jia
distcc3.1  3.2rc1Hongxu Jia
qmmp  0.7.70.8.4 Hongxu Jia
perl  5.20.0   5.21.11   Hongxu Jia
createrepo0.4.11   0.10.4Hongxu Jia 
  Versions after 0.9.* use YU...
bash  4.3  4.3.30Hongxu Jia 
  The latest version in yocto...
python-mako   0.9.11.0.1 Khem Raj
python-nose   1.2.11.3.6 Khem Raj
python-numpy  1.7.01.9.2 Khem Raj
python3-distribute0.6.32   0.7.3 Khem Raj
rpm   5.4.14   5.4.15Mark Hatle
libpfm4   4.3.04.6.0 Matthew McClintock
liberror-perl 0.17023  0.17024   No maintainer
debianutils   4.5  4.5.1 No maintainer
grub  2.00+X   2.00+AUTOINC+ca59...  Paul Eggleton
dropbear  2014.66  2015.67   Paul Eggleton
cmake 2.8.12.2 3.2.2 Paul Eggleton
dosfstools2.11 3.0.27Paul Eggleton
libav 9.16 11.4  Paul Eggleton
x264  r2265+gitX   r2491 Paul Eggleton
qt4-embedded  4.8.65.4.1 Paul Eg

Re: [yocto] getting started...

2015-06-01 Thread Ed Sutter


On 5/31/2015 8:16 AM, Paul Eggleton wrote:

On Friday 29 May 2015 14:41:37 Trevor Woerner wrote:

Hi Ed,

On 05/27/15 16:32, Ed Sutter wrote:

This year I have two ongoing iMX6 based linux projects, and may need
to use a beaglebone
or RPi for some other small project.

The point of the above detail is that I'd like to backup a bit and
attempt to use Yocto to
organize all four of these with one instance of Yocto/Poky.  Is that
practical?

Yes, that would be a great idea!Have a look at angstrom, for example:
http://www.angstrom-distribution.org. They build one distro for a whole
bunch of different machines. As such, they start with a whole bunch of
different layers, most of which are BSP layers, and then simply do:

$ MACHINE= bitbake 

e.g.

$ MACHINE=raspberrypi2 bitbake angstrom-image
$ MACHINE=beaglebone bitbake angstrom-image
...

and build the exact same image for a bunch of different boards/machines.

They've recently switched to using a repo manifest (which I think is a
great idea): https://github.com/Angstrom-distribution/angstrom-manifest

I've been playing around with doing essentially the same thing for a
"poky" distribution here (but it's still a work-in-progress and not
really ready for prime time yet): https://github.com/twoerner/layer-repos


   Seems

to me that is the ideal goal of Yocto, but I don't see many BSPs
listed under the project
downloads page.

Take a look here:
http://layers.openembedded.org/layerindex/branch/master/layers this is
the "master" list of all the "known" layers, recipes, etc. As you can
see, there are quite a few BSP layers.

Furthermore, you can click on the "Machines" tab i.e.

http://layers.openembedded.org/layerindex/branch/master/machines/

Type in a keyword (or leave the box empty to see all) and hit Search, and
you'll see a list of the matching machines provided by all the layers in the
index.

Cheers,
Paul


Trevor & Paul,
Ok, thanks much.  I'll dig into this more now.
By the way, the page that gave me the impression there were very
few BSPs is this: https://www.yoctoproject.org/downloads/bsps
Clicking on "Board Support Packages" and using  and 
for "YP Core Release" and "Processor Family" respectively.

--
Ed Sutter
Alcatel-Lucent Technologies -- Bell Laboratories
Phone: 908-582-2351
Email: ed.sut...@alcatel-lucent.com

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH] poky.conf: DISTRO_VERSION bump

2015-06-01 Thread Beth Flanagan

We missed the DISTRO_VERSION bump for the 1.6.3 release. I've opened
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7836 to
ensure that this doesn't happen again.

Signed-off-by: Beth Flanagan 
---
 meta-yocto/conf/distro/poky.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta-yocto/conf/distro/poky.conf b/meta-yocto/conf/distro/poky.conf
index b62de4b..9c10031 100644
--- a/meta-yocto/conf/distro/poky.conf
+++ b/meta-yocto/conf/distro/poky.conf
@@ -1,6 +1,6 @@
 DISTRO = "poky"
 DISTRO_NAME = "Poky (Yocto Project Reference Distro)"
-DISTRO_VERSION = "1.6.2"
+DISTRO_VERSION = "1.6.3"
 DISTRO_CODENAME = "daisy"
 SDK_VENDOR = "-pokysdk"
 SDK_VERSION := "${@'${DISTRO_VERSION}'}"
-- 
1.9.1

-
Intel Ireland Limited (Branch)
Collinstown Industrial Park, Leixlip, County Kildare, Ireland
Registered Number: E902934

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Multi recipes for different defconfig on the same kernel source

2015-06-01 Thread Joel (Xi Zhou) Zhou

Hi all,

I need to create multiple recipes for different kernel config based on the same 
kernel source.
In my experiment, I create a new recipe linux-brcm-nand based on linux-brcm, 
the only different is the kernel defconfig file.
>From the following error message, it looks like the idea of multi-kernel 
>providers.

What is the correct way to different kernel config on the same kernel source?

Thanks,
Joel
--
ERROR: The recipe linux-brcm-nand is trying to install files into a shared area 
when those files already exist. Those files and their manifest location are:
   /projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel
Matched in manifest-brcm-linux-brcm.packagedata
/projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel.packaged
Matched in manifest-brcm-linux-brcm.packagedata
...
/projects/poky/build64/tmp/sysroots/brcm/pkgdata/kernel-depmod/System.map-3.14.29
Matched in manifest-brcm-linux-brcm.packagedata
Please verify which recipe should provide the above files.
The build has stopped as continuing in this scenario WILL break things, if not 
now, possibly in the future (we've seen builds fail several months later). If 
the system knew how to recover from this automatically it would however there 
are several different scenarios which can result in this and we don't know 
which one this is. It may be you have switched providers of something like 
virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you 
need to execute the clean task for both recipes and it will resolve this error. 
It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. 
Cleaning those recipes should again resolve this error however switching 
DISTRO_FEATURES on an existing build directory is not supported, you should 
really clean out tmp and rebuild (reusing sstate should be safe). It could be 
the overlapping files detected are harmless in which case adding them to 
SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is 
including two different conflicting versions of things (e.g. bluez 4 and bluez 
5 and the correct solution for that would be to resolve the conflict. If in 
doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: If the above message is too much, the simpler version is you're advised 
to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix 
things in most (but not all) cases.
ERROR: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: /projects/poky/build64/tmp/work/brcm 
-poky-linux/linux-brcm-nand/3.14.29-r6/temp/log.do_packagedata.40045
NOTE: recipe linux-brcm-nand-3.14.29-r6: task do_packagedata: Failed
ERROR: Task 11 
(/projects/poky/build64../meta-brcm/meta/recipes-kernel/linux/linux-brcm-nand_3.14.29.bb,
 do_packagedata) failed with exit code '1'
NOTE: Tasks Summary: Attempted 447 tasks of which 445 didn't need to be rerun 
and 2 failed.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] build hello_world.c in yocto

2015-06-01 Thread Burton, Ross

On 1 June 2015 at 13:08, Victor Rodriguez  wrote:

> EXTRA_IMAGE_FEATURES = "debug-tweaks dev-pkgs"
>

As the documentation says (
http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#ref-features-image),
dev-pkgs is just the headers and library links for the packages you've
installed.  No tools come with that.

Ross
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] build hello_world.c in yocto

2015-06-01 Thread Victor Rodriguez

On Sun, May 31, 2015 at 5:48 PM, Burton, Ross  wrote:
>
> On 29 May 2015 at 21:59, Victor Rodriguez  wrote:
>>
>> Question what are the necessary IMAGE_INSTALL_append to build a c
>> hello world in an core-image-minimal ?
>
>
> The easy way is to add tools-sdk to IMAGE_FEATURES.  That gives you a
> complete toolchain (not just gcc) and more pieces.
>
> Ross
Thanks a lot Ross

I will try this on e, I had the idea that just with

EXTRA_IMAGE_FEATURES = "debug-tweaks dev-pkgs"

Thanks

Victor Rodriguez
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Strange configure error (???)

2015-06-01 Thread Neuer User

Hi

I'm currently moving from Dora to Fido. I moved all my recipes to a new
yocto installation and are modifying the recipes where necessary.

I have a very strange error when configuring a kernel recipe
(linux-cubox-i). Actually, there is no error when using the defaut
recipe included in fido. Only if I add the following bbappend file in
order to change the kernel configuration, I get the error:

FILESEXTRAPATHS_prepend := "${THISDIR}/linux-cubox-i:"

SRC_URI = "file://defconfig \
   file://videoin.cfg \
   file://networking.cfg \
   file://wlan.cfg \
   file://dm-crypt.cfg \
   file://no-caam.cfg \
   file://leds.cfg \
   file://mod-to-builtin.cfg \
   file://watchdog-nowayout.cfg \
"

KERNEL_IMAGETYPE_cubox-i = "zImage"


Error:

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function do_configure
| WARNING: exit code 128 from a shell command.
| ERROR: Function failed: do_configure (log file is located at
/home/ubuntu/yocto1.8/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.14.14-r0/temp/log.do_configure.29043)


Nothing more in the configure log. :(

Any idea, what is wrong? In general I just want to use a diffent kernel
config. Actually a kernel config that worked before without problems on
dora. I really have no idea, why this isn't working or even what the
error means.

Thanks for any help

Michael

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] cortexa15 toolchain compilation option

2015-06-01 Thread Neelkumar Patel

Hi,

Sorry option is  -mfloat-abi=hard.

We have to provide below option during compilation.
arm-XXX-gcc  -mfloat-abi=hard hello.c

We do not want to give -mfloat-abi=hard option during compilation.

If we do not provide that option (arm-XXX-gcc  hello.c ) then it gives below 
error.
fatal error: gnu/stubs-soft.h: No such file or directory

Thanks
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Neelkumar Patel
Sent: 01 June 2015 12:04
To: yocto@yoctoproject.org
Subject: [yocto] cortexa15 toolchain compilation option

Hi,

We are building the toolchain for cortexa15 CPU in oe-core and we are able to 
build the toolchain but during the compilation of the application we have to 
provide manually option "--with-float=hard".

e.g.  We have one application called "hello.c". We have to provide below option 
for compilation. If we do not provide --with-float option then we are getting 
compilation error.

arm-XXX-gcc  --with-float=hard  hello.c

Is there any option to remove "-with-float" option during the application 
compilation. Is there any change we have to do in oe-core ??

Thanks in Advance.

*
 eInfochips Business Disclaimer: This e-mail message and all attachments 
transmitted with it are intended solely for the use of the addressee and may 
contain legally privileged and confidential information. If the reader of this 
message is not the intended recipient, or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, or other use of this message or its 
attachments is strictly prohibited. If you have received this message in error, 
please notify the sender immediately by replying to this message and please 
delete it from your computer. Any views expressed in this message are those of 
the individual sender unless otherwise stated. Company has taken enough 
precautions to prevent the spread of viruses. However the company accepts no 
liability for any damage caused by any virus transmitted by this email. 
*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Issue with toaster

[yocto] Question regarding python, _sysconfigdata.py, and building C extension modules on the target...

[yocto] Agenda: Yocto Project Technical Team Meeting - Tuesday, June 2, 2015 8:00 AM US Pacific Time

[yocto] [PATCH][layerindex-web] Add support for inherit field in recipes

[yocto] ERROR: Multiple .bb files

[yocto] [Recipe reporting system] Upgradable recipe name list

Re: [yocto] getting started...

[yocto] [PATCH] poky.conf: DISTRO_VERSION bump

[yocto] Multi recipes for different defconfig on the same kernel source

Re: [yocto] build hello_world.c in yocto

Re: [yocto] build hello_world.c in yocto

[yocto] Strange configure error (???)

Re: [yocto] cortexa15 toolchain compilation option

13 matches

Site Navigation

Mail list logo

Footer information