[yocto] [meta-raspberrypi][PATCH 0/1] raspberrypi3.conf: fix typo for BCM43430

2016-11-15 Thread Piotr Lewicki 
From: "piotr.lewicki" 

New linux-firmware subpackage is called "bcm43430" and not "bcrm43430".
Renaming it because the test image is not building with the typo.

piotr.lewicki (1):
  raspberrypi3.conf: fix typo for BCM43430

 conf/machine/raspberrypi3.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.7.4

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

[yocto] [meta-raspberrypi][PATCH 1/1] raspberrypi3.conf: fix typo for BCM43430

2016-11-15 Thread Piotr Lewicki 
From: "piotr.lewicki" 

Signed-off-by: Piotr Lewicki 
---
 conf/machine/raspberrypi3.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/raspberrypi3.conf b/conf/machine/raspberrypi3.conf
index 438c6e6..9820209 100644
--- a/conf/machine/raspberrypi3.conf
+++ b/conf/machine/raspberrypi3.conf
@@ -4,7 +4,7 @@
 
 MACHINEOVERRIDES = "raspberrypi2:${MACHINE}"
 
-MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"
+MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-bcm43430"
 
 include conf/machine/raspberrypi2.conf
 
-- 
2.7.4

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

Re: [yocto] [meta-raspberrypi][PATCH] linux-firmware_git.bbappend: Delete

2016-11-15 Thread Piotr Lewicki 

Hi.

Michael was right, the new subpackage was renamed and it is now called 
linux-firmware-bcm43430.


I have sent the patch with fixed typo.


Piotr


On 14.11.2016 18:45, Khem Raj wrote:

are you using linux-firmware-bcm43430

On Mon, Nov 14, 2016 at 4:27 AM, Piotr Lewicki  wrote:

Dear Raj,

I have been trying to test this, but I get "ERROR: Nothing RPROVIDES
'linux-firmware-brcm43430'".

I'm one hundred percent sure that I have the commit you have mentioned
("linux-firmware: package Broadcom BCM43430 firmware").

I use poky- latest on morty branch and meta-openembedded - also latest on
morty branch.

Since I don't use bluetooth I have removed the line

MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-brcm43430"

from the file `meta-raspberrypi/conf/machine/raspberrypi3.conf`


Any idea why it is not building for me?

BR,

Piotr


On 03.11.2016 23:26, Khem Raj wrote:

OE-core already bumped the base rev on linux-firmware package
to include the upstreamed version of brcmfmac43430 firmware in
september via OE-Core commit a0bc732976670810505286ba43feee70e2c812ce

Signed-off-by: Khem Raj 
---
   .../linux-firmware/LICENSE.broadcom_brcm80211  | 205
-
   .../linux-firmware/brcmfmac43430-sdio.bin  | Bin 368957 -> 0
bytes
   .../linux-firmware/brcmfmac43430-sdio.txt  |  66 ---
   .../linux-firmware/linux-firmware_git.bbappend |  34 
   4 files changed, 305 deletions(-)
   delete mode 100644
recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
   delete mode 100644
recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.bin
   delete mode 100644
recipes-kernel/linux-firmware/linux-firmware/brcmfmac43430-sdio.txt
   delete mode 100644
recipes-kernel/linux-firmware/linux-firmware_git.bbappend

diff --git
a/recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
b/recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
deleted file mode 100644
index e2cf868..000
---
a/recipes-kernel/linux-firmware/linux-firmware/LICENSE.broadcom_brcm80211
+++ /dev/null
@@ -1,205 +0,0 @@
-SOFTWARE LICENSE AGREEMENT
-
-Unless you and Broadcom Corporation (“Broadcom”) execute a separate
written
-software license agreement governing use of the accompanying software,
this
-software is licensed to you under the terms of this Software License
Agreement
-(“Agreement”).
-
-ANY USE, REPRODUCTION OR DISTRIBUTION OF THE SOFTWARE CONSTITUTES YOUR
-ACCEPTANCE OF THIS AGREEMENT.
-
-1. DEFINITIONS.
-
-1.1.   “Broadcom Product” means any of the proprietary integrated circuit
-product(s) sold by Broadcom with which the Software was designed to be
used, or
-their successors.
-
-1.2.   “Licensee” means you or if you are accepting on behalf of an
entity
-then the entity and its affiliates exercising rights under, and complying
with
-all of the terms of this Agreement.
-
-1.3.   “Software” shall mean that software made available by Broadcom to
-Licensee in binary code form with this Agreement.
-
-2. LICENSE GRANT; OWNERSHIP
-
-2.1.   License Grants.  Subject to the terms and conditions of this
Agreement,
-Broadcom hereby grants to Licensee a non-exclusive, non-transferable,
-royalty-free license (i) to use and integrate the Software in conjunction
with
-any other software; and (ii) to reproduce and distribute the Software
complete,
-unmodified and as provided by Broadcom, and only for use with a Broadcom
-Product.
-
-2.2.   Restriction on Modification.  Licensee may not make any
modifications
-to the Software.
-
-2.3.   Restriction on Distribution.  Licensee shall only distribute the
-Software under the terms of this Agreement and a copy of this Agreement
-accompanies such distribution.
-
-2.4.   Proprietary Notices.  Licensee shall not remove, efface or obscure
any
-copyright or trademark notices from the Software.  Licensee shall include
-reproductions of the Broadcom copyright notice with each copy of the
Software,
-except where such Software is embedded in a manner not readily accessible
to
-the end user.  Licensee acknowledges that any symbols, trademarks,
tradenames,
-and service marks adopted by Broadcom to identify the Software belong to
-Broadcom and that Licensee shall have no rights therein.
-
-2.5.   Ownership.  Broadcom shall retain all right, title and interest,
-including all intellectual property rights, in and to the Software.
Licensee
-hereby covenants that it will not assert any claim that the Software
created by
-or for Broadcom infringe any intellectual property right owned or
controlled by
-Licensee; provided however, the foregoing shall not apply in case the
Agreement
-is terminated.
-
-2.6.   No Other Rights Granted; Restrictions.  Apart from the license
rights
-expressly set forth in this Agreement, Broadcom does not grant and
Licensee
-does not receive any ownership right, title or interest nor any security
-interest or other interest in any intellectual property rights relating
to the
-Software, nor in any c

Re: [yocto] [sysvinit] Problem with disabling sysvinit service

2016-11-15 Thread Jussi Kukkonen 
On 13 November 2016 at 16:51, Lukasz Majewski  wrote:

> Dear All,
>
> Maybe here I would find answer to question which puzzles me from some
> time.
>
> The problem:
>
> Disable syslog service on startup of sysvinit based board.
> (syslog is defined in e.g. /etc/rc5.d/S20syslog -> /etc/init.d/syslog)
>
> Syslog on my setup is provided by busybox.
>
> I was trying to find where 'update-rc.d ... syslog ...' is called in the
> poky (2.1.2) source tree but without any success.
>
> Then, I've discovered that it is appended to INITSCRIPT_NAME variable
> and further processed by update-rc.d.bbclass
>

> Is there any method/recipe which would allow just removing S20klogd
> symlink from /etc/rcX.d from the created rootfs?
>
>
You should be able to modify (append) the busybox recipe to not create the
symlinks in the first place. I'm not 100% sure what the correct line is
but INITSCRIPT_PARAMS is the variable you want to modify. Maybe something
like this?

INITSCRIPT_PARAMS_${PN}-syslog = "start 80 . stop 20 0 1 6 ."

(that should be the default except with all start runlevels removed)

 - Jussi



> The goal is to have syslog installed (in this case built into busybox),
> but disabled at boot up time.
>
> Any help is more than welcome.
>
> Tanks in advance,
> Łukasz Majewski
>
> --
> ___
> 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] mklibs in USER_CLASSES (Khem Raj)

2016-11-15 Thread Taek Hyun Shin 
I did use only image-mklibs TTAnd, I did try modify some project make file for mklibs. add *_pic.aSo, I did resolve not pic file found for error message. just modified package.But, other error occurred as follow:__dso_handle undefinedDoes mklibs can't support c++? only support c library??




Thanks & Best Regards,Wily Taekhyun ShinTelechips Inc.R&D Center / Automotive Group / Linux Team / Research EngineerTel : +82-2-3443-6792(Ext. 390), M.P : +82-10-4376-5530, E-mail : ths...@telechips.comThis mail and attachments contain confidential information of Telechips Inc. which has its own authority. It is not allowed to disclose,transmit or use this confidential information to the third parties without the prior written consent of Telechips Inc. by any form or means. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents and destroy all copies of the original message.   --Original Message  Sender : yocto-requ...@yoctoproject.org  Received : 2016-11-12 05:02:24  To : yocto@yoctoproject.org  Title : yocto Digest, Vol 74, Issue 56Send yocto mailing list submissions to	yocto@yoctoproject.orgTo subscribe or unsubscribe via the World Wide Web, visit	https://lists.yoctoproject.org/listinfo/yoctoor, via email, send a message with subject or body 'help' to	yocto-requ...@yoctoproject.orgYou can reach the person managing the list at	yocto-ow...@yoctoproject.orgWhen replying, please edit your Subject line so it is more specificthan "Re: Contents of yocto digest..."Today's Topics:   1. Re: mklibs in USER_CLASSES (Khem Raj)   2. Re: Buildbot / Autobuilder / custom? (Beth 'pidge' Flanagan)--Message: 1Date: Fri, 11 Nov 2016 10:17:54 -0800From: Khem Raj To: ??? (Taek Hyun Shin) ,	yocto@yoctoproject.orgSubject: Re: [yocto] mklibs in USER_CLASSESMessage-ID: <7cdefdbc-baa9-4dfd-f60d-64c0d3c9e...@gmail.com>Content-Type: text/plain; charset="utf-8"On 11/11/16 1:22 AM, ??? (Taek Hyun Shin) wrote:> Hi,> > Somebody help met plz.> > > I'm using Yocto Project 2.0> > I want to reduce my rootfs due to fast execute binaries.> > So, I did apply mklibs using USE_CLASSESif you use prelink as well then make sure mklibs appear before prelink inUSE_CLASSES> > But, I got error message as follow:> > >  208 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libgmp.so.10> ; copying> >  209 reducing libgobject-2.0.so.0> >  210 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libgobject-2.0.so.0> ; copying> >  211 reducing libgstreamer-1.0.so.0> >  212 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libgstreamer-1.0.so.0> ; copying> >  213 reducing libhogweed.so.4> >  214 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libhogweed.so.4> ; copying> >  215 reducing libinput.so.10> >  216 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libinput.so.10> ; copying> >  217 reducing libjpeg.so.9> >  218 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libjpeg.so.9> ; copying> >  219 reducing liblog.so> >  220 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//liblog.so ;> copying> >  221 reducing libm.so.6> >  222 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/lib//libm.so.6 ;> copying> >  223 reducing libmenuw.so.5> >  224 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libmenuw.so.5> ; copying> >  225 reducing libmount.so.1> >  226 No pic file found for> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/lib//libmount.so.1 ;> copying> >  227 reducing libmtdev.so.1> > > How can I create the pic file each libraries> > > Help me plz TT> >  > >  > >  > >  > > /Thanks & Best Regards,/> > /*Wily Taekhyun Shin*/> > > *Telechips Inc.*> > *R&D Center / Automotive Group / Linux Team / Research Engineer*> > Tel : +82-2-3443-6792(Ext. 390), M.P : +82-10-4376-5530, E-mail> : ths...@telechips.com > > This mail and attachments contain confidential information of Telechips Inc.> which has its own authority. > > It is not allowed to disclose,transmit or use this confidential information to> the third parties without the prior written consent> of Telechips Inc. by any form or means.> If you are not the intended recipient, please notify the sender immediately> and do not disclose the contents and destroy all> copies of the original message.> > > -- next part --A non-text attachment was scrubbed...Name: signature.ascType: application/pgp-signatureSize: 204 bytesDesc: OpenPGP digital signatureURL: --Message: 2Date: Fri, 11 Nov 2016 18:37:53 +From: Beth 'pidge' Flanagan To: A

[yocto] [PATCH][yocto-autobuilder] nightly-qa-extras: test the API documentation DISTRO_FEATURE

2016-11-15 Thread Ross Burton 
Build the core-image-sato SDK with API documentation enabled to verify that this
doesn't regress.

Signed-off-by: Ross Burton 
---
 buildset-config.controller/nightly-qa-extras.conf | 4 
 1 file changed, 4 insertions(+)

diff --git a/buildset-config.controller/nightly-qa-extras.conf 
b/buildset-config.controller/nightly-qa-extras.conf
index f796bb1..9f56f3b 100644
--- a/buildset-config.controller/nightly-qa-extras.conf
+++ b/buildset-config.controller/nightly-qa-extras.conf
@@ -19,5 +19,9 @@ steps: [{'SetDest':{}},
 'atextappend' : '\nROOT_HOME = "/root"\n'}},
 {'BuildImages': {'images': 'core-image-minimal'}},
 {'RunSanityTests': {'images': 'core-image-minimal'}},
+{'CreateAutoConf': {'machine': 'qemux86-64', 'SDKMACHINE' : 'i686',
+'distro': 'poky', 'buildhistory' : False,
+'atextappend' : '\nDISTRO_FEATURES_append = " 
api-documentation"\n'}},
+{'BuildImages': {'images': 'core-image-sato:do_populate_sdk'}},
 {'DownloadErrorReports': {}},
 {'SendErrorReport': {}}]
-- 
2.8.1

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

[yocto] New error

2016-11-15 Thread Gary Thomas 

I just ran a new build for one of my PowerPC targets and I'm getting errors 
like these:

ERROR: openssh-7.3p1-r0 do_package: runstrip: ''powerpc-amltd-linux-gnuspe-strip' --remove-section=.comment 
--remove-section=.note 
'/build/diskstation_2016-11-15/tmp/work/p1022ds-amltd-linux-gnuspe/openssh/7.3p1-r0/package/usr/bin/scp.openssh'' strip 
command failed with 1 (b'powerpc-amltd-linux-gnuspe-strip: 
/build/diskstation_2016-11-15/tmp/work/p1022ds-amltd-linux-gnuspe/openssh/7.3p1-r0/package/usr/bin/strW48QK: Not enough 
room for program headers, try linking with 
-N\npowerpc-amltd-linux-gnuspe-strip:/build/diskstation_2016-11-15/tmp/work/p1022ds-amltd-linux-gnuspe/openssh/7.3p1-r0/package/usr/bin/strW48QK[.interp]: 
Bad value\n')
ERROR: coreutils-8.25-r0 do_package: runstrip: ''powerpc-amltd-linux-gnuspe-strip' --remove-section=.comment 
--remove-section=.note --strip-unneeded 
'/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/coreutils/8.25-r0/package/usr/lib/coreutils/libstdbuf.so'' 
strip command failed with 1 (b'powerpc-amltd-linux-gnuspe-strip: 
/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/coreutils/8.25-r0/package/usr/lib/coreutils/std1tFcO: 
Not enough room for program headers, try linking with 
-N\npowerpc-amltd-linux-gnuspe-strip:/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/coreutils/8.25-r0/package/usr/lib/coreutils/std1tFcO[.note.gnu.build-id]: 
Bad value\n')
ERROR: eudev-3.2-r0 do_package: runstrip: ''powerpc-amltd-linux-gnuspe-strip' --remove-section=.comment 
--remove-section=.note --strip-unneeded 
'/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/eudev/3.2-r0/package/lib/libudev.so.1.6.3'' strip 
command failed with 1 (b'powerpc-amltd-linux-gnuspe-strip: 
/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/eudev/3.2-r0/package/lib/stxt1rac: Not enough room 
for program headers, try linking with 
-N\npowerpc-amltd-linux-gnuspe-strip:/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/eudev/3.2-r0/package/lib/stxt1rac[.note.gnu.build-id]: 
Bad value\n')


Actually, I got 438 of them :-(

Build Configuration:
BB_VERSION= "1.32.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS= "powerpc-amltd-linux-gnuspe"
MACHINE   = "p1022ds"
DISTRO= "amltd"
DISTRO_VERSION= "2.2+snapshot-20161115"
TUNE_FEATURES = "m32 spe ppce500v2"
TARGET_FPU= "ppc-efd"
meta  = "master:43e652f3d1fee5ce7fad67e6400315eab1b34270"
meta-amltd= "master:697b2bc1467a311233f1da362aa4c8a2cccf52bf"
meta-diskstation  = "master:0839596be89af4da67fb7c5ab41337f1a382e5b5"
meta-freescale= "master:979d079732949c49f7a859e93278287eb95fa056"


Questions:
* What's the best way to fix them?  I assume it's just some
  compiler/binutils option I need to adjust.  I tried comparing
  this build against the stock qemuppc, but it got no such errors
  and I don't see the difference (except for the CPU tuning of
  e500v2 vs 7400).
* If these are labeled 'ERROR', why do the packages continue
  to be built?  Indeed, I ended up with a complete build image
  (which I've not been able to test yet so I don't know if these
  errors actually break things)

Thanks for any pointers

--

Gary Thomas |  Consulting for the
MLB Associates  |Embedded world

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

Re: [yocto] [sysvinit] Problem with disabling sysvinit service

2016-11-15 Thread Lukasz Majewski 
Hi Jussi,

> On 13 November 2016 at 16:51, Lukasz Majewski 
> wrote:
> 
> > Dear All,
> >
> > Maybe here I would find answer to question which puzzles me from
> > some time.
> >
> > The problem:
> >
> > Disable syslog service on startup of sysvinit based board.
> > (syslog is defined in e.g. /etc/rc5.d/S20syslog
> > -> /etc/init.d/syslog)
> >
> > Syslog on my setup is provided by busybox.
> >
> > I was trying to find where 'update-rc.d ... syslog ...' is called
> > in the poky (2.1.2) source tree but without any success.
> >
> > Then, I've discovered that it is appended to INITSCRIPT_NAME
> > variable and further processed by update-rc.d.bbclass
> >
> 
> > Is there any method/recipe which would allow just removing S20klogd
> > symlink from /etc/rcX.d from the created rootfs?
> >
> >
> You should be able to modify (append) the busybox recipe to not
> create the symlinks in the first place. I'm not 100% sure what the
> correct line is but INITSCRIPT_PARAMS is the variable you want to
> modify. Maybe something like this?
> 
> INITSCRIPT_PARAMS_${PN}-syslog = "start 80 . stop 20 0 1 6 ."
> 
> (that should be the default except with all start runlevels removed)
> 
>  - Jussi
> 

Thanks for advice. 

I've also thought about extending image.bbclass
to put function between do_rootfs and do_build.

In this way I could run update-rc.d in it.

Anyway, I will test your solution.

Thanks and best regards,
Łukasz Majewski

> 
> 
> > The goal is to have syslog installed (in this case built into
> > busybox), but disabled at boot up time.
> >
> > Any help is more than welcome.
> >
> > Tanks in advance,
> > Łukasz Majewski
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> >



pgp8_1tBnnFjZ.pgp
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] SWAT Reboot

2016-11-15 Thread Lock, Joshua G 
The short version is that the SWAT process document has been updated,
if you're a member of the SWAT team please take a few moments to read
this mail and update the wiki.


We're making a concerted effort in the 2.3 cycle to improve the SWAT
process and ensure that it's operating effectively.

To that end I've updated the SWAT process document on the Yocto Project
wiki to reflect current expectations, particularly in light of the
addition of the buildlogger tool during the morty cycle:

https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Build_Failure_
Swat_Team


In reviewing the process we've added an extra role, as described on the
wiki, for someone to be a first point of contact for the SWAT process
and to provide backup cover for the active member. This should help
provide continuity for the process when active members rotate and help
people external to the process with a constant point of contact.

As Tracy Graydon is already heavily involved in build and release
through her role as Yocto Project release engineer we've asked her to
help out here.

During the 2.3 development cycle we will be further improving the
buildlogger tool to automate more of the boilerplate aspects of the
SWAT process, most significantly a change to automate initial updating
of the BuildLog entry on a build failure:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=10466

It would be useful if SWAT members could update their user page on the
wiki to include their contact details and link to it from the members
section of the SWAT process page:

https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Member
s

Feel free to reach out to Tracy and myself with any questions.

Expect more updates as we proceed with the SWAT reboot and tool
enhancements.

Regards,

Joshua
-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

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

Re: [yocto] [yocto-announce] [ANNOUNCEMENT] Yocto Project 2.2 (morty 16.0.0) Released

2016-11-15 Thread Rich Persaud 
> On Nov 1, 2016, at 15:48, Tracy Graydon  wrote:
> 
> Hello,
> 
> The latest release of the Yocto Project 2.2 (morty-16.0.0) is now available 
> for download at:
> 
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.2/poky-morty-16.0.0.tar.bz2
> http://mirrors.kernel.org/yocto/yocto/yocto-2.2/poky-morty-16.0.0.tar.bz2
> 
> A gpg signed version of these release notes is available at:
> 
> http://downloads.yoctoproject.org/releases/yocto/yocto-2.2/RELEASENOTES

It would be helpful if morty could be added to the stable branch page, with 
clarification on whether jethro is being actively maintained:

  https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance

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

[yocto] [layerindex-web][PATCH 1/4] admin: add an action to duplicate a branch

2016-11-15 Thread Paul Eggleton 
Add an action to duplicate a Branch object, along with all of the
LayerBranches (and LayerMaintainers and LayerDependencies) underneath
it.

Signed-off-by: Paul Eggleton 
---
 layerindex/admin.py | 26 ++
 1 file changed, 26 insertions(+)

diff --git a/layerindex/admin.py b/layerindex/admin.py
index 7339ce1..f50aae4 100644
--- a/layerindex/admin.py
+++ b/layerindex/admin.py
@@ -17,6 +17,32 @@ class LayerDependencyInline(admin.StackedInline):
 
 class BranchAdmin(CompareVersionAdmin):
 model = Branch
+actions = ['duplicate']
+
+def duplicate(self, request, queryset):
+for branch in queryset:
+layerbranches = branch.layerbranch_set.all()
+branch.pk = None
+branch.name += '-copy'
+branch.save()
+for layerbranch in layerbranches:
+layerbranch_maintainers = layerbranch.layermaintainer_set.all()
+layerbranch_dependencies = layerbranch.dependencies_set.all()
+layerbranch.pk = None
+layerbranch.branch = branch
+layerbranch.vcs_last_fetch = None
+layerbranch.vcs_last_rev = ''
+layerbranch.vcs_last_commit = None
+layerbranch.save()
+for layermaintainer in layerbranch_maintainers:
+layermaintainer.pk = None
+layermaintainer.layerbranch = layerbranch
+layermaintainer.save()
+for layerdependency in layerbranch_dependencies:
+layerdependency.pk = None
+layerdependency.layerbranch = layerbranch
+layerdependency.save()
+duplicate.short_description = "Duplicate selected Branches"
 
 class LayerItemAdmin(CompareVersionAdmin):
 list_filter = ['status', 'layer_type']
-- 
2.5.5

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

[yocto] [layerindex-web][PATCH 2/4] utils: fix error in runcmd() if printerr=False

2016-11-15 Thread Paul Eggleton 
If you specified printerr=False we were referring to the output variable
that hadn't been set. Looks like I broke this back in 2013 in
93ce26f21cdbbd8a645792359cde87acf05144d7.

Signed-off-by: Paul Eggleton 
---
 layerindex/utils.py | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/layerindex/utils.py b/layerindex/utils.py
index e3be631..9248077 100644
--- a/layerindex/utils.py
+++ b/layerindex/utils.py
@@ -190,9 +190,9 @@ def runcmd(cmd, destdir=None, printerr=True, logger=None):
 subprocess.check_call(cmd, stdout=out, stderr=out, cwd=destdir, 
shell=True)
 except subprocess.CalledProcessError as e:
 out.seek(0)
+output = out.read()
+output = output.decode('ascii').strip()
 if printerr:
-output = out.read()
-output = output.decode('ascii').strip()
 if logger:
 logger.error("%s" % output)
 else:
-- 
2.5.5

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

[yocto] [layerindex-web][PATCH 3/4] Record and display update logs

2016-11-15 Thread Paul Eggleton 
At the moment it's a bit difficult to get update logs out of the
environment in which the update script is being run. In order to make
the logs more accessible, create a LayerUpdate model to record the
output of update_layer.py separately for each layerbranch and tie the
created LayerUpdates together with a single Update model per session.

We provide two ways to look at this - a Tools->Updates page for
logged-in users, and there's also an "Updates" tab on each layer that is
accessible to anyone; which one is useful depends on whether you are
looking at the index as a whole or an individual layer.

Update records older than 30 days are deleted automatically by default.

Signed-off-by: Paul Eggleton 
---
 TODO  |   2 -
 layerindex/admin.py   |   8 +
 layerindex/migrations/0005_layerupdate.py |  46 +
 layerindex/models.py  |  37 +++-
 layerindex/update.py  | 286 ++
 layerindex/urls.py|  14 +-
 layerindex/urls_branch.py |   4 +-
 layerindex/utils.py   |  13 ++
 layerindex/views.py   |  30 +++-
 settings.py   |   3 +
 templates/base.html   |   1 +
 templates/layerindex/detail.html  |  37 
 templates/layerindex/layerupdate.html |  30 
 templates/layerindex/updatedetail.html|  47 +
 templates/layerindex/updatelist.html  |  57 ++
 15 files changed, 491 insertions(+), 124 deletions(-)
 create mode 100644 layerindex/migrations/0005_layerupdate.py
 create mode 100644 templates/layerindex/layerupdate.html
 create mode 100644 templates/layerindex/updatedetail.html
 create mode 100644 templates/layerindex/updatelist.html

diff --git a/TODO b/TODO
index b5e8974..167715d 100644
--- a/TODO
+++ b/TODO
@@ -35,10 +35,8 @@ Other
 * Create simple script to check for unlisted layer subdirectories in all repos
 * Auto-detect more values from github pages?
 * Ability for submitters to get email notification about publication?
-* Update script still seems not to be always printing layer name on parsing 
warnings/errors
 * Update script could send warnings when parsing layers to maintainers? 
(optional)
 * Click on OE-Classic graph element to go to query?
 * Use bar instead of pie graphs for OE-Classic statistics
 * Ensure OE-Core appears before meta-oe in layer list
 * Ability for reviewers to comment before publishing a layer?
-* Record update & parse errors against recipe/layer
diff --git a/layerindex/admin.py b/layerindex/admin.py
index f50aae4..d25829a 100644
--- a/layerindex/admin.py
+++ b/layerindex/admin.py
@@ -74,6 +74,12 @@ class LayerDependencyAdmin(CompareVersionAdmin):
 class LayerNoteAdmin(CompareVersionAdmin):
 list_filter = ['layer__name']
 
+class UpdateAdmin(admin.ModelAdmin):
+pass
+
+class LayerUpdateAdmin(admin.ModelAdmin):
+list_filter = ['update__started', 'layerbranch__layer__name', 
'layerbranch__branch__name']
+
 class RecipeAdmin(admin.ModelAdmin):
 search_fields = ['filename', 'pn']
 list_filter = ['layerbranch__layer__name', 'layerbranch__branch__name']
@@ -144,6 +150,8 @@ admin.site.register(LayerBranch, LayerBranchAdmin)
 admin.site.register(LayerMaintainer, LayerMaintainerAdmin)
 admin.site.register(LayerDependency, LayerDependencyAdmin)
 admin.site.register(LayerNote, LayerNoteAdmin)
+admin.site.register(Update, UpdateAdmin)
+admin.site.register(LayerUpdate, LayerUpdateAdmin)
 admin.site.register(Recipe, RecipeAdmin)
 admin.site.register(RecipeFileDependency)
 admin.site.register(Machine, MachineAdmin)
diff --git a/layerindex/migrations/0005_layerupdate.py 
b/layerindex/migrations/0005_layerupdate.py
new file mode 100644
index 000..3cf4ab2
--- /dev/null
+++ b/layerindex/migrations/0005_layerupdate.py
@@ -0,0 +1,46 @@
+# -*- coding: utf-8 -*-
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+
+dependencies = [
+('layerindex', '0004_layerdependency_required'),
+]
+
+operations = [
+migrations.CreateModel(
+name='LayerUpdate',
+fields=[
+('id', models.AutoField(auto_created=True, primary_key=True, 
serialize=False, verbose_name='ID')),
+('started', models.DateTimeField()),
+('finished', models.DateTimeField()),
+('errors', models.IntegerField(default=0)),
+('warnings', models.IntegerField(default=0)),
+('log', models.TextField(blank=True)),
+('layerbranch', 
models.ForeignKey(to='layerindex.LayerBranch')),
+],
+),
+migrations.CreateModel(
+name='Update',
+fields=[
+('id', models.AutoField(auto_created=True, primary_key=True, 
serialize=False, verbose_name='ID')),
+('star

[yocto] [layerindex-web][PATCH 4/4] views: support querying class inheritance

2016-11-15 Thread Paul Eggleton 
It's a little crude and certainly not optimal performance-wise, but we
can support querying for recipes that inherit a particular class without
too much trouble. This allows you to add "inherits:cmake" to the query
and have it return only recipes that inherit the cmake class. You can
use more than one inherits: item to filter down to recipes that inherit
all of the specified classes.

Note: this does not otherwise change the behaviour of specifying
multiple words - all of the words other than those that start with
"inherits:" are treated as part of a single phrase that will be searched
for - not separate keywords.

Fixes [YOCTO #9879].

Signed-off-by: Paul Eggleton 
---
 layerindex/views.py | 16 
 1 file changed, 16 insertions(+)

diff --git a/layerindex/views.py b/layerindex/views.py
index 0933bf0..ae0220b 100644
--- a/layerindex/views.py
+++ b/layerindex/views.py
@@ -376,6 +376,22 @@ class RecipeSearchView(ListView):
 _check_url_branch(self.kwargs)
 query_string = self.request.GET.get('q', '')
 init_qs = 
Recipe.objects.filter(layerbranch__branch__name=self.kwargs['branch'])
+
+# Support slightly crude search on inherits field
+query_items = query_string.split()
+inherits = []
+query_terms = []
+for item in query_items:
+if item.startswith('inherits:'):
+inherits.append(item.split(':')[1])
+else:
+query_terms.append(item)
+if inherits:
+# FIXME This is a bit ugly, perhaps we should consider having this 
as a one-many relationship instead
+for inherit in inherits:
+init_qs = init_qs.filter(Q(inherits=inherit) | 
Q(inherits__startswith=inherit + ' ') | Q(inherits__endswith=' ' + inherit) | 
Q(inherits__contains=' %s ' % inherit))
+query_string = ' '.join(query_terms)
+
 if query_string.strip():
 order_by = ('pn', 'layerbranch__layer')
 
-- 
2.5.5

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

[yocto] [PATCH] rmc: Fix include path and type definitions

2016-11-15 Thread Jianxun Zhang 
Add detection of current path for -I option, also update
type definitions for EFI compiling.

Signed-off-by: Jianxun Zhang 
---
 Makefile| 4 +++-
 Makefile.efi| 4 +++-
 inc/rmc_types.h | 9 ++---
 3 files changed, 12 insertions(+), 5 deletions(-)

diff --git a/Makefile b/Makefile
index f152829..6c68a51 100644
--- a/Makefile
+++ b/Makefile
@@ -1,5 +1,7 @@
 # Copyright (C) 2016 Jianxun Zhang 
 
+TOPDIR = $(shell if [ -z "$$PWD" ]; then pwd; else echo "$$PWD"; fi)
+
 RMC_TOOL_SRC := $(wildcard src/*.c)
 RMC_TOOL_OBJ := $(patsubst %.c,%.o,$(RMC_TOOL_SRC))
 
@@ -17,7 +19,7 @@ RMC_INSTALL_BIN_PATH := $(RMC_INSTALL_PREFIX)/bin/
 
 ALL_OBJS := $(RMC_TOOL_OBJ) $(RMCL_OBJ) $(RSMP_OBJ)
 
-CFLAGS := -Wall -O2 -Iinc $(RMC_CFLAGS)
+CFLAGS := -Wall -O2 -I$(TOPDIR)/inc $(RMC_CFLAGS)
 
 all: rmc librmcl librsmp
 
diff --git a/Makefile.efi b/Makefile.efi
index 4c2aada..2af85cb 100644
--- a/Makefile.efi
+++ b/Makefile.efi
@@ -1,5 +1,7 @@
 # Copyright (C) 2016 Jianxun Zhang 
 
+TOPDIR = $(shell if [ -z "$$PWD" ]; then pwd; else echo "$$PWD"; fi)
+
 RMCL_SRC :=$(wildcard src/rmcl/*.c)
 RMCL_OBJ := $(patsubst %.c,%.efi.o,$(RMCL_SRC))
 
@@ -34,7 +36,7 @@ RMC_INSTALL_LIBS_PATH := $(RMC_INSTALL_PREFIX)/lib/
 SHARED_OBJS := src/util/util.efi.o
 ALL_OBJS := $(RMCL_OBJ) $(RSMP_OBJ) $(SHARED_OBJS)
 
-CFLAGS := -DRMC_EFI -Wall -O2 -Iinc -fpic -nostdinc -nostdlib  -fno-builtin 
-std=gnu90 \
+CFLAGS := -DRMC_EFI -Wall -O2 -I$(TOPDIR)/inc -fpic -nostdinc -nostdlib  
-fno-builtin -std=gnu90 \
   -I$(RMC_EFI_HEADER_PREFIX) 
-I$(RMC_EFI_HEADER_PREFIX)/$(RMC_EFI_ARCH) $(RMC_CFLAGS)
 
 all: librmclefi librsmpefi
diff --git a/inc/rmc_types.h b/inc/rmc_types.h
index b6e4521..9154231 100644
--- a/inc/rmc_types.h
+++ b/inc/rmc_types.h
@@ -7,14 +7,17 @@
 #define INC_RMC_TYPES_H_
 
 #ifndef RMC_EFI
+#include 
 #include 
 #include 
 #include 
 #else
 #include 
-/* Fixme: we define (s)size_t here for both 32 and 64 bit because gnu-efi 
doesn't provide these */
-typedef uint64_t size_t;
-typedef uint64_t ssize_t;
+/* we specify -nostdinc in C flag and provide these in rmc
+ * for EFI applications that don't want to use standard headers.
+ */
+typedef unsigned long size_t;
+typedef long ssize_t;
 #endif
 
 typedef uint8_t BYTE;
-- 
2.7.4

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

Re: [yocto] mklibs in USER_CLASSES (Khem Raj)

2016-11-15 Thread Khem Raj 


On 11/15/16 3:56 AM, 신택현 (Taek Hyun Shin) wrote:
> I did use only image-mklibs TT
> 
> And, I did try modify some project make file for mklibs. add *_pic.a
> 
> So, I did resolve not pic file found for error message. just modified package.
> 
> But, other error occurred as follow:
> 
> __dso_handle undefined
> 
> 
> Does mklibs can't support c++? only support c library??
>

Can you check if OE mklib has this patch applied ?

https://lists.debian.org/debian-boot/2013/01/msg00239.html


>  
> 
>  
> 
>  
> 
>  
> 
> /Thanks & Best Regards,/
> 
> /*Wily Taekhyun Shin*/
> 
> 
> *Telechips Inc.*
> 
> *R&D Center / Automotive Group / Linux Team / Research Engineer*
> 
> Tel : +82-2-3443-6792(Ext. 390), M.P : +82-10-4376-5530, E-mail
> : ths...@telechips.com 
> 
> This mail and attachments contain confidential information of Telechips Inc.
> which has its own authority. 
> 
> It is not allowed to disclose,transmit or use this confidential information to
> the third parties without the prior written consent
> of Telechips Inc. by any form or means.
> If you are not the intended recipient, please notify the sender immediately
> and do not disclose the contents and destroy all
> copies of the original message.
> 
> 
>   *--Original Message*
>   Sender : yocto-requ...@yoctoproject.org
>   Received : 2016-11-12 05:02:24
>   To : yocto@yoctoproject.org
>   Title : yocto Digest, Vol 74, Issue 56
> 
> Send yocto mailing list submissions to
> yocto@yoctoproject.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.yoctoproject.org/listinfo/yocto
> or, via email, send a message with subject or body 'help' to
> yocto-requ...@yoctoproject.org
> 
> You can reach the person managing the list at
> yocto-ow...@yoctoproject.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of yocto digest..."
> 
> 
> Today's Topics:
> 
>1. Re: mklibs in USER_CLASSES (Khem Raj)
>2. Re: Buildbot / Autobuilder / custom? (Beth 'pidge' Flanagan)
> 
> 
> --
> 
> Message: 1
> Date: Fri, 11 Nov 2016 10:17:54 -0800
> From: Khem Raj 
> To: ??? (Taek Hyun Shin) ,
> yocto@yoctoproject.org
> Subject: Re: [yocto] mklibs in USER_CLASSES
> Message-ID: <7cdefdbc-baa9-4dfd-f60d-64c0d3c9e...@gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> 
> 
> On 11/11/16 1:22 AM, ??? (Taek Hyun Shin) wrote:
>> Hi,
>> 
>> Somebody help met plz.
>> 
>> 
>> I'm using Yocto Project 2.0
>> 
>> I want to reduce my rootfs due to fast execute binaries.
>> 
>> So, I did apply mklibs using USE_CLASSES
> 
> if you use prelink as well then make sure mklibs appear before prelink in
> USE_CLASSES
> 
>> 
>> But, I got error message as follow:
>> 
>> 
>>  208 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libgmp.so.10
>> ; copying
>> 
>>  209 reducing libgobject-2.0.so.0
>> 
>>  210 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libgobject-2.0.so.0
>> ; copying
>> 
>>  211 reducing libgstreamer-1.0.so.0
>> 
>>  212 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libgstreamer-1.0.so.0
>> ; copying
>> 
>>  213 reducing libhogweed.so.4
>> 
>>  214 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libhogweed.so.4
>> ; copying
>> 
>>  215 reducing libinput.so.10
>> 
>>  216 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libinput.so.10
>> ; copying
>> 
>>  217 reducing libjpeg.so.9
>> 
>>  218 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libjpeg.so.9
>> ; copying
>> 
>>  219 reducing liblog.so
>> 
>>  220 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//liblog.so
>>  ;
>> copying
>> 
>>  221 reducing libm.so.6
>> 
>>  222 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/lib//libm.so.6 ;
>> copying
>> 
>>  223 reducing libmenuw.so.5
>> 
>>  224 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/usr/lib//libmenuw.so.5
>> ; copying
>> 
>>  225 reducing libmount.so.1
>> 
>>  226 No pic file found for
>> /home/B110141/works/Yocto/build/tcc8021/tmp/sysroots/tcc8021/lib//libmount.so.1
>>  ;
>> copying
>> 
>>  227 reducing libmtdev.so.1
>> 
>> 
>> How can I create the pic file each libraries
>> 
>> 
>> Help me plz TT
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> /Thanks & Best Regards,/
>> 
>> /*Wily Taekhyun Shin*/
>> 
>> 
>> *Telechips Inc.*
>> 
>> *R&D Center / Automotive Group / Linux Team / Research Engineer*
>> 
>> Tel : +82-2-3443-6792(Ext. 390), M.P : +82-10-4376-5530, E-mail
>> : ths...@telechips.com 
>> 
>> This mail and attachments contain confidential

Re: [yocto] New error

2016-11-15 Thread Khem Raj 
Can you test out this patch for OE-Core

https://github.com/kraj/openembedded-core/commit/b2d345d0217db0c2dda3b9b40824829116599568


On 11/15/16 4:41 AM, Gary Thomas wrote:
> I just ran a new build for one of my PowerPC targets and I'm getting errors
> like these:
> 
> ERROR: openssh-7.3p1-r0 do_package: runstrip:
> ''powerpc-amltd-linux-gnuspe-strip' --remove-section=.comment
> --remove-section=.note
> '/build/diskstation_2016-11-15/tmp/work/p1022ds-amltd-linux-gnuspe/openssh/7.3p1-r0/package/usr/bin/scp.openssh''
> strip command failed with 1 (b'powerpc-amltd-linux-gnuspe-strip:
> /build/diskstation_2016-11-15/tmp/work/p1022ds-amltd-linux-gnuspe/openssh/7.3p1-r0/package/usr/bin/strW48QK:
> Not enough room for program headers, try linking with
> -N\npowerpc-amltd-linux-gnuspe-strip:/build/diskstation_2016-11-15/tmp/work/p1022ds-amltd-linux-gnuspe/openssh/7.3p1-r0/package/usr/bin/strW48QK[.interp]:
> Bad value\n')
> ERROR: coreutils-8.25-r0 do_package: runstrip:
> ''powerpc-amltd-linux-gnuspe-strip' --remove-section=.comment
> --remove-section=.note --strip-unneeded
> '/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/coreutils/8.25-r0/package/usr/lib/coreutils/libstdbuf.so''
> strip command failed with 1 (b'powerpc-amltd-linux-gnuspe-strip:
> /build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/coreutils/8.25-r0/package/usr/lib/coreutils/std1tFcO:
> Not enough room for program headers, try linking with
> -N\npowerpc-amltd-linux-gnuspe-strip:/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/coreutils/8.25-r0/package/usr/lib/coreutils/std1tFcO[.note.gnu.build-id]:
> Bad value\n')
> ERROR: eudev-3.2-r0 do_package: runstrip: ''powerpc-amltd-linux-gnuspe-strip'
> --remove-section=.comment --remove-section=.note --strip-unneeded
> '/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/eudev/3.2-r0/package/lib/libudev.so.1.6.3''
> strip command failed with 1 (b'powerpc-amltd-linux-gnuspe-strip:
> /build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/eudev/3.2-r0/package/lib/stxt1rac:
> Not enough room for program headers, try linking with
> -N\npowerpc-amltd-linux-gnuspe-strip:/build/diskstation_2016-11-15/tmp/work/ppce500v2-amltd-linux-gnuspe/eudev/3.2-r0/package/lib/stxt1rac[.note.gnu.build-id]:
> Bad value\n')
> 
> Actually, I got 438 of them :-(
> 
> Build Configuration:
> BB_VERSION= "1.32.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS= "powerpc-amltd-linux-gnuspe"
> MACHINE   = "p1022ds"
> DISTRO= "amltd"
> DISTRO_VERSION= "2.2+snapshot-20161115"
> TUNE_FEATURES = "m32 spe ppce500v2"
> TARGET_FPU= "ppc-efd"
> meta  = "master:43e652f3d1fee5ce7fad67e6400315eab1b34270"
> meta-amltd= "master:697b2bc1467a311233f1da362aa4c8a2cccf52bf"
> meta-diskstation  = "master:0839596be89af4da67fb7c5ab41337f1a382e5b5"
> meta-freescale= "master:979d079732949c49f7a859e93278287eb95fa056"
> 
> 
> Questions:
> * What's the best way to fix them?  I assume it's just some
>   compiler/binutils option I need to adjust.  I tried comparing
>   this build against the stock qemuppc, but it got no such errors
>   and I don't see the difference (except for the CPU tuning of
>   e500v2 vs 7400).
> * If these are labeled 'ERROR', why do the packages continue
>   to be built?  Indeed, I ended up with a complete build image
>   (which I've not been able to test yet so I don't know if these
>   errors actually break things)
> 
> Thanks for any pointers
> 



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] rmc: Fix include path and type definitions

2016-11-15 Thread Khem Raj 


On 11/15/16 8:56 PM, Jianxun Zhang wrote:
> Add detection of current path for -I option, also update
> type definitions for EFI compiling.
> 
> Signed-off-by: Jianxun Zhang 
> ---
>  Makefile| 4 +++-
>  Makefile.efi| 4 +++-
>  inc/rmc_types.h | 9 ++---
>  3 files changed, 12 insertions(+), 5 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index f152829..6c68a51 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,5 +1,7 @@
>  # Copyright (C) 2016 Jianxun Zhang 
>  
> +TOPDIR = $(shell if [ -z "$$PWD" ]; then pwd; else echo "$$PWD"; fi)
> +
>  RMC_TOOL_SRC := $(wildcard src/*.c)
>  RMC_TOOL_OBJ := $(patsubst %.c,%.o,$(RMC_TOOL_SRC))
>  
> @@ -17,7 +19,7 @@ RMC_INSTALL_BIN_PATH := $(RMC_INSTALL_PREFIX)/bin/
>  
>  ALL_OBJS := $(RMC_TOOL_OBJ) $(RMCL_OBJ) $(RSMP_OBJ)
>  
> -CFLAGS := -Wall -O2 -Iinc $(RMC_CFLAGS)
> +CFLAGS := -Wall -O2 -I$(TOPDIR)/inc $(RMC_CFLAGS)
>  
>  all: rmc librmcl librsmp
>  
> diff --git a/Makefile.efi b/Makefile.efi
> index 4c2aada..2af85cb 100644
> --- a/Makefile.efi
> +++ b/Makefile.efi
> @@ -1,5 +1,7 @@
>  # Copyright (C) 2016 Jianxun Zhang 
>  
> +TOPDIR = $(shell if [ -z "$$PWD" ]; then pwd; else echo "$$PWD"; fi)
> +
>  RMCL_SRC :=$(wildcard src/rmcl/*.c)
>  RMCL_OBJ := $(patsubst %.c,%.efi.o,$(RMCL_SRC))
>  
> @@ -34,7 +36,7 @@ RMC_INSTALL_LIBS_PATH := $(RMC_INSTALL_PREFIX)/lib/
>  SHARED_OBJS := src/util/util.efi.o
>  ALL_OBJS := $(RMCL_OBJ) $(RSMP_OBJ) $(SHARED_OBJS)
>  
> -CFLAGS := -DRMC_EFI -Wall -O2 -Iinc -fpic -nostdinc -nostdlib  -fno-builtin 
> -std=gnu90 \
> +CFLAGS := -DRMC_EFI -Wall -O2 -I$(TOPDIR)/inc -fpic -nostdinc -nostdlib  
> -fno-builtin -std=gnu90 \
>  -I$(RMC_EFI_HEADER_PREFIX) 
> -I$(RMC_EFI_HEADER_PREFIX)/$(RMC_EFI_ARCH) $(RMC_CFLAGS)

while this patch improves the situation. It would be better if the package
would respect the flags coming from environment and not ignore them as it is
doing here and then synthesizing stuff. Are there other compile scenarios
where its compiled for non-linux targets as well ? when will
RMC_EFI_HEADER_PREFIX not look into sysroot ?

if this makefile was accomodating the environment then bitbake rightly sets up
CFLAGS for cross compiling.

>  
>  all: librmclefi librsmpefi
> diff --git a/inc/rmc_types.h b/inc/rmc_types.h
> index b6e4521..9154231 100644
> --- a/inc/rmc_types.h
> +++ b/inc/rmc_types.h
> @@ -7,14 +7,17 @@
>  #define INC_RMC_TYPES_H_
>  
>  #ifndef RMC_EFI
> +#include 
>  #include 
>  #include 
>  #include 
>  #else
>  #include 
> -/* Fixme: we define (s)size_t here for both 32 and 64 bit because gnu-efi 
> doesn't provide these */
> -typedef uint64_t size_t;
> -typedef uint64_t ssize_t;
> +/* we specify -nostdinc in C flag and provide these in rmc
> + * for EFI applications that don't want to use standard headers.
> + */
> +typedef unsigned long size_t;
> +typedef long ssize_t;
>  #endif
>  
>  typedef uint8_t BYTE;
> 



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto