Re: [yocto] Separate out image generation into a new task

[Markus Volk]

Thank you,

unfortunately this has´t solved the problem for me

> Am 15.01.2016 um 02:56 schrieb Andre McCurdy :
> 
> On Wed, Jan 13, 2016 at 12:36 PM, Markus Volk  wrote:
>> With the recent improvements in the master branch regarding image creation 
>> i´m not able to build usb images anymore.
> 
> This patch might help:
> 
>  
> http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115474.html
> 
>> do_image_ext3 and do_image_jffs2 works well, then i´m getting this error 
>> message:
>> 
>> Log data follows:
>> | DEBUG: Executing python function set_image_size
>> | DEBUG: Python function set_image_size finished
>> | DEBUG: Executing shell function do_image_hd1-usbimg
>> | 
>> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/run.do_image_hd1-usbimg.126432:
>>  108: 
>> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/run.do_image_hd1-usbimg.126432:
>>  do_image_hd1-usbimg: not found
>> | WARNING: exit code 127 from a shell command.
>> | ERROR: Function failed: do_image_hd1-usbimg (log file is located at 
>> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/log.do_image_hd1-usbimg.126432)
>> ERROR: Task 18 
>> (/home/flk/yocto/poky/meta-neutrino/recipes-images/images/neutrino-image.bb, 
>> do_image_hd1-usbimg) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 2349 tasks of which 742 didn't need to be 
>> rerun and 1 failed.
>> Waiting for 0 running tasks to finish:
>> 
>> Summary: 1 task failed:
>>  /home/flk/yocto/poky/meta-neutrino/recipes-images/images/neutrino-image.bb, 
>> do_image_hd1-usbimg
>> Summary: There were 3 WARNING messages shown.
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>> 
>> 
>> Until now i used this file for building an usb image (very similar to the 
>> way the sd image for raspberrypi is created):
>> 
>> usb_image-hd1.bbclass:
>> 
>> inherit image_types
>> 
>> #
>> ## this is heavily inspired by the raspberry pi sdimage class.
>> #
>> # Create an image that can by written onto an USB stick.
>> #
>> # The disk layout used is:
>> #
>> #0  -> IMAGE_ROOTFS_ALIGNMENT - reserved for other 
>> data
>> #IMAGE_ROOTFS_ALIGNMENT -> BOOT_SPACE - u-boot script and 
>> kernel
>> #BOOT_SPACE -> USBIMG_SIZE - rootfs
>> #
>> # Default Free space = 
>> 1.3x
>> # Use 
>> IMAGE_OVERHEAD_FACTOR to add more space
>> # <->
>> #1MiB  20MiB   USBIMG_ROOTFS
>> # <---> <--> <-->
>> #    
>> # | IMAGE_ROOTFS_ALIGNMENT | BOOT_SPACE | ROOTFS_SIZE|
>> #    
>> # ^^^^
>> # ||||
>> # 0  1MiB 1MiB + 20MiB   1MiB + 20Mib + 
>> USBIMG_ROOTFS
>> 
>> # This image depends on the rootfs image
>> IMAGE_TYPEDEP_hd1-usbimg = "${USBIMG_ROOTFS_TYPE}"
>> 
>> # Boot partition volume id
>> BOOTDD_VOLUME_ID ?= "KERNEL"
>> 
>> # Boot partition size [in KiB] (will be rounded up to IMAGE_ROOTFS_ALIGNMENT)
>> BOOT_SPACE ?= "20480"
>> 
>> # Set alignment to 4MB [in KiB]
>> IMAGE_ROOTFS_ALIGNMENT = "1024"
>> 
>> # Use an uncompressed ext3 by default as rootfs
>> USBIMG_ROOTFS_TYPE ?= "ext3"
>> USBIMG_ROOTFS = "${IMAGE_NAME}.rootfs.${USBIMG_ROOTFS_TYPE}"
>> 
>> IMAGE_DEPENDS_hd1-usbimg = " \
>>parted-native \
>>mtools-native \
>>dosfstools-native \
>>virtual/kernel \
>> "
>> 
>> # USB image name
>> USBIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.hd1-usbimg"
>> 
>> # Compression method to apply to USBIMG after it has been created. Supported
>> # compression formats are "gzip", "bzip2" or "xz". The original .hd1-usbimg 
>> file
>> # is kept and a new compressed file is created if one of these compression
>> # formats is chosen. If USBIMG_COMPRESSION is set to any other value it is
>> # silently ignored.
>> #USBIMG_COMPRESSION ?= ""
>> 
>> # Additional files and/or directories to be copied into the vfat partition 
>> from the IMAGE_ROOTFS.
>> FATPAYLOAD ?= ""
>> 
>> IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
>> 
>> IMAGE_CMD_hd1-usbimg () {
>> 
>># Align partitions
>>BOOT_SPACE_ALIGNED=$(expr ${BOOT_SPACE} + ${IMAGE_ROOTFS_ALIGNMENT} - 
>> 1)
>>BOOT_SPACE_ALIGNED=$(expr ${BOOT_SPACE_ALIGNED} - 
>> ${BOOT_SPACE_ALIGNED} % ${IMAGE_ROOTFS_ALIGNMENT})
>>ROOTFS_SIZE=`du -bks ${USBIMG_ROOTFS} | awk '{print $1}'`
>># Round up RootFS size to the alignm

Re: [yocto] Separate out image generation into a new task

[Andre McCurdy]

On Wed, Jan 13, 2016 at 12:36 PM, Markus Volk  wrote:
> With the recent improvements in the master branch regarding image creation 
> i´m not able to build usb images anymore.

This patch might help:

  
http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115474.html

> do_image_ext3 and do_image_jffs2 works well, then i´m getting this error 
> message:
>
> Log data follows:
> | DEBUG: Executing python function set_image_size
> | DEBUG: Python function set_image_size finished
> | DEBUG: Executing shell function do_image_hd1-usbimg
> | 
> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/run.do_image_hd1-usbimg.126432:
>  108: 
> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/run.do_image_hd1-usbimg.126432:
>  do_image_hd1-usbimg: not found
> | WARNING: exit code 127 from a shell command.
> | ERROR: Function failed: do_image_hd1-usbimg (log file is located at 
> /home/flk/yocto/poky/build-zee/tmp-glibc/work/coolstream_hd1-oe-linux-gnueabi/neutrino-image/1.0-r0/temp/log.do_image_hd1-usbimg.126432)
> ERROR: Task 18 
> (/home/flk/yocto/poky/meta-neutrino/recipes-images/images/neutrino-image.bb, 
> do_image_hd1-usbimg) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 2349 tasks of which 742 didn't need to be 
> rerun and 1 failed.
> Waiting for 0 running tasks to finish:
>
> Summary: 1 task failed:
>   /home/flk/yocto/poky/meta-neutrino/recipes-images/images/neutrino-image.bb, 
> do_image_hd1-usbimg
> Summary: There were 3 WARNING messages shown.
> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>
>
> Until now i used this file for building an usb image (very similar to the way 
> the sd image for raspberrypi is created):
>
> usb_image-hd1.bbclass:
>
> inherit image_types
>
> #
> ## this is heavily inspired by the raspberry pi sdimage class.
> #
> # Create an image that can by written onto an USB stick.
> #
> # The disk layout used is:
> #
> #0  -> IMAGE_ROOTFS_ALIGNMENT - reserved for other 
> data
> #IMAGE_ROOTFS_ALIGNMENT -> BOOT_SPACE - u-boot script and 
> kernel
> #BOOT_SPACE -> USBIMG_SIZE - rootfs
> #
> # Default Free space = 
> 1.3x
> # Use 
> IMAGE_OVERHEAD_FACTOR to add more space
> # <->
> #1MiB  20MiB   USBIMG_ROOTFS
> # <---> <--> <-->
> #    
> # | IMAGE_ROOTFS_ALIGNMENT | BOOT_SPACE | ROOTFS_SIZE|
> #    
> # ^^^^
> # ||||
> # 0  1MiB 1MiB + 20MiB   1MiB + 20Mib + 
> USBIMG_ROOTFS
>
> # This image depends on the rootfs image
> IMAGE_TYPEDEP_hd1-usbimg = "${USBIMG_ROOTFS_TYPE}"
>
> # Boot partition volume id
> BOOTDD_VOLUME_ID ?= "KERNEL"
>
> # Boot partition size [in KiB] (will be rounded up to IMAGE_ROOTFS_ALIGNMENT)
> BOOT_SPACE ?= "20480"
>
> # Set alignment to 4MB [in KiB]
> IMAGE_ROOTFS_ALIGNMENT = "1024"
>
> # Use an uncompressed ext3 by default as rootfs
> USBIMG_ROOTFS_TYPE ?= "ext3"
> USBIMG_ROOTFS = "${IMAGE_NAME}.rootfs.${USBIMG_ROOTFS_TYPE}"
>
> IMAGE_DEPENDS_hd1-usbimg = " \
> parted-native \
> mtools-native \
> dosfstools-native \
> virtual/kernel \
> "
>
> # USB image name
> USBIMG = "${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.hd1-usbimg"
>
> # Compression method to apply to USBIMG after it has been created. Supported
> # compression formats are "gzip", "bzip2" or "xz". The original .hd1-usbimg 
> file
> # is kept and a new compressed file is created if one of these compression
> # formats is chosen. If USBIMG_COMPRESSION is set to any other value it is
> # silently ignored.
> #USBIMG_COMPRESSION ?= ""
>
> # Additional files and/or directories to be copied into the vfat partition 
> from the IMAGE_ROOTFS.
> FATPAYLOAD ?= ""
>
> IMAGEDATESTAMP = "${@time.strftime('%Y.%m.%d',time.gmtime())}"
>
> IMAGE_CMD_hd1-usbimg () {
>
> # Align partitions
> BOOT_SPACE_ALIGNED=$(expr ${BOOT_SPACE} + ${IMAGE_ROOTFS_ALIGNMENT} - 
> 1)
> BOOT_SPACE_ALIGNED=$(expr ${BOOT_SPACE_ALIGNED} - 
> ${BOOT_SPACE_ALIGNED} % ${IMAGE_ROOTFS_ALIGNMENT})
> ROOTFS_SIZE=`du -bks ${USBIMG_ROOTFS} | awk '{print $1}'`
> # Round up RootFS size to the alignment size as well
> ROOTFS_SIZE_ALIGNED=$(expr ${ROOTFS_SIZE} + ${IMAGE_ROOTFS_ALIGNMENT} 
> - 1)
> ROOTFS_SIZE_ALIGNED=$(expr ${ROOTFS_SIZE_ALIGNED} - 
> ${ROOTFS_SIZE_ALIGNED} % ${IMAGE_ROOTFS_ALIGNMENT})
> USBIMG_SIZE=$(expr ${

[yocto] qmlvideo: no service found for - "org.qt-project.qt.mediaplayer"

[Charles Chau]

Hello,

I am using the i.MX6 Dual Core. I have followed this recipe 
and 
have a working image with GStreamer.


However, I am having trouble to get the Qt qmlvideo player to play video.
GStreamer can play video with sound fine.  But it seems to be missing 
some library to link to the Qt.


Please advise; what component am I missing?

Thank you,

/qrc:///qml/qmlvideo/DisableScreenSaver.qml:47:9: Cannot assign to 
non-existent property "screenSaverInhibited"//

//[qmlvideo] performanceLoader.init logging false visible true//
//[frequencymonitor] FrequencyMonitor::FrequencyMonitor //
//[frequencymonitor] FrequencyMonitor::FrequencyMonitor //
//[qmlvideo] main.onSceneSourceChanged source VideoFullScreen.qml//
//[qmlvideo] Content.initialize: contentType video//
//[qmlvideo] Content.initialize: loading VideoItem.qml//
//defaultServiceProvider::requestService(): no service found for - 
"org.qt-project.qt.mediaplayer" //

//[qmlvideo] Content.start//
//[qmlvideo] Content.initialize: complete//
//[qmlvideo] VideoItem.onError error 5 errorString The QMediaPlayer 
object does not have a valid service//

//[qmlvideo] Content.onFatalError//
//[qmlvideo] Content.stop/

--
Charles Chau

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

Re: [yocto] How to change the order of package installation

[RayBloodworth]

Hi, Raj
   Thanks for your reply!   I will try another way:   Merging /bin and /usr/bin 
at the last step of do_rootfs.
   Thanks!
Subject: Re: [yocto] How to change the order of package installation
From: raj.k...@gmail.com
Date: Thu, 14 Jan 2016 09:47:09 -0800
CC: yocto@yoctoproject.org
To: k870818...@outlook.com


On Jan 14, 2016, at 1:58 AM, RayBloodworth  wrote:Hi, 
everyone
   I'm using the dizzy branch of freescale yocto project to build image. When 
do_rootfs is done, I found that package "base-files" wasn't the first order of 
installation.Since I want do some modify like "/bin -> /usr/bin" in 
"base-files", package "base-files" must be the first order of installation.   
Could anyone help me with this issue?
There is a separate thread going on about merging /usr and /I am not sure what 
you want to do but symlinking /bin and /usr/bin might involve more thatjust 
post processing.

Best regards,Ray-- ___yocto mailing 
listyocto@yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto
  -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [Toaster] Production Instance Setup

[Rudolf J Streif]

Hi Everyone:

I am trying to set up Toaster in a production environment with Apache etc. The 
web server setup is ok. It is running builds where I am currently stuck.

I am using the Jethro branch from the git repo.

According to step 7 in [1] one needs to start

/var/www/toaster/poky/bitbake/lib/toaster/manage.py runbuilds

to start the runner service to dispatch builds. If there are currently no 
pending builds (non yet created using the web UI) then running this command 
immediately returns. The command gets dispatched to

poky/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py

In its command help it states:

14: help= "Schedules and executes build requests as possible. Does not 
return (interrupt with Ctrl-C)"

However, that is apparently not the case because if there is not build request 
pending then

35:try:
36:# select the build environment and the request to build
37:   br = self._selectBuildRequest()
38:except IndexError as e:
39:logger.debug("runbuilds: No build request")
40:return

If you use the web UI and schedule (start) a build first and then execute 
runbuilds, then the command eventually fails with:

2016-01-14 21:37:54,086 DEBUG lbc_shellcmmd: () git remote -v
Traceback (most recent call last):
  File 
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py",
 line 59, in schedule
bec.triggerBuild(br.brbitbake_set.all(), br.brlayer_set.all(), 
br.brvariable_set.all(), br.brtarget_set.all())
  File 
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py",
 line 365, in triggerBuild
self.setLayers(bitbake, layers, targets)
  File 
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py",
 line 229, in setLayers
for remotes in self._shellcmd("git remote -v", 
self.be.sourcedir).split("\n"):
  File 
"/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py",
 line 61, in _shellcmd
p = subprocess.Popen(command, cwd = cwd, shell=True, 
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
  File "/usr/lib64/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
  File "/usr/lib64/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory: ''

This is because the BuildEnvironment object in the database has empty fields 
for Sourcedir and Builddir. One can fix that by going into the Django admin 
interface and enter paths into these fields of the one BuildEnvironment object 
that is in the database.

Once the paths are entered and the build is started again then it breaks where 
runbuilds apparently waits for the Bitbake server to be available:

2016-01-14 22:14:54,565 DEBUG lbc_shellcmmd: (/home/fedora/source) bash -c 
"source 
/home/fedora/source/_toaster_clones/_git___git.yoctoproject.org_poky_master/oe-init-build-env
 /home/fedora/build 2>&1 >toaster_server.log && bitbake --read 
/home/fedora/build/conf/toaster-pre.conf --postread 
/home/fedora/build/conf/toaster.conf --server-only -t xmlrpc -B 0.0.0.0:0 2>&1 
>>toaster_server.log "
2016-01-14 22:14:55,540 DEBUG localhostbecontroller: shellcmd success
2016-01-14 22:14:55,540 DEBUG localhostbecontroller: Found bitbake server port 
33438

2016-01-14 22:14:55,543 DEBUG localhostbecontroller: Waiting bitbake server to 
start

... repeated 50 times ...

2016-01-14 22:15:20,595 ERROR runbuilds: Error launching build 
localhostbecontroller: Bitbake server did not start in 25 seconds, aborting 
(Error: '

That is in the file 
/var/www/toaster/poky/bitbake/lib/toaster/bldcontrol/localhostbecontroller.py 
at lines:

146 while not started and retries < 50:
147 started = _toaster_ui_started(toaster_ui_log_filepath, 
toaster_ui_log_filelength)
148 import time
149 logger.debug("localhostbecontroller: Waiting bitbake server 
to start")
150 time.sleep(0.5)
151 retries += 1

The function _toaster_ui_started() that checks if Bitbake is running is defined 
as:

133 def _toaster_ui_started(filepath, filepos = 0):
134 if not os.path.exists(filepath):
135 return False
136 with open(filepath, "r") as f:
137 f.seek(filepos)
138 for line in f:
139 if line.startswith("NOTE: ToasterUI waiting for 
events"):
140 return True
141 return False
 
Apparently, it is looking for a line to start with the string "NOTE: ToasterUI 
waiting for events" in the file toaster_ui.log which is located inside the 
build environment that is initialized with oe-init-build-env. I grepped the 
Poky code base for that string and could not find any code module that ever 
writes that string into any file. What the file does contain though is a lin

Re: [yocto] Package naming "exceptions" in Yocto

[Paul Eggleton]

Hi Elena,

On Thu, 14 Jan 2016 07:43:19 Reshetova, Elena wrote:
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel".
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check.
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can.

FYI we do have meta/conf/distro/include/distro_alias.inc which sets 
DISTRO_PN_ALIAS for each recipe, which is intended to help map to the names 
used in other distros. Will that work?

Cheers,
Paul

-- 

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

Re: [yocto] Package naming "exceptions" in Yocto

[Khem Raj]

Elena

> On Jan 13, 2016, at 11:43 PM, Reshetova, Elena  
> wrote:
> 
> Hi,
> 
> I have a small question about “exceptional” names of packages in yocto/OE. 
> Kernel package is being one example with the name “linux-yocto” vs.  
> traditional “linux_kernel”.


This just happens to be that Yocto project maintain a reference kernel and its 
called linux-yocto just following the naming conventions that are in use for 
kernel trees ( linux- ) e.g. linux-stable and so on
OE infra provides virtuals that we use to have pluggable kernels or other 
packages e.g. virtual/kernel for kernel and there are other packages which are 
using this mechanism too.

> Are there more such yocto-specific packages (of course excluding FW and other 
> bsp-related packages)? A look over the package list didn’t reveal any, but I 
> wanted to double check.
> 

yocto project does have more tools e.g. cross-prelink etc. there is no general 
naming convention of something-yocto for packages that project maintains
just check git.yoctoproject.org for number of components.

> The reason I am asking is that in case when we try to determine the package 
> CVEs against the NVD database, in these particular exception cases, we 
> probably want to check not only “linux-yocto”, but also “linux_kernel” open 
> package CVEs with regards to specified version to make sure we cover as much 
> as we can.

it probably is a general problem for end users since they may not use 
linux-yocto to provide the kernel on system but some other name but in the end 
they are kernels. may be some tooling to encode this in recipe would be good.


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH][coreutils] Add attr build dependency

[Khem Raj]

Scott

Thanks for patch. You might want to send into to oe-core mailing list.

> On Jan 14, 2016, at 6:54 AM, Scott Ellis  wrote:
> 
> Fixes this warning:
> 
> WARNING: QA Issue: coreutils rdepends on libattr, but it isn't a build 
> dependency? [build-deps]
> 
> Signed-off-by: Scott Ellis 
> ---
> meta/recipes-core/coreutils/coreutils_8.24.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-core/coreutils/coreutils_8.24.bb 
> b/meta/recipes-core/coreutils/coreutils_8.24.bb
> index f042346..47a25f3 100644
> --- a/meta/recipes-core/coreutils/coreutils_8.24.bb
> +++ b/meta/recipes-core/coreutils/coreutils_8.24.bb
> @@ -7,7 +7,7 @@ BUGTRACKER = "http://debbugs.gnu.org/coreutils";
> LICENSE = "GPLv3+"
> LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504\
> 
> file://src/ls.c;beginline=5;endline=16;md5=38b79785ca88537b75871782a2a3c6b8"
> -DEPENDS = "gmp libcap"
> +DEPENDS = "attr gmp lib cap”

while this fix is good. We can make this into a packageconfig knob

PACKAGECONFIG[attr] = "--enable-something,--disable-something,attr,"

> DEPENDS_class-native = ""
> 
> inherit autotools gettext texinfo
> --
> 2.5.0
> 
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to change the order of package installation

[Khem Raj]

> On Jan 14, 2016, at 1:58 AM, RayBloodworth  wrote:
> 
> Hi, everyone
> 
>I'm using the dizzy branch of freescale yocto project to build image. When 
> do_rootfs is done, I found that package "base-files" wasn't the first order 
> of installation.
>Since I want do some modify like "/bin -> /usr/bin" in "base-files", 
> package "base-files" must be the first order of installation.
>Could anyone help me with this issue?

There is a separate thread going on about merging /usr and /
I am not sure what you want to do but symlinking /bin and /usr/bin might 
involve more that
just post processing.

> 
> Best regards,
> Ray
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org 
> https://lists.yoctoproject.org/listinfo/yocto 
> 


signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-java] openjdk-8 fail to build

[Stef Boerrigter]

Hi,

What version of Yocto are you using?
I'm using 1.7.1 version with only the patch i described in my previous
answer.
When using it on the master of meta-java i got it working without any
issues.. You mentioned you use another patch as well?

Regards

2016-01-13 18:46 GMT+01:00 Federico Pietro Briata :

> Hi again,
> looking to the above error on Makefile, seems there is still something
> wrong with autotools
>
>
> cat
> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile
> # This Makefile was generated by configure Tue Jan 12 22:44:00 CET 2016
> # GENERATED FILE, DO NOT EDIT
>
> SPEC:=/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/build/linux-x86_64-normal-server-release/spec.gmk
> include
> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile
>
> so the build stuck here in this loop I think.
>
> regards
> Federico
>
> 2016-01-12 17:41 GMT+01:00 Federico Pietro Briata :
>
>> Hi Stef,
>> Thanks, I've tried to apply that patch and also
>>
>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=527b28c10955daf0387597020d69593ce24bcaa4
>>
>> and now I'm getting this:
>>
>> ERROR: Function failed: do_compile (log file is located at
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_compile.15889)
>> ERROR: Logfile of failure stored in:
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_compile.15889
>> Log data follows:
>> | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
>> 'bit-64', 'x86_64-linux', 'common']
>> | DEBUG: Executing shell function do_compile
>> | NOTE: make
>> OE_CFLAGS=-isystem/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/include
>> -O2 -pipe -DHEADLESS=true
>> OE_CPPFLAGS=-isystem/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/include
>> -DHEADLESS=true
>> OE_CXXFLAGS=-isystem/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/include
>> -O2 -pipe -DHEADLESS=true
>> OE_LDFLAGS=-L/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/lib
>> -L/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/lib
>> -Wl,-rpath-link,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/lib
>> -Wl,-rpath-link,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/lib
>> -Wl,-rpath,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/lib
>> -Wl,-rpath,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/lib
>> -Wl,-O1 BUILD_HEADLESS_ONLY=1 BUILD_HEADLESS=true BUILD_SOUNDLESS_ONLY=1
>> X11_NOT_NEEDED=1 CUPS_NOT_NEEDED=1 ALSA_NOT_NEEDED=1 PULSE_NOT_NEEDED=1
>> MAKE_VERBOSE=y VERBOSE=-s LOG_LEVEL=trace QUIETLY= images
>> |
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile:27:
>> *** Too many open files.  Stop.
>> | ERROR: oe_runmake failed
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_compile (log file is located at
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_compile.15889)
>> ERROR: Task 207
>> (/home/federico/yocto/imx6/R6.0/sources/meta-java/recipes-core/openjdk/
>> openjdk-8-native_72b05.bb, do_compile) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 1469 tasks of which 1237 didn't need to be
>> rerun and 1 failed.
>> No currently running tasks (1469 of 1483)
>>
>> Summary: 1 task failed:
>>   /home/federico/yocto/imx6/R6.0/sources/meta-java/recipes-core/openjdk/
>> openjdk-8-native_72b05.bb, do_compile
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>
>> thanks and regards
>> federico
>>
>> 2015-12-19 10:38 GMT+01:00 Stef :
>>
>>> Federico Pietro Briata  writes:
>>>
>>> >
>>> >
>>> >
>>> > Hi All,
>>> > I'm trying to build openjdk-8 but I'm stuck.my current setup does not
>>> define anything for:#PREFERRED_PROVIDER_virtual/java-
>>> native#PREFERRED_PROVIDER_virtual/javac-native
>>> >
>>> > follow the log error
>>> >
>>> >
>>> >
>>> > ERROR: Function failed: do_configure (log file is located at
>>> /home/federico/yocto/imx6/R6.0/build-imx6-mx6quad/tmp/work/x86_64-
>>> linux/openjdk-8-native/72b05-r0/temp/log.do_configure.27024)ERROR:
>>> Logfile of failure stored in: /home/federico/yocto/imx6/R6.0/build-imx6-
>>> mx6quad/tmp/work/x86_64-linux/open

Re: [yocto] [AUH] gpgme: upgrading to 1.6.0 SUCCEEDED

[Anibal Limon]

On 01/13/2016 02:19 PM, Burton, Ross wrote:
> On 13 January 2016 at 20:03, Paul Eggleton 
> wrote:
> 
>> I'd question the value of -a as well; the tool is supposed to be smart
>> enough
>> to show you the things that matter and hide everything else by default. If
>> it's not doing that effectively then we should fix it.

Now i made the changes for generate the two buildhistories simple and
full see gpgme examples attached. I'm fixing the license diff issue
before send the patchset.


>>
> 
> If this is turning into a "how can we make buildhistory-diff better" thread
> then I'd love it if there were a way to hide PKGR changes.  I've a PR
> service running locally but don't really care if a PR changed in the
> context of diffs

If we don't use -a option the PKGR changes are not shown. I don't know
if buildhistory-diff needs another improvements :D.


> 
> Ross
> 


alimon
packages/i586-poky-linux/gpgme/gpgme-pthread: FILELIST: removed 
"/usr/lib/libgpgme-pthread.so.11.13.3" added 
"/usr/lib/libgpgme-pthread.so.11.14.0"
  * PV changed from "1.5.4" to "1.6.0"
packages/i586-poky-linux/gpgme/gpgme-pthread: RPROVIDES: removed "1.5.4" added 
"1.6.0"
  * PV changed from "1.5.4" to "1.6.0"
packages/i586-poky-linux/gpgme/gpgme: FILELIST: removed 
"/usr/lib/libgpgme.so.11.13.3" added "/usr/lib/libgpgme.so.11.14.0"
  * PV changed from "1.5.4" to "1.6.0"
packages/i586-poky-linux/gpgme/gpgme-dbg: PV changed from "1.5.4" to "1.6.0"
packages/i586-poky-linux/gpgme/gpgme-dbg: FILELIST: removed 
"/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/assuan-support.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/encrypt.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/dirinfo.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/error.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/ath-pthread.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-gpg.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/ops.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/posix-io.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/data-identify.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/parsetlv.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/opassuan.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-assuan.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/wait-global.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/sig-notation.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/data-compat.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/data.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/posix-util.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/data-fd.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/ath.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/vfs-mount.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-spawn.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/get-env.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/ath.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-gpgconf.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/conversion.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/delete.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-g13.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/passphrase.c 
/usr/src/debug/gpgme/1.5.4-r0/build/src/gpgme.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/data-mem.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/status-table.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/data-user.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/getauditlog.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/genkey.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/trust-item.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-backend.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/priv-io.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/encrypt-sign.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/decrypt-verify.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/util.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/import.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/engine-uiserver.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/wait-user.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/wait.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/debug.h 
/usr/lib/.debug/libgpgme-pthread.so.11.13.3 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/gpgconf.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/gpgme.c 
/usr/lib/.debug/libgpgme.so.11.13.3 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/edit.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/debug.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/wait.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/key.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/sema.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/spawn.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/gpgme-tool.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/export.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/context.h 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/src/verify.c 
/usr/src/debug/gpgme/1.5.4-r0/gpgme-1.5.4/sr

[yocto] [meta-raspberrypi][PATCH v2 7/7] pitft: Add PiTFT22 support

[Petter Mabäcker]

- Add support to build overlays for PiTFT22 in the kernel.
- Setup a basic configuration for the driver

The PiTFT22 support is optional and can be enabled by adding below in
local.conf:

MACHINE_FEATURES += "pitft pitft22"

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README |   9 ++
 conf/machine/include/rpi-base.inc  |   1 +
 recipes-bsp/bootfiles/rpi-config_git.bb|   7 ++
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   4 +-
 7 files changed, 243 insertions(+), 3 deletions(-)
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

diff --git a/README b/README
index 6a6c398..f5b155f 100644
--- a/README
+++ b/README
@@ -170,6 +170,15 @@ MACHINE_FEATURES += "pitft"
 NOTE: To get this working the overlay for the PiTFT model must be build,
   added and specified as well (dtoverlay= in config.txt)
 
+Below is a list of currently supported PiTFT models in meta-raspberrypi,
+the modelname should be added as a MACHINE_FEATURES in local.conf like below:
+
+   - MACHINE_FEATURES .= "pitft "
+
+List of currently supported models
+---
+pitft22
+
 2.L. Images
 ===
 * rpi-hwup-image
diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index c8f6cd6..27f09ad 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -31,6 +31,7 @@ KERNEL_DEVICETREE ?= " \
 overlays/iqaudio-dac-overlay.dtb \
 overlays/iqaudio-dacplus-overlay.dtb \
 overlays/lirc-rpi-overlay.dtb \
+overlays/pitft22-overlay.dtb \
 overlays/pps-gpio-overlay.dtb \
 overlays/w1-gpio-overlay.dtb \
 overlays/w1-gpio-pullup-overlay.dtb \
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index 236a359..631ff42 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -16,6 +16,7 @@ S = "${WORKDIR}/git"
 PR = "r4"
 
 PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+PITFT22="${@bb.utils.contains("MACHINE_FEATURES", "pitft22", "1", "0", d)}"
 
 inherit deploy
 
@@ -80,6 +81,12 @@ do_deploy() {
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+# PiTFT22 display support
+if [ "${PITFT22}" = "1" ]; then
+echo "# Enable PITFT22 display" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtoverlay=pitft22,rotate=270,speed=3200,txbuflen=32768" 
>>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
diff --git 
a/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
new file mode 100644
index 000..fa73599
--- /dev/null
+++ 
b/recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
@@ -0,0 +1,110 @@
+From 2f44861e2a2d651a9aa62a75343a032fee33e93b Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Petter=20Mab=C3=A4cker?= 
+Date: Fri, 8 Jan 2016 09:02:44 +0100
+Subject: [PATCH] dts: add overlay for pitft22 in linux 3.18
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+Upstream-Status: Pending
+
+Add the pitft22 overlay from adafruit Adafruit-Pi-Kernel-o-Matic repo:
+https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic
+
+Signed-off-by: Petter Mabäcker 
+---
+ arch/arm/boot/dts/overlays/Makefile|  1 +
+ arch/arm/boot/dts/overlays/pitft22-overlay.dts | 69 ++
+ 2 files changed, 70 insertions(+)
+ create mode 100755 arch/arm/boot/dts/overlays/pitft22-overlay.dts
+
+diff --git a/arch/arm/boot/dts/overlays/Makefile 
b/arch/arm/boot/dts/overlays/Makefile
+index c766616..1eaaf81 100644
+--- a/arch/arm/boot/dts/overlays/Makefile
 b/arch/arm/boot/dts/overlays/Makefile
+@@ -27,6 +27,7 @@ dtb-$(RPI_DT_OVERLAYS) += mcp2515-can0-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mmc-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += mz61581-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += piscreen-overlay.dtb
++dtb-$(RPI_DT_OVERLAYS) += pitft22-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pitft28-resistive-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += pps-gpio-overlay.dtb
+ dtb-$(RPI_DT_OVERLAYS) += rpi-dac-overlay.dtb
+diff --git a/arch/arm/boot/dts/overlays/pitft22-overlay.dts 
b/arch/arm/boot/dts/overlays/pitft22-overlay.dts
+new file mode 100755
+index 000..894ba22
+--- /dev/null

[yocto] [meta-raspberrypi][PATCH v2 0/7] Various upgrade/fixes from Technux

[Petter Mabäcker]

Various fixes from Technux, with focus on PiTFT support.

Major changes from v1 is that after feedback, MACHINE_FEATURES is used to
enable/disable pitft support instead of MACHINEOVERRIDES.

Petter Mabäcker (7):
  README: Add SPI bus chapter to content
  .gitignore: Ignore .swp files
  linux-raspberrypi: Update 4.1 recipe to 4.1.15
  rpi-config: I2C support
  rpi-base.inc: Allow MACHINE_FEATURES appends
  pitft: Add basic support for PiTFT
  pitft: Add PiTFT22 support

 .gitignore |   1 +
 README |  55 ---
 conf/machine/include/rpi-base.inc  |   3 +-
 recipes-bsp/bootfiles/rpi-config_git.bb|  17 +++-
 .../rpi/xorg.conf.d/99-pitft.conf  |   5 +
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  |  11 ++-
 recipes-kernel/linux/linux-raspberrypi.inc |   6 +-
 ...dts-add-overlay-for-pitft22-in-linux-3.18.patch | 110 +
 .../0001-dts-add-overlay-for-pitft22.patch | 110 +
 recipes-kernel/linux/linux-raspberrypi_3.18.bb |   5 +-
 recipes-kernel/linux/linux-raspberrypi_4.1.bb  |   8 +-
 11 files changed, 308 insertions(+), 23 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22-in-linux-3.18.patch
 create mode 100644 
recipes-kernel/linux/linux-raspberrypi/0001-dts-add-overlay-for-pitft22.patch

-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v2 6/7] pitft: Add basic support for PiTFT

[Petter Mabäcker]

Add basic support for PiTFT display by using device-trees.

In order get it working below configurations must be active in
local.conf:

MACHINE_FEATURES += "pitft"
 - This will enable SPI bus and i2c device-trees, it will also setup
   framebuffer for console and x server on PiTFT.

[Support #70]

Signed-off-by: Petter Mabäcker 
---
 README | 29 --
 recipes-bsp/bootfiles/rpi-config_git.bb|  6 +++--
 .../rpi/xorg.conf.d/99-pitft.conf  |  5 
 .../xorg-xserver/xserver-xf86-config_0.1.bbappend  | 11 ++--
 recipes-kernel/linux/linux-raspberrypi.inc |  6 -
 5 files changed, 44 insertions(+), 13 deletions(-)
 create mode 100644 
recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf

diff --git a/README b/README
index 8ef4e7a..6a6c398 100644
--- a/README
+++ b/README
@@ -22,10 +22,11 @@ Contents:
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
 2.J. Optional - Enable I2C
-2.K. Images
-2.L. Boot to U-Boot
-2.M. Image with Initramfs
-2.N. Device tree support
+2.K. Optional - Enable PiTFT support
+2.L. Images
+2.M. Boot to U-Boot
+2.N. Image with Initramfs
+2.O. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -157,7 +158,19 @@ ENABLE_SPI_BUS = "1"
 When using device tree kernels, set this variable to enable I2C
 ENABLE_I2C = "1"
 
-2.K. Images
+2.K. Optional - Enable PiTFT support
+
+Basic support for using PiTFT screens can be enabled by adding
+below in local.conf:
+
+MACHINE_FEATURES += "pitft"
+  - This will enable SPI bus and i2c device-trees, it will also setup
+framebuffer for console and x server on PiTFT.
+
+NOTE: To get this working the overlay for the PiTFT model must be build,
+  added and specified as well (dtoverlay= in config.txt)
+
+2.L. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -167,7 +180,7 @@ ENABLE_I2C = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.L. Boot to U-Boot
+2.M. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -175,7 +188,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.M. Image with Initramfs
+2.N. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -188,7 +201,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.N. Device tree support
+2.O. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index ccb9b7f..236a359 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -15,6 +15,8 @@ S = "${WORKDIR}/git"
 
 PR = "r4"
 
+PITFT="${@bb.utils.contains("MACHINE_FEATURES", "pitft", "1", "0", d)}"
+
 inherit deploy
 
 do_deploy() {
@@ -68,12 +70,12 @@ do_deploy() {
 fi
 
 # SPI bus support
-if [ -n "${ENABLE_SPI_BUS}" ]; then
+if [ -n "${ENABLE_SPI_BUS}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
 
-if [ -n "${ENABLE_I2C}" ]; then
+if [ -n "${ENABLE_I2C}" ] || [ "${PITFT}" = "1" ]; then
 echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
diff --git 
a/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
new file mode 100644
index 000..0d2b36b
--- /dev/null
+++ 
b/recipes-graphics/xorg-xserver/xserver-xf86-config/rpi/xorg.conf.d/99-pitft.conf
@@ -0,0 +1,5 @@
+Section "Device"
+Identifier "Adafruit PiTFT"
+Driver "fbdev"
+Option "fbdev" "/dev/fb1"
+EndSection
diff --git a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend 
b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
index 2cf40f8..0ae2ee0 100644
--- a/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
+++ b/recipes-graphics/xorg-xserver/xserver-xf86-config_0.1.bbappend
@@ -1,10 +1,17 @@
 FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
 
-SRC_URI_append_rpi = " file://xorg.conf.d/10-evdev.conf "
+SRC_URI_append_rpi = " file://

[yocto] [meta-raspberrypi][PATCH v2 2/7] .gitignore: Ignore .swp files

[Petter Mabäcker]

Signed-off-by: Petter Mabäcker 
---
 .gitignore | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.gitignore b/.gitignore
index 1677b58..f235765 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,2 +1,3 @@
 build*
 *~
+.*.swp
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v2 4/7] rpi-config: I2C support

[Petter Mabäcker]

With newer kernels (>=3.18) that supports device-trees I2C
should be enabled with device-trees.

This is now support by adding:
ENABLE_I2C = "1"
in local.conf

This will enable the dtparams:
i2c1
i2c_arm

Signed-off-by: Petter Mabäcker 
---
 README  | 21 +
 recipes-bsp/bootfiles/rpi-config_git.bb |  6 ++
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/README b/README
index a168692..8ef4e7a 100644
--- a/README
+++ b/README
@@ -21,10 +21,11 @@ Contents:
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
 2.I. Optional - Enable SPI bus
-2.J. Images
-2.K. Boot to U-Boot
-2.L. Image with Initramfs
-2.M. Device tree support
+2.J. Optional - Enable I2C
+2.K. Images
+2.L. Boot to U-Boot
+2.M. Image with Initramfs
+2.N. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -151,8 +152,12 @@ ENABLE_KGDB = "1"
 When using device tree kernels, set this variable to enable the SPI bus
 ENABLE_SPI_BUS = "1"
 
+2.J. Optional - Enable I2C
+==
+When using device tree kernels, set this variable to enable I2C
+ENABLE_I2C = "1"
 
-2.J. Images
+2.K. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -162,7 +167,7 @@ ENABLE_SPI_BUS = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.K. Boot to U-Boot
+2.L. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -170,7 +175,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.L. Image with Initramfs
+2.M. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -183,7 +188,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.M. Device tree support
+2.N. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
diff --git a/recipes-bsp/bootfiles/rpi-config_git.bb 
b/recipes-bsp/bootfiles/rpi-config_git.bb
index aa11b25..ccb9b7f 100644
--- a/recipes-bsp/bootfiles/rpi-config_git.bb
+++ b/recipes-bsp/bootfiles/rpi-config_git.bb
@@ -72,6 +72,12 @@ do_deploy() {
 echo "# Enable SPI bus" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 echo "dtparam=spi=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
 fi
+
+if [ -n "${ENABLE_I2C}" ]; then
+echo "# Enable I2C" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c1=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+echo "dtparam=i2c_arm=on" >>${DEPLOYDIR}/bcm2835-bootfiles/config.txt
+fi
 }
 
 addtask deploy before do_package after do_install
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v2 1/7] README: Add SPI bus chapter to content

[Petter Mabäcker]

The optional SPI bus chapter was missing in the content list.

While at it also place it together with the other "optional" chapters,
instead of in the end.

Signed-off-by: Petter Mabäcker 
---
 README | 28 +++-
 1 file changed, 15 insertions(+), 13 deletions(-)

diff --git a/README b/README
index 16ac1cb..a168692 100644
--- a/README
+++ b/README
@@ -20,10 +20,11 @@ Contents:
 2.F. Optional - Video camera support with V4L2 drivers
 2.G. Optional - Enable offline compositing support
 2.H. Optional - Enable kgdb over console support
-2.I. Images
-2.J. Boot to U-Boot
-2.K. Image with Initramfs
-2.L. Device tree support
+2.I. Optional - Enable SPI bus
+2.J. Images
+2.K. Boot to U-Boot
+2.L. Image with Initramfs
+2.M. Device tree support
 3. Extra apps
 3.A. omxplayer
 4. Source code and mirrors
@@ -145,7 +146,13 @@ To add the kdbg over console (kgdboc) parameter to the 
kernel command line,
 set this variable in local.conf:
 ENABLE_KGDB = "1"
 
-2.I. Images
+2.I. Optional - Enable SPI bus
+==
+When using device tree kernels, set this variable to enable the SPI bus
+ENABLE_SPI_BUS = "1"
+
+
+2.J. Images
 ===
 * rpi-hwup-image
 Hardware up image
@@ -155,7 +162,7 @@ ENABLE_KGDB = "1"
 Image based on rpi-basic-image which includes most of the packages in this
 layer and some media samples.
 
-2.J. Boot to U-Boot
+2.K. Boot to U-Boot
 ===
 To have u-boot load kernel image, set in your local.conf
 KERNEL_IMAGETYPE = "uImage"
@@ -163,7 +170,7 @@ KERNEL_IMAGETYPE = "uImage"
 This will make kernel.img be u-boot image which will load uImage.
 By default, kernel.img is the actual kernel image (ex. Image).
 
-2.K. Image with Initramfs
+2.L. Image with Initramfs
 =
 To build an initramfs image :
 * Set this 3 kernel variables (in linux-raspberrypi.inc for example)
@@ -176,7 +183,7 @@ To build an initramfs image :
 * Set the meta-rasberrypi variable (in raspberrypi.conf for example)
 - KERNEL_INITRAMFS = "-initramfs"
 
-2.L. Device tree support
+2.M. Device tree support
 =
 Device tree for RPi is only supported when using linux-raspberrypi 3.18+
 kernels.
@@ -189,11 +196,6 @@ kernels.
 NOTE: KERNEL_DEVICETREE is default enabled for kernel >= 3.18 and always 
disabled for
   older kernel versions.
 
-2.M. Optional - enable SPI bus
-==
-When using device tree kernels, set this variable to enable the SPI bus
-ENABLE_SPI_BUS = "1"
-
 3. Extra apps
 =
 
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v2 5/7] rpi-base.inc: Allow MACHINE_FEATURES appends

[Petter Mabäcker]

Ensure that it's possible to add MACHINE_FEATURES from places that will
be executed before rpi-base.inc (like e.g. local.conf), without having
them overrided.

Signed-off-by: Petter Mabäcker 
---
 conf/machine/include/rpi-base.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conf/machine/include/rpi-base.inc 
b/conf/machine/include/rpi-base.inc
index e097702..c8f6cd6 100644
--- a/conf/machine/include/rpi-base.inc
+++ b/conf/machine/include/rpi-base.inc
@@ -37,7 +37,7 @@ KERNEL_DEVICETREE ?= " \
 "
 KERNEL_IMAGETYPE ?= "Image"
 
-MACHINE_FEATURES = "kernel26 apm usbhost keyboard vfat ext2 screen touchscreen 
alsa bluetooth wifi sdio"
+MACHINE_FEATURES += "kernel26 apm usbhost keyboard vfat ext2 screen 
touchscreen alsa bluetooth wifi sdio"
 
 # Raspberry Pi has no hardware clock
 MACHINE_FEATURES_BACKFILL_CONSIDERED = "rtc"
-- 
1.9.1

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

[yocto] [meta-raspberrypi][PATCH v2 3/7] linux-raspberrypi: Update 4.1 recipe to 4.1.15

[Petter Mabäcker]

[Support #69]

Signed-off-by: Petter Mabäcker 
---
 recipes-kernel/linux/linux-raspberrypi_4.1.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-raspberrypi_4.1.bb 
b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
index 3a3cf40..cae459a 100644
--- a/recipes-kernel/linux/linux-raspberrypi_4.1.bb
+++ b/recipes-kernel/linux/linux-raspberrypi_4.1.bb
@@ -1,6 +1,6 @@
-LINUX_VERSION ?= "4.1.10"
+LINUX_VERSION ?= "4.1.15"
 
-SRCREV = "b74df9228c27f55361c065bc5dbfba88861cc771"
+SRCREV = "02a8ee530e32b08e5df44f10e24d5fd82bb960e3"
 SRC_URI = 
"git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.1.y"
 
 require linux-raspberrypi.inc
-- 
1.9.1

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

Re: [yocto] Package naming "exceptions" in Yocto

[akuster]

On 01/13/2016 11:43 PM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 

Since you ask about "Yocto" naming in the Poky distribution I have the
following comments:

The Reference to "Yocto" should only be in terms of the project. The
Soures you refer to in support of the "Poky" distro.
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check. 

The Yocto project should not have any specific packages. Its "Poky". In
fact in the last OEDAME it was decided to rename the meta-yocto* layers
to meta-poky*.  I was hoping would have been changed by now.

People are saying "Yocto linux" which is wrong. Its the Yocto Project
which has a test distro named "Poky".

Just ask Phil B.


> 
>  
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can. 

There may be a need to have a mapping for upstream names to packages
named within OE. They may not all be 1:1. Or in the case of someone
outside the project runs this in there distro they can.

regards,
Armin

> 
>  
> 
> Best Regards,
> Elena.
> 
>  
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [PATCH][coreutils] Add attr build dependency

[Scott Ellis]

Fixes this warning:

WARNING: QA Issue: coreutils rdepends on libattr, but it isn't a build 
dependency? [build-deps]

Signed-off-by: Scott Ellis 
---
 meta/recipes-core/coreutils/coreutils_8.24.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/coreutils/coreutils_8.24.bb 
b/meta/recipes-core/coreutils/coreutils_8.24.bb
index f042346..47a25f3 100644
--- a/meta/recipes-core/coreutils/coreutils_8.24.bb
+++ b/meta/recipes-core/coreutils/coreutils_8.24.bb
@@ -7,7 +7,7 @@ BUGTRACKER = "http://debbugs.gnu.org/coreutils";
 LICENSE = "GPLv3+"
 LIC_FILES_CHKSUM = "file://COPYING;md5=d32239bcb673463ab874e80d47fae504\
 
file://src/ls.c;beginline=5;endline=16;md5=38b79785ca88537b75871782a2a3c6b8"
-DEPENDS = "gmp libcap"
+DEPENDS = "attr gmp libcap"
 DEPENDS_class-native = ""

 inherit autotools gettext texinfo
--
2.5.0

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

Re: [yocto] Package naming "exceptions" in Yocto

[Reshetova, Elena]

>Please note there is a security page on the wiki:

>https://wiki.yoctoproject.org/wiki/Security

>and there is a security list at:

>yocto-secur...@yoctoproject.org

>The list isn't very active, but it should be copied on all security
discussions. If you are interested you should be subscribed to this list.

>If I hadn't read the email, I wouldn't have realized this was about
security issues.

Well, security is just an example use-case, but the question is generic,
that's why I asked on yocto list. 

Best Regards,
Elena.

On 01/14/2016 02:43 AM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 
> 
> Are there more such yocto-specific packages (of course excluding FW 
> and other bsp-related packages)? A look over the package list didn't 
> reveal any, but I wanted to double check.
> 
>  
> 
> The reason I am asking is that in case when we try to determine the 
> package CVEs against the NVD database, in these particular exception 
> cases, we probably want to check not only "linux-yocto", but also 
> "linux_kernel" open package CVEs with regards to specified version to 
> make sure we cover as much as we can.
> 
>  
> 
> Best Regards,
> Elena.
> 
>  
> 
> 
> 
> 


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

Re: [yocto] Package naming "exceptions" in Yocto

[Philip Balister]

Please note there is a security page on the wiki:

https://wiki.yoctoproject.org/wiki/Security

and there is a security list at:

yocto-secur...@yoctoproject.org

The list isn't very active, but it should be copied on all security
discussions. If you are interested you should be subscribed to this list.

If I hadn't read the email, I wouldn't have realized this was about
security issues.

Philip

On 01/14/2016 02:43 AM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check. 
> 
>  
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can. 
> 
>  
> 
> Best Regards,
> Elena.
> 
>  
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-java] openjdk-8 fail to build

[Federico Pietro Briata]

Hi,

I'm on 1.6.2 (daisy Branch), so probably I've to cherry-pick something more
on poky.

With poky-daisy-11.0.2 (Hash: e3dd621197548b4cf64988e757e9bc926082db73) I
confirm that openjdk 7 was working for sure with this commit
d7d4f64a32d26fc8a92e4c89b47c78956f20a14d

Regards,
Federico
Hi,

What version of Yocto are you using?
I'm using 1.7.1 version with only the patch i described in my previous
answer.
When using it on the master of meta-java i got it working without any
issues.. You mentioned you use another patch as well?

Regards

2016-01-13 18:46 GMT+01:00 Federico Pietro Briata :

> Hi again,
> looking to the above error on Makefile, seems there is still something
> wrong with autotools
>
>
> cat
> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile
> # This Makefile was generated by configure Tue Jan 12 22:44:00 CET 2016
> # GENERATED FILE, DO NOT EDIT
>
> SPEC:=/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/build/linux-x86_64-normal-server-release/spec.gmk
> include
> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile
>
> so the build stuck here in this loop I think.
>
> regards
> Federico
>
> 2016-01-12 17:41 GMT+01:00 Federico Pietro Briata :
>
>> Hi Stef,
>> Thanks, I've tried to apply that patch and also
>>
>> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=527b28c10955daf0387597020d69593ce24bcaa4
>>
>> and now I'm getting this:
>>
>> ERROR: Function failed: do_compile (log file is located at
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_compile.15889)
>> ERROR: Logfile of failure stored in:
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_compile.15889
>> Log data follows:
>> | DEBUG: SITE files ['endian-little', 'common-linux', 'common-glibc',
>> 'bit-64', 'x86_64-linux', 'common']
>> | DEBUG: Executing shell function do_compile
>> | NOTE: make
>> OE_CFLAGS=-isystem/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/include
>> -O2 -pipe -DHEADLESS=true
>> OE_CPPFLAGS=-isystem/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/include
>> -DHEADLESS=true
>> OE_CXXFLAGS=-isystem/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/include
>> -O2 -pipe -DHEADLESS=true
>> OE_LDFLAGS=-L/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/lib
>> -L/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/lib
>> -Wl,-rpath-link,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/lib
>> -Wl,-rpath-link,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/lib
>> -Wl,-rpath,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/usr/lib
>> -Wl,-rpath,/home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/sysroots/x86_64-linux/lib
>> -Wl,-O1 BUILD_HEADLESS_ONLY=1 BUILD_HEADLESS=true BUILD_SOUNDLESS_ONLY=1
>> X11_NOT_NEEDED=1 CUPS_NOT_NEEDED=1 ALSA_NOT_NEEDED=1 PULSE_NOT_NEEDED=1
>> MAKE_VERBOSE=y VERBOSE=-s LOG_LEVEL=trace QUIETLY= images
>> |
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/jdk8u-e8bed1496ff2/Makefile:27:
>> *** Too many open files.  Stop.
>> | ERROR: oe_runmake failed
>> | WARNING: exit code 1 from a shell command.
>> | ERROR: Function failed: do_compile (log file is located at
>> /home/federico/yocto/imx6/R6.0/build-OpenJDK8-imx6-mx6quad/tmp-eglibc/work/x86_64-linux/openjdk-8-native/72b05-r0/temp/log.do_compile.15889)
>> ERROR: Task 207
>> (/home/federico/yocto/imx6/R6.0/sources/meta-java/recipes-core/openjdk/
>> openjdk-8-native_72b05.bb, do_compile) failed with exit code '1'
>> NOTE: Tasks Summary: Attempted 1469 tasks of which 1237 didn't need to be
>> rerun and 1 failed.
>> No currently running tasks (1469 of 1483)
>>
>> Summary: 1 task failed:
>>   /home/federico/yocto/imx6/R6.0/sources/meta-java/recipes-core/openjdk/
>> openjdk-8-native_72b05.bb, do_compile
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>>
>> thanks and regards
>> federico
>>
>> 2015-12-19 10:38 GMT+01:00 Stef :
>>
>>> Federico Pietro Briata  writes:
>>>
>>> >
>>> >
>>> >
>>> > Hi All,
>>> > I'm trying to build openjdk-8 but I'm stuck.my current setup does not
>>> define anything for:#PREFERRED_PROVIDER_virtual/java-
>>> native#PREFERRED_PROVIDER_virtual/javac-native
>>> >
>>> > follow the log error
>>> >
>>> >
>>> >
>>> > ERROR: Function failed: do_confi

[yocto] How to change the order of package installation

[RayBloodworth]

Hi, everyone
   I'm using the dizzy branch of freescale yocto project to build image. When 
do_rootfs is done, I found that package "base-files" wasn't the first order of 
installation.Since I want do some modify like "/bin -> /usr/bin" in 
"base-files", package "base-files" must be the first order of installation.   
Could anyone help me with this issue?
Best regards,Ray  -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto