Re: [yocto] Is it possible to add machine specific changes in a separate custom layer?

[Paul Eggleton]

Hi Felix,

On Monday 23 September 2013 18:40:19 Felix01 Fischer wrote:
> My goal is to build a custom-layer which supports 2 devices building on
> top of the meta-intel and meta-ivi layer without changing anything except
> my meta-custom layer.
> 
> Is it possible to have machine specific changes in a separate layer
> building on top of  another layer?
> I want to costumise meta-intel/meta-crownbay and
> meta-intel/meta-chiefriver without changing something inside the
> meta-intel layer.
> My goal is to have modifications for the meta-intel layer in a meta-custom
> layer, which only get considered if a certain MACHINE ?= ""  (crownbay
> or chiefriver) from the meta-intel layer is set.
> Is this possible?

This is definitely possible - the key is to make use of bbappends and machine
overrides. Append files are covered here:

http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#using-bbappend-files

Overrides effectively make an assignment statement apply only when the
specified override appears in the value of the OVERRIDES variable. For
example:

VARIABLENAME = "the default value"
VARIABLENAME_crownbay = "value specific to crownbay machine"

You can use append/prepend to add to the variable value instead of just
setting it:

ANOTHERVARIABLE_append_chiefriver = " appended only for chiefriver"
ANOTHERVARIABLE_prepend_crownbay = "prepended only for crownbay "

By default, the value of OVERRIDES includes the value of MACHINE, DISTRO, etc.
If you run bitbake -e | less and then search (with /) for OVERRIDES= you can
see how how OVERRIDES is constructed.

> I have the same question regarding DISTRO. I want some changes to be
> considered if DISTRO = poky and some other changes when DISTRO =
> poky-ivi-systemd.

Same as above only you'd be using the distro name as the override e.g.

SOMETHING_append_poky = " whatever poky-specific additions are needed"

> Is it possible to maintain these modifications in ONE custom layer or do I
> need to have seperate layers (one for poky, one for poky-ivi-systemd and
> machine specific changes inside the meta-intel layer)?

You don't have to, but generally we recommend keeping the machine
customisations separate from policy (distro) customisations. This can make
things easier if you have to change the machine later.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [yocto-docs][PATCH] ref-manual: update list of undocumented classes

[Paul Eggleton]

Signed-off-by: Paul Eggleton 
---
 documentation/ref-manual/ref-classes.xml | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/documentation/ref-manual/ref-classes.xml 
b/documentation/ref-manual/ref-classes.xml
index 6ed8fe5..83d4c1b 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -981,6 +981,7 @@
 allarch.bbclass
 archive*.bbclass
 binconfig.bbclass
+bin_package.bbclass
 blacklist.bbclass
 bootimg.bbclass
 boot-directdisk.bbclass
@@ -989,6 +990,7 @@
 buildstats.bbclass
 ccache.bbclass
 chrpath.bbclass
+clutter.bbclass
 cmake.bbclass
 cml1.bbclass
 copyleft_compliance.bbclass
@@ -998,7 +1000,9 @@
 crosssdk.bbclass
 deploy.bbclass
 distrodata.bbclass
+distro_features_check.bbclass
 dummy.bbclass
+extrausers.bbclass
 fontcache.bbclass
 gconf.bbclass
 gettext.bbclass
@@ -1017,12 +1021,11 @@
 image-mklibs.bbclass
 image-prelink.bbclass
 image-swab.bbclass
-imagetest-dummy.bbclass
-imagetest-qemu.bbclass
 image_types.bbclass
 image_types_uboot.bbclass
 insserv.bbclass
 kernel-arch.bbclass
+kernel-module-split.bbclass
 kernel-yocto.bbclass
 lib_package.bbclass
 linux-kernel-base.bbclass
@@ -1063,6 +1066,7 @@
 sip.bbclass
 siteconfig.bbclass
 sourcepkg.bbclass
+spdx.bbclass
 sstate.bbclass
 staging.bbclass
 syslinux.bbclass
@@ -1071,8 +1075,11 @@
 tinderclient.bbclass
 toolchain-scripts.bbclass
 typecheck.bbclass
+uboot-config.bbclass
 utility-tasks.bbclass
 utils.bbclass
+vala.bbclass
+waf.bbclass
 -->
 
 
-- 
1.8.1.2

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

Re: [yocto] [DYLAN] RPATH issue with qt5's qtwebkit

[Trevor Woerner]

On 18 September 2013 21:36, Trevor Woerner 
wrote:
> I'll create a patch

I have created two patches:
- one for dylan:
http://article.gmane.org/gmane.comp.handhelds.openembedded/59766
- one for master:
http://article.gmane.org/gmane.comp.handhelds.openembedded/59795

Which I'm hoping will be found acceptable for merging.
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-selinux][PATCH] documentation: update guidance for runqemu

[Joe MacDonald]

Testing SELinux on QEMU occasionally results in OOM conditions during a
relabel from time to time.  Update the documentation to warn about this
and suggest a way to avoid the situation.

Signed-off-by: Joe MacDonald 
---
 SELinux-FAQ |8 
 1 file changed, 8 insertions(+)

diff --git a/SELinux-FAQ b/SELinux-FAQ
index 5894626..b6a0df9 100644
--- a/SELinux-FAQ
+++ b/SELinux-FAQ
@@ -111,6 +111,14 @@ For example, when you are using qemu targets,
 
   $ runqemu qemumips core-image-selinux ext3 nographic bootparams="selinux=0"
 
+The initial filesystem relabel step requires considerable memory and can result
+in unexpected, sometimes impossible to reproduce, failures if an OOM condition
+occurs while it is in progress.  Therefore you should consider allocating at a
+minimum 512MB of RAM to your qemu image.  1GB or more is recommended.  This is
+accomplished by adding qemuparams="-m 1024" to your runqemu options.
+
+The defaults for various platforms vary, though it is usually around 256MB.
+
 3.2 - How do I turn enforcing mode on/off?
 
 You can specify the SELinux mode in /etc/selinux/config.
-- 
1.7.10.4

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

[yocto] Problems with the ADT installation

[Dusty Clark]

Reading the Quick Start and ADT manuals, it was recommended to use the ADT
installer script as the easiest method to get the tools and the Eclipse
plugin in place. I'm running a Fedora 17 VM as the development host, and
would like to target Beaglebone and vanilla x86 devices using Eclipse.
However, I ran into some issues:

First, the prerequisites lists a package "eglibc-devel" that does not seem
to exist as a yum package, although it looks like the poky tarball has it
inside -- so it should be built from the source tarball during installation
of poky -- e.g. NOT using the ADT installation? The ADT guide warns against
mixing installation methods, building ADT from poky vs. the ADT installer,
etc. So, what is the recommended method for having this prerequisite
library for Yocto?

Second, the ADT installer script is pointing to 404s when getting packages:
the YOCTOADT_REPO variable is pointing to a repo at
http://adtrepo-dev.yoctoproject.org//$VERSION that doesn't exist. I edited
adt_installer.conf to point to what I thought was the appropriate master as
/1.4+snapshot-$hash-master, but the install script failed with a message
about wget trying to get the opkg portion of the repo. There appears to be
no opkg folder at all to be found there...so is the ADT installer now
deprecated and one should just install poky and build the ADT stuff from
there on?

Thanks for any help!
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] IPK naming oddity for ipkg's containing archived ${PN}-dev files

[Glenn Schmottlach]

I've run across what appears to be a naming inconsistency (not sure if it's
intentional or a bug) that seems to impact the name given to the ipk file
for recipe's "dev" files.


Let me be more clear. My recipe produces a shared object library called:

libtts_engine.so

This shared library is deployed in /usr/lib and the package-split directory
structure looks like the following in my recipe workdir:

package-split/tts-sdk-dev
package-split/tts-sdk-dev/usr
package-split/tts-sdk-dev/usr/lib
package-split/tts-sdk-dev/usr/lib/libtts_engine.so
package-split/tts-sdk-dev/usr/include
package-split/tts-sdk-dev/usr/include/tts.h

So, when Yocto generates my ipk archive I would expect it to be named
something like:

tts-sdk-dev_${PV}_${PACKAGE_ARCH}.ipk

Instead, Yocto is generating the following name for the "dev" ipk:

libtts_engine-dev_${PV}_${PACKAGE_ARCH}.ipk

This is *not* consistent with how the other ipk are named by Yocto, e.g.

tts-sdk_${PV}_${PACKAGE_ARCH}.ipk
tts-sdk-doc_${PV}_${PACKAGE_ARCH}.ipk
tts-sdk-dbg_${PV}_${PACKAGE_ARCH}.ipk

In the poky class file (package_ipk.bbclass) I looked at the
do_package_ipk() python function and see that there is an explicit query
for the following variable to determine the base name of the ipk file:

pkgname = localdata.getVar('PKG_%s' % pkg, True)

In most cases, this look-up returns the expected name, e.g. tts-sdk-doc,
tts-sdk-dbg, etc But for some reason, the "dev" package name is
remapped from tts-sdk to libtts_engine. My only counter-measure to correct
this is to add the following explicit assignment in my recipe:

PKG_${PN}-dev = "${PN}-dev"

This seems to "correct" the name. Can anyone explain to me the behavior I
am observing? Is there some reason the "dev" package (and only the "dev"
package) is named differently when the ipk is created. Am I breaking an
expected behavior by forcing it to use the more consistent
tts-sdk-dev_${PV}_${PACKAGE_ARCH}.ipk name? I can't find any documentation
that answers this question.

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

Re: [yocto] Problems with the ADT installation

[Zhang, Jessica]

Hi Dusty,

 

The prerequisite for eglibc-devel are for running a yocto build on your
host. adt-installer is for  setup the cross development environment for
application development so it's not the tool to install those prerequisite
packages.

 

As to your adt-installer issues, we've heard similar report from our QA
engineer as well, so to confirm, are you using the latest built out of
adt-installer?

 

Thanks,

Jessica

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Dusty Clark
Sent: Tuesday, September 24, 2013 12:08 PM
To: yocto@yoctoproject.org
Subject: [yocto] Problems with the ADT installation

 

Reading the Quick Start and ADT manuals, it was recommended to use the ADT
installer script as the easiest method to get the tools and the Eclipse
plugin in place. I'm running a Fedora 17 VM as the development host, and
would like to target Beaglebone and vanilla x86 devices using Eclipse.
However, I ran into some issues:

 

First, the prerequisites lists a package "eglibc-devel" that does not seem
to exist as a yum package, although it looks like the poky tarball has it
inside -- so it should be built from the source tarball during installation
of poky -- e.g. NOT using the ADT installation? The ADT guide warns against
mixing installation methods, building ADT from poky vs. the ADT installer,
etc. So, what is the recommended method for having this prerequisite library
for Yocto?

 

Second, the ADT installer script is pointing to 404s when getting packages:
the YOCTOADT_REPO variable is pointing to a repo at
http://adtrepo-dev.yoctoproject.org//$VERSION
  that doesn't exist. I edited
adt_installer.conf to point to what I thought was the appropriate master as
/1.4+snapshot-$hash-master, but the install script failed with a message
about wget trying to get the opkg portion of the repo. There appears to be
no opkg folder at all to be found there...so is the ADT installer now
deprecated and one should just install poky and build the ADT stuff from
there on?

 

Thanks for any help!

 



smime.p7s
Description: S/MIME cryptographic signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [Patch v2 1/1] common-pc-wifi.cfg: add support for broadcom wifi drivers

[nitin . a . kamble]

From: Nitin A Kamble 

This enables broadcom wifi driver modules for the common-pc(-64)
machines.

Fixes Bug:
[YOCTO #5238]

Signed-off-by: Nitin A Kamble 
---
 meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg | 6 ++
 1 file changed, 6 insertions(+)

diff --git a/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg 
b/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg
index 1769b15..a19e028 100644
--- a/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg
+++ b/meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg
@@ -16,3 +16,9 @@ CONFIG_ATH9K=m
 
 CONFIG_RT2X00=m
 CONFIG_RT2800PCI=m
+
+CONFIG_BRCMUTIL=m
+CONFIG_BRCMSMAC=m
+CONFIG_BRCMFMAC=m
+CONFIG_BRCMFMAC_SDIO=y
+CONFIG_BRCMFMAC_USB=y
-- 
1.8.1.4

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

[linux-yocto] [Patch v2 0/1] update commit message for a commit

[nitin . a . kamble]

From: Nitin A Kamble 

Adding more information to the commit adding broadcom wifi drivers.

Thanks,
Nitin

The following changes since commit ba7add39d0c088bc5fc4acbbcdd9a3b4f79d1958:

  common-pc-64: add kernel CONFIG options for sugarbay platform (2013-09-24 
18:15:39 +)

are available in the git repository at:

  git://git.yoctoproject.org/linux-yocto-contrib nitin/3.10-meta
  
http://git.yoctoproject.org/cgit.cgi/linux-yocto-contrib/log/?h=nitin/3.10-meta

Nitin A Kamble (1):
  common-pc-wifi.cfg: add support for broadcom wifi drivers

 meta/cfg/kernel-cache/bsp/common-pc/common-pc-wifi.cfg | 6 ++
 1 file changed, 6 insertions(+)

-- 
1.8.1.4

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

Re: [yocto] IPK naming oddity for ipkg's containing archived ${PN}-dev files

[Khem Raj]

On Sep 24, 2013, at 1:17 PM, Glenn Schmottlach  wrote:

> I've run across what appears to be a naming inconsistency (not sure if it's 
> intentional or a bug) that seems to impact the name given to the ipk file for 
> recipe's "dev" files.
> 
> 
> Let me be more clear. My recipe produces a shared object library called:
> 
> libtts_engine.so

may be this should be something libtts_engine.so.X and libtts_engine.so is then 
a symlink to it which is commonly the
case with shared libraries

> 
> This shared library is deployed in /usr/lib and the package-split directory 
> structure looks like the following in my recipe workdir:
> 
> package-split/tts-sdk-dev
> package-split/tts-sdk-dev/usr
> package-split/tts-sdk-dev/usr/lib
> package-split/tts-sdk-dev/usr/lib/libtts_engine.so
> package-split/tts-sdk-dev/usr/include
> package-split/tts-sdk-dev/usr/include/tts.h
> 
> So, when Yocto generates my ipk archive I would expect it to be named 
> something like:
> 
> tts-sdk-dev_${PV}_${PACKAGE_ARCH}.ipk
> 
> Instead, Yocto is generating the following name for the "dev" ipk:
> 
> libtts_engine-dev_${PV}_${PACKAGE_ARCH}.ipk

this is because of debian library naming. see 
http://www.debian.org/doc/debian-policy/ch-sharedlibs.html
and http://www.v7w.com/debian/libpkg-guide.html#naminglibpkg

> 
> This is *not* consistent with how the other ipk are named by Yocto, e.g.
> 
> tts-sdk_${PV}_${PACKAGE_ARCH}.ipk
> tts-sdk-doc_${PV}_${PACKAGE_ARCH}.ipk
> tts-sdk-dbg_${PV}_${PACKAGE_ARCH}.ipk
> 
> In the poky class file (package_ipk.bbclass) I looked at the do_package_ipk() 
> python function and see that there is an explicit query for the following 
> variable to determine the base name of the ipk file:
> 
> pkgname = localdata.getVar('PKG_%s' % pkg, True)
> 
> In most cases, this look-up returns the expected name, e.g. tts-sdk-doc, 
> tts-sdk-dbg, etc But for some reason, the "dev" package name is remapped 
> from tts-sdk to libtts_engine. My only counter-measure to correct this is to 
> add the following explicit assignment in my recipe:
> 
> PKG_${PN}-dev = "${PN}-dev"
> 
> This seems to "correct" the name. Can anyone explain to me the behavior I am 
> observing? Is there some reason the "dev" package (and only the "dev" 
> package) is named differently when the ipk is created. Am I breaking an 
> expected behavior by forcing it to use the more consistent 
> tts-sdk-dev_${PV}_${PACKAGE_ARCH}.ipk name? I can't find any documentation 
> that answers this question.
> 
> Thanks . . .
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

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

Re: [yocto] Problems with the ADT installation

[Khem Raj]

On Sep 24, 2013, at 2:09 PM, Dusty Clark  wrote:

> Hello Jessica,
> 
> OK, so for plain application development, I don't need eglibc-devel 
> library...just the cross-development toolchain and whatever recipes and 
> whatnot for my target, yes?
> 
> For the record, I downloaded the ADT tarball from here:
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.4/adt-installer/
> The link in the manual is a 404, so I found this one by modifying the link 
> location in the browser.
> 
> Then I browsed around and found what I thought was the closest snapshot, and 
> edited the adt_installer.conf as follows:
> 
> #YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org//1.4.2-d734ab491a30078d43dee5440c03acce2d251425-dylan";
> 
> #Edit by Dusty 9/24/13, since the original repo target is a 404:
> YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org/1.4+snapshot-6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/";
> 
> And of course this failed as mentioned. I attach the installer logfile for 
> your reference...I tried it twice, once with the bad link and again with the 
> edit. 
> 
> Thanks for your help!


Looking at your logs

 * opkg_download: Failed to download 
http://adtrepo-dev.yoctoproject.org//1.4.2-d734ab491a30078d43dee5440c03acce2d251425-dylan/adt-ipk/x86_64-nativesdk/Packages,
 wget returned 8.
opkg update process ended…

and return 8 for wget suggests "Server issued an error response."

Does it happens everytime you retry ?

e.g. I did below and it all downloaded ok.

wget 
http://adtrepo-dev.yoctoproject.org/1.4+snapshot-6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/adt-ipk/x86_64-nativesdk/Packages
--2013-09-24 14:24:18--  
http://adtrepo-dev.yoctoproject.org/1.4+snapshot-6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/adt-ipk/x86_64-nativesdk/Packages
Resolving adtrepo-dev.yoctoproject.org (adtrepo-dev.yoctoproject.org)... 
140.211.169.59
Connecting to adtrepo-dev.yoctoproject.org 
(adtrepo-dev.yoctoproject.org)|140.211.169.59|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2753125 (2.6M)
Saving to: ‘Packages’

100%[===>]
 2,753,125   1.34MB/s   in 2.0s   

2013-09-24 14:24:21 (1.34 MB/s) - ‘Packages’ saved [2753125/2753125]




> 
> Dusty Clark
> Staff Engineer Sr.
> MMT Observatory
> University of Arizona
> Tucson, AZ 85721
> 
> 
> On Tue, Sep 24, 2013 at 1:30 PM, Zhang, Jessica  
> wrote:
> Hi Dusty,
> 
>  
> 
> The prerequisite for eglibc-devel are for running a yocto build on your host. 
> adt-installer is for  setup the cross development environment for application 
> development so it’s not the tool to install those prerequisite packages.
> 
>  
> 
> As to your adt-installer issues, we’ve heard similar report from our QA 
> engineer as well, so to confirm, are you using the latest built out of 
> adt-installer?
> 
>  
> 
> Thanks,
> 
> Jessica
> 
>  
> 
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] 
> On Behalf Of Dusty Clark
> Sent: Tuesday, September 24, 2013 12:08 PM
> To: yocto@yoctoproject.org
> Subject: [yocto] Problems with the ADT installation
> 
>  
> 
> Reading the Quick Start and ADT manuals, it was recommended to use the ADT 
> installer script as the easiest method to get the tools and the Eclipse 
> plugin in place. I'm running a Fedora 17 VM as the development host, and 
> would like to target Beaglebone and vanilla x86 devices using Eclipse. 
> However, I ran into some issues:
> 
>  
> 
> First, the prerequisites lists a package "eglibc-devel" that does not seem to 
> exist as a yum package, although it looks like the poky tarball has it inside 
> -- so it should be built from the source tarball during installation of poky 
> -- e.g. NOT using the ADT installation? The ADT guide warns against mixing 
> installation methods, building ADT from poky vs. the ADT installer, etc. So, 
> what is the recommended method for having this prerequisite library for Yocto?
> 
>  
> 
> Second, the ADT installer script is pointing to 404s when getting packages: 
> the YOCTOADT_REPO variable is pointing to a repo at 
> http://adtrepo-dev.yoctoproject.org//$VERSION that doesn't exist. I edited 
> adt_installer.conf to point to what I thought was the appropriate master as 
> /1.4+snapshot-$hash-master, but the install script failed with a message 
> about wget trying to get the opkg portion of the repo. There appears to be no 
> opkg folder at all to be found there...so is the ADT installer now deprecated 
> and one should just install poky and build the ADT stuff from there on?
> 
>  
> 
> Thanks for any help!
> 
>  
> 
> 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

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

Re: [yocto] Problems with the ADT installation

[Zhang, Jessica]

Please see my answer below.

 

From: Dusty Clark [mailto:dcl...@mmto.org] 
Sent: Tuesday, September 24, 2013 2:09 PM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problems with the ADT installation

 

Hello Jessica,

OK, so for plain application development, I don't need eglibc-devel
library...just the cross-development toolchain and whatever recipes and
whatnot for my target, yes?

[JZ] correct for app devel you really need the cross toolchain and the
sysroot which contains the target libraries and headers.



For the record, I downloaded the ADT tarball from here:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.4/adt-installer/

The link in the manual is a 404, so I found this one by modifying the link
location in the browser.

Then I browsed around and found what I thought was the closest snapshot, and
edited the adt_installer.conf as follows:

#YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org//1.4.2-d734ab491a30078d4
3dee5440c03acce2d251425-dylan
 "

#Edit by Dusty 9/24/13, since the original repo target is a 404:
YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org/1.4+snapshot-6b4f7e4b26c5
1f0c1517c0a697031e7bc488b76f-master/"

And of course this failed as mentioned. I attach the installer logfile for
your reference...I tried it twice, once with the bad link and again with the
edit.

[JZ] I just realized that you're using 1.4 release, can you try to download
the adt-installer from
http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.2/adt-installer/
to ensure using the right adtrepo? You shouldn't need to manually tweak the
adtrepo in the config file.

Thanks for your help!

Dusty Clark
Staff Engineer Sr.

MMT Observatory
University of Arizona
Tucson, AZ 85721

 

On Tue, Sep 24, 2013 at 1:30 PM, Zhang, Jessica 
wrote:

Hi Dusty,

 

The prerequisite for eglibc-devel are for running a yocto build on your
host. adt-installer is for  setup the cross development environment for
application development so it's not the tool to install those prerequisite
packages.

 

As to your adt-installer issues, we've heard similar report from our QA
engineer as well, so to confirm, are you using the latest built out of
adt-installer?

 

Thanks,

Jessica

 

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Dusty Clark
Sent: Tuesday, September 24, 2013 12:08 PM
To: yocto@yoctoproject.org
Subject: [yocto] Problems with the ADT installation

 

Reading the Quick Start and ADT manuals, it was recommended to use the ADT
installer script as the easiest method to get the tools and the Eclipse
plugin in place. I'm running a Fedora 17 VM as the development host, and
would like to target Beaglebone and vanilla x86 devices using Eclipse.
However, I ran into some issues:

 

First, the prerequisites lists a package "eglibc-devel" that does not seem
to exist as a yum package, although it looks like the poky tarball has it
inside -- so it should be built from the source tarball during installation
of poky -- e.g. NOT using the ADT installation? The ADT guide warns against
mixing installation methods, building ADT from poky vs. the ADT installer,
etc. So, what is the recommended method for having this prerequisite library
for Yocto?

 

Second, the ADT installer script is pointing to 404s when getting packages:
the YOCTOADT_REPO variable is pointing to a repo at
http://adtrepo-dev.yoctoproject.org//$VERSION
  that doesn't exist. I edited
adt_installer.conf to point to what I thought was the appropriate master as
/1.4+snapshot-$hash-master, but the install script failed with a message
about wget trying to get the opkg portion of the repo. There appears to be
no opkg folder at all to be found there...so is the ADT installer now
deprecated and one should just install poky and build the ADT stuff from
there on?

 

Thanks for any help!

 

 



smime.p7s
Description: S/MIME cryptographic signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Problems with the ADT installation

[Rifenbark, Scott M]

Looks like the link in the 1.4.2 manual does barf... the link in the 1.4.1 
manual resolves.  Not sure why there is no tarball of the ADT Installer at the 
1.4.2  location.

Scott

From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On 
Behalf Of Dusty Clark
Sent: Tuesday, September 24, 2013 2:09 PM
To: Zhang, Jessica
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problems with the ADT installation

Hello Jessica,

OK, so for plain application development, I don't need eglibc-devel 
library...just the cross-development toolchain and whatever recipes and whatnot 
for my target, yes?

For the record, I downloaded the ADT tarball from here:
http://downloads.yoctoproject.org/releases/yocto/yocto-1.4/adt-installer/
The link in the manual is a 404, so I found this one by modifying the link 
location in the browser.
Then I browsed around and found what I thought was the closest snapshot, and 
edited the adt_installer.conf as follows:

#YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org//1.4.2-d734ab491a30078d43dee5440c03acce2d251425-dylan"

#Edit by Dusty 9/24/13, since the original repo target is a 404:
YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org/1.4+snapshot-6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/";
And of course this failed as mentioned. I attach the installer logfile for your 
reference...I tried it twice, once with the bad link and again with the edit.
Thanks for your help!

Dusty Clark
Staff Engineer Sr.
MMT Observatory
University of Arizona
Tucson, AZ 85721

On Tue, Sep 24, 2013 at 1:30 PM, Zhang, Jessica 
mailto:jessica.zh...@intel.com>> wrote:
Hi Dusty,

The prerequisite for eglibc-devel are for running a yocto build on your host. 
adt-installer is for  setup the cross development environment for application 
development so it's not the tool to install those prerequisite packages.

As to your adt-installer issues, we've heard similar report from our QA 
engineer as well, so to confirm, are you using the latest built out of 
adt-installer?

Thanks,
Jessica

From: yocto-boun...@yoctoproject.org 
[mailto:yocto-boun...@yoctoproject.org] 
On Behalf Of Dusty Clark
Sent: Tuesday, September 24, 2013 12:08 PM
To: yocto@yoctoproject.org
Subject: [yocto] Problems with the ADT installation

Reading the Quick Start and ADT manuals, it was recommended to use the ADT 
installer script as the easiest method to get the tools and the Eclipse plugin 
in place. I'm running a Fedora 17 VM as the development host, and would like to 
target Beaglebone and vanilla x86 devices using Eclipse. However, I ran into 
some issues:

First, the prerequisites lists a package "eglibc-devel" that does not seem to 
exist as a yum package, although it looks like the poky tarball has it inside 
-- so it should be built from the source tarball during installation of poky -- 
e.g. NOT using the ADT installation? The ADT guide warns against mixing 
installation methods, building ADT from poky vs. the ADT installer, etc. So, 
what is the recommended method for having this prerequisite library for Yocto?

Second, the ADT installer script is pointing to 404s when getting packages: the 
YOCTOADT_REPO variable is pointing to a repo at 
http://adtrepo-dev.yoctoproject.org//$VERSION
 that doesn't exist. I edited adt_installer.conf to point to what I thought was 
the appropriate master as /1.4+snapshot-$hash-master, but the install script 
failed with a message about wget trying to get the opkg portion of the repo. 
There appears to be no opkg folder at all to be found there...so is the ADT 
installer now deprecated and one should just install poky and build the ADT 
stuff from there on?

Thanks for any help!


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

Re: [yocto] Problems with the ADT installation

[Rifenbark, Scott M]

I see the problem... the link has an underscore in it (adt_installer) instead 
of adt-installer.  I will fix that for "Current" manuals and republish to the 
website.

Scott

>-Original Message-
>From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Khem Raj
>Sent: Tuesday, September 24, 2013 2:27 PM
>To: Dusty Clark
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] Problems with the ADT installation
>
>
>On Sep 24, 2013, at 2:09 PM, Dusty Clark  wrote:
>
>> Hello Jessica,
>>
>> OK, so for plain application development, I don't need eglibc-devel
>library...just the cross-development toolchain and whatever recipes and
>whatnot for my target, yes?
>>
>> For the record, I downloaded the ADT tarball from here:
>> http://downloads.yoctoproject.org/releases/yocto/yocto-1.4/adt-
>installer/
>> The link in the manual is a 404, so I found this one by modifying the
>link location in the browser.
>>
>> Then I browsed around and found what I thought was the closest
>snapshot, and edited the adt_installer.conf as follows:
>>
>> #YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org//1.4.2-
>d734ab491a30078d43dee5440c03acce2d251425-dylan"
>>
>> #Edit by Dusty 9/24/13, since the original repo target is a 404:
>> YOCTOADT_REPO="http://adtrepo-dev.yoctoproject.org/1.4+snapshot-
>6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/"
>>
>> And of course this failed as mentioned. I attach the installer logfile
>for your reference...I tried it twice, once with the bad link and again
>with the edit.
>>
>> Thanks for your help!
>
>
>Looking at your logs
>
> * opkg_download: Failed to download http://adtrepo-
>dev.yoctoproject.org//1.4.2-d734ab491a30078d43dee5440c03acce2d251425-
>dylan/adt-ipk/x86_64-nativesdk/Packages, wget returned 8.
>opkg update process ended...
>
>and return 8 for wget suggests "Server issued an error response."
>
>Does it happens everytime you retry ?
>
>e.g. I did below and it all downloaded ok.
>
>wget http://adtrepo-dev.yoctoproject.org/1.4+snapshot-
>6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/adt-ipk/x86_64-
>nativesdk/Packages
>--2013-09-24 14:24:18--  http://adtrepo-
>dev.yoctoproject.org/1.4+snapshot-
>6b4f7e4b26c51f0c1517c0a697031e7bc488b76f-master/adt-ipk/x86_64-
>nativesdk/Packages
>Resolving adtrepo-dev.yoctoproject.org (adtrepo-dev.yoctoproject.org)...
>140.211.169.59
>Connecting to adtrepo-dev.yoctoproject.org (adtrepo-
>dev.yoctoproject.org)|140.211.169.59|:80... connected.
>HTTP request sent, awaiting response... 200 OK
>Length: 2753125 (2.6M)
>Saving to: 'Packages'
>
>100%[===
>
>>] 2,753,125   1.34MB/s   in 2.0s
>
>2013-09-24 14:24:21 (1.34 MB/s) - 'Packages' saved [2753125/2753125]
>
>
>
>
>>
>> Dusty Clark
>> Staff Engineer Sr.
>> MMT Observatory
>> University of Arizona
>> Tucson, AZ 85721
>>
>>
>> On Tue, Sep 24, 2013 at 1:30 PM, Zhang, Jessica
> wrote:
>> Hi Dusty,
>>
>>
>>
>> The prerequisite for eglibc-devel are for running a yocto build on
>your host. adt-installer is for  setup the cross development environment
>for application development so it's not the tool to install those
>prerequisite packages.
>>
>>
>>
>> As to your adt-installer issues, we've heard similar report from our
>QA engineer as well, so to confirm, are you using the latest built out
>of adt-installer?
>>
>>
>>
>> Thanks,
>>
>> Jessica
>>
>>
>>
>> From: yocto-boun...@yoctoproject.org [mailto:yocto-
>boun...@yoctoproject.org] On Behalf Of Dusty Clark
>> Sent: Tuesday, September 24, 2013 12:08 PM
>> To: yocto@yoctoproject.org
>> Subject: [yocto] Problems with the ADT installation
>>
>>
>>
>> Reading the Quick Start and ADT manuals, it was recommended to use the
>ADT installer script as the easiest method to get the tools and the
>Eclipse plugin in place. I'm running a Fedora 17 VM as the development
>host, and would like to target Beaglebone and vanilla x86 devices using
>Eclipse. However, I ran into some issues:
>>
>>
>>
>> First, the prerequisites lists a package "eglibc-devel" that does not
>seem to exist as a yum package, although it looks like the poky tarball
>has it inside -- so it should be built from the source tarball during
>installation of poky -- e.g. NOT using the ADT installation? The ADT
>guide warns against mixing installation methods, building ADT from poky
>vs. the ADT installer, etc. So, what is the recommended method for
>having this prerequisite library for Yocto?
>>
>>
>>
>> Second, the ADT installer script is pointing to 404s when getting
>packages: the YOCTOADT_REPO variable is pointing to a repo at
>http://adtrepo-dev.yoctoproject.org//$VERSION that doesn't exist. I
>edited adt_installer.conf to point to what I thought was the appropriate
>master as /1.4+snapshot-$hash-master, but the install script failed with
>a message about wget trying to get the opkg portion of the repo. There
>appears to be no opkg folder at 

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, September 24, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

[Liu, Song]

Attendees:
Nitin, Beth, JeffP, MichaelH, MarkH, Saul, Jessica, Darren, ScottR, Tom, Belen, 
Paul, Ross, Richard, AlexG, Song

Agenda:

* Opens collection - 5 min (Song)
* Yocto 1.5 status - 10 min (Song/team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.5_Status
  https://wiki.yoctoproject.org/charts/combo.html
  - Bug fixing: WDD is going up, but shows signs of stabilizing. Resolved 40+ 
bugs last week. Let's keep up the good work and bring WDD down.
  - QA: Running the full pass on last RC. Will have the report out tomorrow. 
Some issues on the generic x86 BSP, Ross will do some triage and look into them.
  - Build: the build last week has some instability issue. Most of them are 
timeout issues. Merged some priority setting code. Seems to work really well. 
Master's only issue is for meta-freescale ppc failure. No concern on that. Much 
better than before. Proposal is to branching today for the release. RP will 
take care of that when we are ready. We will be more strict on what patches we 
can merge after we branch. At the same time, we understand that many people are 
working on bug fixes to bring WDD down. It's a balance.
  - Partitioning patches: Tom has not posted anything yet. Cleaning up 
functionality. Will send out the patches this week. RP: We might be able to 
squeeze it in for this release, as long as it's standalone, nothing breaks 
because of it.
* SWAT team rotation: Saul
* Opens - 10 min
* Team Sharing - 20 min
  - Michael: working on the YP dev day server, get it out asap. Working hard on 
it.



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

[yocto] Yocto Project 1.5_M5.rc5 availability

[Flanagan, Elizabeth]

The rc5 build for the upcoming 1.5 release should be available in a
few hours at:

http://autobuilder.yoctoproject.org/pub/releases/1.5_M5.rc5

Please being testing as soon as it is available.

poky 4d8ab87d25ea6e59dc88375813ef88ee0ac813d0
meta-fsl-arm 561842ac3e1e9f59536dbbbc4a81876f9e0df97b
meta-fsl-ppc 28b7ac5a37a9705d090d7303a024d84efef61b89
meta-intel 67b58a79279ad1beaf8dc0c68fb411f1d440abe4
meta-minnow ad469d78a1f56abd3b7d5103f1e0344cb10684b1
meta-qt3 b73552fb998fd30a01dbee5a172e432a16078222
eclipse-poky-juno 2fa1c58940141a3c547c8790b8a6832167e8eb66
eclipse-poky-kepler ad74249895f882a8f00bdeef7a0f7c18998cc43e


-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto