[yocto] [RFC] Report build

2015-04-06 Thread João Henrique Ferreira de Freitas 


Hi,

I would like to share an implementation that I've used with
great success to solve the following situation:

We have a farm server that Jenkins CI has the control. All the
nights a bunch of devel, snapshot and stable builds are fired.
Each machine receives a job that the aim is to build image, SDK,
packages and wic images. After that, all the artifacts are collected
and send to a consolidation server which my users could download.

I believed that many YP users has the very similar settings. So I wanted
to create a solution which is integrated with YP.

This solution involves three things:

* new class to collect the artifacts
* script to send the collected artifacts
* web interface to summaries the results

So I implemented a class called report-build. Once properly setup, it
will collect the artifacts writing in a json file. The meaning of
artifact is: images, packages, sdks, manifest, deploy kernel and bootloader.
After that, all artifact is collected using another script called 
send-build-report. This scripts has

the responsibility to control and send the artifacts (until now using rsync)
to consolidation server.

The consolidation server is a machine running an instance of 
build-report-web that
receives the json payload, creates all the database entry and filesystem 
places where

the artifacts will be placed.

On Jenkins I've created Freestyle jobs that  is setup scripts to build 
the artifacts and

configures the variables that build-report class use:

BUILD_REPORT_DISTRO ?= ${DISTRO}
BUILD_REPORT_DISTRO_VERSION ?= ${DISTRO_VERSION}

BUILD_REPORT_JOB_RETENTION ?= 1
BUILD_REPORT_JOB_ID ?= job-${DATE}
BUILD_REPORT_DIR ?= ${LOG_DIR}/build-report
BUILD_REPORT_SERVER ?= http://127.0.0.1:8000/Builds;
BUILD_REPORT_USER ?= 
BUILD_REPORT_EMAIL ?= 
BUILD_REPORT_TYPE ?= snapshot
BUILD_REPORT_DEPLOY_DIR = ${DEPLOY_DIR}

When the Jenkins runs the job, it only executes the script and 
report-build is in charge to

sends the generated artifacts.

So, the users goes to build-report-web tool and inspects and downloads 
the results.


Here is the very basic web interface:

A home page showing all builds: http://imgur.com/LTqRewq

A detail page to get files (image, sdk, packages): http://imgur.com/gNOtoLO

There are some drawbacks like: the solution uses rsync over ssh to send 
files and
the user must setup ssh keys between build machines and consolidation 
server. But

this is done only once, to setup the initial environment.

This work was based on ideas from:
- report-error
- Error reporting tool

Currently this implementation works using daisy and master. On my 
production environment

I need to use daisy but I am doing the same using master on my free time.


Implementation links:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=joaohf/master-build-report-tool
http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=joaohf/build-report-web

Thanks


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

Re: [yocto] Kernel Panic: /sbin/init not found

2015-04-06 Thread Yu, Chan KitX 
I guess I have mistaken something in 
https://wiki.yoctoproject.org/wiki/Multilib#How_to_use_it . I have simply put 
the line:

IMAGE_INSTALL = lib32-connman

which turned out to be a wrong move. I'm not entirely sure of why this has 
worked for me for several months but that was the case and I stuck to it until 
this problem took me in the knee. I'm not sure if the line above is correct in 
its context. lib32-connman is just a package and perhaps it should have used 
IMAGE_INSTALL_append or IMAGE_INSTALL+=

Chan Kit

 -Original Message-
 From: Smith, Virgil [mailto:virgil.sm...@flir.com]
 Sent: Tuesday, April 07, 2015 1:13 AM
 To: Paul Eggleton
 Cc: Yu, Chan KitX; yocto@yoctoproject.org
 Subject: RE: [yocto] Kernel Panic: /sbin/init not found
 
 
  This is not true in the general case. You definitely can use
  IMAGE_INSTALL_append with a leading space to add items to an image, I
  just verified that now.
 
  I'm not clear on exactly what happened in the case we're discussing,
  at least initially it sounded like IMAGE_INSTALL = rather than
  IMAGE_INSTALL_append = was being used, which would definitely account
 for the behaviour described.
 
 Digging testing reading
 I don't know what happened in Chan Kit's case, but it looks like my earlier
 trouble was using IMAGE_INSTALL +=  from inside local.conf.
 IMAGE_INSTALL_append isn't applied until after parsing completes.  So here
 is one (or rather the) way to overcome the fact that local.conf is *parsed*
 too early for extending variables/configuration introduced later in the
 *parsing* chain.
 
 So, my earlier statement that you can't use/rely on IMAGE_INSTALL_append
 from local.conf is flat wrong.
 
  The precedence of bb files and order of application of bbappends is
  controlled primarily by layer priorities; the order that layers appear
  in bblayers.conf shouldn't come into that (although it may if you have
  layers that have exactly the same priority set). The order of layers
  in bblayers.conf can influence the order in which bbclass and inc
  files are found *where files of the same name exist across different
  layers*, since these are found using BBPATH, which is prepended or
  appended to by each layer.conf file and thus the order in which those files
 are parsed is significant.
 
 Thanks Paul, I wasn't sure I had the whole story.
 
 
 
 Notice to recipient: This email is meant for only the intended recipient of 
 the
 transmission, and may be a communication privileged by law, subject to
 export control restrictions or that otherwise contains proprietary
 information. If you receive this email by mistake, please notify us
 immediately by replying to this message and then destroy it and do not
 review, disclose, copy or distribute it. Thank you in advance for your
 cooperation.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ERROR: python not found in the base feeds

2015-04-06 Thread Rickard Bremer 
Hello,

I'm trying to include python in my Build. I can build a image but whenever i 
add python in local.conf i get a crash.

ERROR: python not found in the base feeds (congatec_qa3_64 
corei7-64-intel-common corei7-64 core2-64 x86_64 noarch any all).

// Lots of text

ERROR: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/var/lib/jenkins/workspace/thesis-build-yocto/intel/tmp/work/congatec_qa3_64-poky-linux/core-image-x11/1.0-r0/temp/log.do_rootfs.10871
ERROR: Task 7 
(/var/lib/jenkins/workspace/thesis-build-yocto/meta/recipes-graphics/images/core-image-x11.bb,
 do_rootfs) failed with exit code '1'

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

[yocto] [prelink-cross][PATCH 1/1] debug-for-missing-loader-and-libc

2015-04-06 Thread Maninder Singh 
Hi,

prelink gives below error message for failure dependency:
./prelink: /test_binary: Could not find one of the dependencies

This provides name of dependent library which is missing like below:
./prelink: /test_binary: Could not find one of the dependencies:
./prelink-rtld: error while loading shared libraries: libB.so: cannot open 
shared object file: No such file or directory
where libB.so is missing dependecy

Signed-off-by: Maninder Singh maninder...@samsung.com
Signed-off-by: Vaneet Narang v.nar...@samsung.com
Reviewed-by: Ajeet Yadav ajee...@samsung.com
Reviewed-by: Geon-ho Kim gh007@samsung.com
---
 src/gather.c |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/gather.c b/src/gather.c
index 5ccd243..4a3f428 100644
--- a/src/gather.c
+++ b/src/gather.c
@@ -240,8 +240,8 @@ gather_deps (DSO *dso, struct prelink_entry *ent)
  if (q != NULL)
{
  error (0, 0,
-%s: Could not find one of the dependencies,
-ent-filename);
+%s: Could not find one of the dependencies:\n%s,
+ent-filename, line);
  goto error_out;
}
}
--


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

[yocto] [prelink-cross] [PATCH 1/1] debug-for-missing-loader-and-libc

2015-04-06 Thread Maninder Singh 
Hi,

During cross prelink if we miss out ld-linux.so.* or libc.so.* It prints below 
info:
./prelink: /test_binary: Could not parse `prelink-rtld: dl-version.c:219: 
rtld_check_map_versions:
 Assertion `needed != ((void *)0)' failed.'

And thus we miss actual cause for this failure,  by this patch we will know 
failure reason.
./prelink: /test_binary: Could not parse `./prelink-rtld: error while loading 
shared libraries: ld-linux.so.3'
(In this case ld-linux.so.3 was missing)

Signed-off-by: Maninder Singh maninder...@samsung.com
Signed-off-by: Vaneet Narang v.nar...@samsung.com
Reviewed-by: Ajeet Yadav ajee...@samsung.com
Reviewed-by: Geon-ho Kim gh007@samsung.com
---
 src/rtld/dl-version.c |6 ++
 1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/src/rtld/dl-version.c b/src/rtld/dl-version.c
index e4040a6..eb62943 100644
--- a/src/rtld/dl-version.c
+++ b/src/rtld/dl-version.c
@@ -216,6 +216,12 @@ _dl_check_map_versions (struct ldlibs_link_map *map, int 
verbose, int trace_mode
  /* If NEEDED is NULL this means a dependency was not found
 and no stub entry was created.  This should never happen.  */
+ if(needed == NULL)
+   {
+ _dl_signal_error (errval, NULL, NULL, strtab + ent-vn_file);
+ printf(error while loading shared libraries: %s, strtab + 
ent-vn_file);
+ exit(0);
+   }
  assert (needed != NULL);
  /* Make sure this is no stub we created because of a missing
--
1.7.1

And also if it is ok we can remove this one --- assert (needed != NULL); 
because we are using exit(0) for (needed==NULL) 

Thanks,
Maninder Singh
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [prelink-cross][PATCH 1/1] debug message for dependencies not found

2015-04-06 Thread Maninder Singh 
Hi,
Same mail sent earlier Changing subject line, By mistake shared subject line of 
other patch.

prelink gives below error message for failure dependency:
./prelink: /test_binary: Could not find one of the dependencies

This provides name of dependent library which is missing like below:
./prelink: /test_binary: Could not find one of the dependencies:
./prelink-rtld: error while loading shared libraries: libB.so: cannot open 
shared object file: No such file or directory
where libB.so is missing dependecy

Signed-off-by: Maninder Singh maninder...@samsung.com
Signed-off-by: Vaneet Narang v.nar...@samsung.com
Reviewed-by: Ajeet Yadav ajee...@samsung.com
Reviewed-by: Geon-ho Kim gh007@samsung.com
---
 src/gather.c |4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/gather.c b/src/gather.c
index 5ccd243..4a3f428 100644
--- a/src/gather.c
+++ b/src/gather.c
@@ -240,8 +240,8 @@ gather_deps (DSO *dso, struct prelink_entry *ent)
  if (q != NULL)
{
  error (0, 0,
-%s: Could not find one of the dependencies,
-ent-filename);
+%s: Could not find one of the dependencies:\n%s,
+ent-filename, line);
  goto error_out;
}
}
--


Thanks 
Maninder Singh

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

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

2015-04-06 Thread recipe-report 
This mail was sent out by Recipe reporting system.

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

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

You can check the detail information at:

http://packages.yoctoproject.org/

Package   Version  Upstream version  Maintainer   
NoUpgradeReason
  ---    ---  
--
nfs-utils 1.3.11.3.2 Alejandro Hernandez
midori0.5.80.5.9 Alejandro Hernandez
python-smmap  0.8.20.9.0 Alejandro Hernandez
python3   3.3.33.5.0a3   Alejandro Hernandez
python2.7.93.5.0a3   Alejandro Hernandez
which 2.20 2.21  Alejandro Hernandez
gnome-icon-theme  2.31.0   3.12.0Alejandro Hernandez  
waiting for the sato gtk3 port
jpeg  8d   9aAníbal Limón 
webkit-gtk 1.8.3 doesn't wo...
dpkg  1.17.21  1.17.24   Aníbal Limón
sqlite3   3.8.7.4  3.8.8.3.  Aníbal Limón
mc4.8.13   4.8.14Aníbal Limón
screen4.0.34.2.1 Aníbal Limón
nettle2.7.13.1rc3Armin Kuster 
3.0.0 breaks gnutls, api ch...
pinentry  0.9.00.9.1 Armin Kuster
linux-libc-headers3.19 3.19.3Bruce Ashfield
busybox   1.23.1   1.23.2Chen Qi
console-tools 0.3.21999.03.02Chen Qi
util-linux2.25.2   2.26.1Chen Qi
kmod  19+gitX  20+gitAUTOINC+a8c...  Chen Qi
curl  7.40.0   7.41.0Chen Qi
sudo  1.8.11p2 1.8.13Chen Qi
sysstat   11.0.2   11.1.3Chen Qi
xz5.2.05.2.1 Chen Qi
dbus-glib 0.1020.104 Chong Lu
dbus-test 1.8.10   1.9.14Chong Lu
dbus  1.8.10   1.9.14Chong Lu 
D-BUS 1.9.x is the developm...
bison 2.7.13.0.4 Chong Lu
strace4.9  4.10  Chong Lu
tcl   8.6.38.6.4 Chong Lu
libuser   0.60 0.61  Chong Lu
bluez44.1015.30  Cristian Iorga   
BlueZ 5.x is not backward-c...
gst-plugin-bluetooth  4.1015.30  Cristian Iorga
bluez55.28 5.30  Cristian Iorga
iproute2  3.17.0   3.19.0Cristian Iorga
libpcap   1.6.21.7.2 Cristian Iorga
wpa-supplicant2.3  2.4   Cristian Iorga
alsa-lib  1.0.28   1.0.29Cristian Iorga
alsa-utils-alsaconf   1.0.28   1.0.29Cristian Iorga
alsa-utils1.0.28   1.0.29Cristian Iorga
gst-ffmpeg0.10.13  0.11.2Cristian Iorga
gst-fluendo-mp3   0.10.31  0.10.32   Cristian Iorga
gst-plugins-bad   0.10.23  1.4.5 Cristian Iorga   
not compatible with gst-flu...
gst-plugins-base  0.10.36  1.4.5 Cristian Iorga   
not compatible with gst-flu...
gst-plugins-good  0.10.31  1.4.5 Cristian Iorga   
not compatible with gst-flu...
gst-plugins-ugly  0.10.19  1.4.5 Cristian Iorga
gstreamer 0.10.36  1.4.5 Cristian Iorga   
not compatible with gst-fl...
libvorbis 1.3.41.3.5 Cristian Iorga
libatomics-ops7.2  7.4.0 Cristian Iorga
speex 1.2rc1   1.2rc2Cristian Iorga
qemu  2.2.02.2.1 Cristian Iorga
db6.0.30   6.1.23.NC Cristian Iorga   
API compatibility issue
libical   1.0.01.0.1 Cristian Iorga
quota 4.01 4.02  Cristian Iorga
harfbuzz  0.9.38   0.9.40Cristian Iorga
hwlatdetect   0.89 0.91  Darren Hart
rt-tests  0.89 0.91

[yocto] Reg flashing Yocto SDcard image onto IMX6q sabre sd card

2015-04-06 Thread Shalini K P 
Hi,

 I have prepared an Yocto SD card image 
core-image-minimal-imx6q-sabresd.sdcard.  I trying to flash the image onto 
sdcard using the command
sudo dd  if= core-image-minimal-imx6q-sabresd.sdcard of=/dev/sdb bs=1M
Sync
Sync

I m getting the boot messages as below

U-Boot 2014.10+fslc+g5fd0b60 (Apr 03 2015 - 18:55:01)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-SabreSD
I2C:   ready
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment

No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In:serial
Out:   serial
Err:   serial
PMIC:  PFUZE100 ID=0x10
Net:   FEC [PRIME]
Hit any key to stop autoboot:  1
I m stuck up badly.  It is not going further.  Does the sdcard image contain 
ü-boot, kernel image and rootfs ? or should I flash u-boot separately ? I even 
tried flashing both u-boot and sdcaed image. But getting same messages.  
Request help in this regard.  I'm using Dizzy branch  and SABRESD Evk board.


Thanks  Regards
Shalini K P


LT Technology Services Ltd

www.LntTechservices.comhttp://www.lnttechservices.com/

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] what's the difference between meta-openembedded/meta-oe and meta-oe/meta-oe

2015-04-06 Thread Philip Balister 
On 04/05/2015 06:46 PM, Ken Davis wrote:
 I'm soo confused.
 
 what's the difference between meta-openembedded/meta-oe and
 meta-oe/meta-oe?
 

Nothing. The meta-oe (and oe-core) repos are deprecated and will be
removed soon.

Make sure you use meta-openembedded and openembedded-core checkouts and
refer to them in manifests and scripts.

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

[yocto] Reg Yocto flashing on IMX6q

2015-04-06 Thread Shalini K P 
Hi,

   I'm using SD card slot 3(SD3) with SW6 Dip switches configuration for 
booting. As per IMX6 SabreSD QSG guide.



Thanks  regards
Shalini K P

LT Technology Services Ltd

www.LntTechservices.comhttp://www.lnttechservices.com/

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Reg flashing Yocto SDcard image onto IMX6q sabre sd card

2015-04-06 Thread Sandeep G.R 
Hi Shalini,

 Below is the basic steps for SD card boot on iMX6. Create two
partitions on the SD card ext2 for boot and ext4 for rootfs using following
commands.

*Create the partions:*

*sudo dd if=/dev/zero of=/dev/sdX bs=1M count=16*
*sudo mkfs.ext2 /dev/sdX1 -L boot*
*sudo mkfs.ext4 /dev/sdX2 -L rootfs*

*Mount the partions:*

*sudo mkdir -p /media/boot/*
*sudo mkdir -p /media/rootfs/*
*sudo mount /dev/sdX1 /media/boot/*
*sudo mount /dev/sdX2 /media/rootfs/*

*Copy the binaries to SD card:*

*sudo tar xfvp yocto-build/tmp/deploy/rootfs.tar -C /media/rootfs/*
*sudo cp -v yocto-build/tmp/deploy/kernel-image /media/boot*
*sudo cp -v yocto-build/tmp/deploy/kernel-dtb /media/boot*

*Edit the fstab file as shown below:*

*sudo nano /media/rootfs/etc/fstab*
*/dev/sdX2   /   auto   errors=remount-ro   0   1*
*/dev/sdX1   /boot/uboot  auto   defaults   0   2*

Make sure your uboot environment variables are set properly for sd card
flash.


On Mon, Apr 6, 2015 at 6:23 AM, Shalini K P shalini...@lnttechservices.com
wrote:

  Hi,



  I have prepared an Yocto SD card image
 core-image-minimal-imx6q-sabresd.sdcard.  I trying to flash the image
 onto sdcard using the command

 *sudo dd  if= core-image-minimal-imx6q-sabresd.sdcard of=/dev/sdb bs=1M*

 *Sync*

 *Sync*



 I m getting the boot messages as below




















 *U-Boot 2014.10+fslc+g5fd0b60 (Apr 03 2015 - 18:55:01) CPU:   Freescale
 i.MX6Q rev1.2 at 792 MHz Reset cause: POR Board: MX6-SabreSD I2C:   ready
 DRAM:  1 GiB MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2 *** Warning - bad
 CRC, using default environment No panel detected: default to Hannstar-XGA
 Display: Hannstar-XGA (1024x768) In:serial Out:   serial Err:   serial
 PMIC:  PFUZE100 ID=0x10 Net:   FEC [PRIME] Hit any key to stop autoboot:  1
 *

 I m stuck up badly.  It is not going further.  Does the sdcard image
 contain ü-boot, kernel image and rootfs ? or should I flash u-boot
 separately ? I even tried flashing both u-boot and sdcaed image. But
 getting same messages.  Request help in this regard.  I'm using Dizzy
 branch  and SABRESD Evk board.





 Thanks  Regards

 Shalini K P



 *LT Technology Services Ltd*

 www.LntTechservices.com http://www.lnttechservices.com/

 This Email may contain confidential or privileged information for the
 intended recipient (s). If you are not the intended recipient, please do
 not use or disseminate the information, notify the sender and delete it
 from your system.

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




-- 
*Thanks  Regards,*
*Sandeep G R*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [prelink-cross] [PATCH 1/1] debug-for-missing-loader-and-libc

2015-04-06 Thread Mark Hatle 
On 4/6/15 3:37 AM, Maninder Singh wrote:
 Hi,
 
 During cross prelink if we miss out ld-linux.so.* or libc.so.* It prints 
 below info:
 ./prelink: /test_binary: Could not parse `prelink-rtld: dl-version.c:219: 
 rtld_check_map_versions:
  Assertion `needed != ((void *)0)' failed.'
 
 And thus we miss actual cause for this failure,  by this patch we will know 
 failure reason.
 ./prelink: /test_binary: Could not parse `./prelink-rtld: error while loading 
 shared libraries: ld-linux.so.3'
 (In this case ld-linux.so.3 was missing)
 
 Signed-off-by: Maninder Singh maninder...@samsung.com
 Signed-off-by: Vaneet Narang v.nar...@samsung.com
 Reviewed-by: Ajeet Yadav ajee...@samsung.com
 Reviewed-by: Geon-ho Kim gh007@samsung.com
 ---
  src/rtld/dl-version.c |6 ++
  1 files changed, 6 insertions(+), 0 deletions(-)
 diff --git a/src/rtld/dl-version.c b/src/rtld/dl-version.c
 index e4040a6..eb62943 100644
 --- a/src/rtld/dl-version.c
 +++ b/src/rtld/dl-version.c
 @@ -216,6 +216,12 @@ _dl_check_map_versions (struct ldlibs_link_map *map, int 
 verbose, int trace_mode
   /* If NEEDED is NULL this means a dependency was not found
  and no stub entry was created.  This should never happen.  */
 + if(needed == NULL)
 +   {
 + _dl_signal_error (errval, NULL, NULL, strtab + ent-vn_file);
 + printf(error while loading shared libraries: %s, strtab + 
 ent-vn_file);
 + exit(0);

I'm likely to change this to an exit 1.  As I want to make sure that any
failures have a non 0 return code.

I believe the assert is in the original rtld code, but I'll check that and
remove it if it's something I added.

--Mark

 +   }
   assert (needed != NULL);
   /* Make sure this is no stub we created because of a missing
 --
 1.7.1
 
 And also if it is ok we can remove this one --- assert (needed != NULL); 
 because we are using exit(0) for (needed==NULL) 
 
 Thanks,
 Maninder Singh
 

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

Re: [yocto] [prelink-cross][PATCH 1/1] debug message for dependencies not found

2015-04-06 Thread Mark Hatle 
This and the other patch have been merged onto the cross_prelink_staging branch.

Please test that I merged it properly.  (Everything passed my basic testing, but
I haven't run it against any ARM/HF libraries or similar.)

--Mark

On 4/6/15 4:07 AM, Maninder Singh wrote:
 Hi,
 Same mail sent earlier Changing subject line, By mistake shared subject line 
 of other patch.
 
 prelink gives below error message for failure dependency:
 ./prelink: /test_binary: Could not find one of the dependencies
 
 This provides name of dependent library which is missing like below:
 ./prelink: /test_binary: Could not find one of the dependencies:
 ./prelink-rtld: error while loading shared libraries: libB.so: cannot open 
 shared object file: No such file or directory
 where libB.so is missing dependecy
 
 Signed-off-by: Maninder Singh maninder...@samsung.com
 Signed-off-by: Vaneet Narang v.nar...@samsung.com
 Reviewed-by: Ajeet Yadav ajee...@samsung.com
 Reviewed-by: Geon-ho Kim gh007@samsung.com
 ---
  src/gather.c |4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)
 
 diff --git a/src/gather.c b/src/gather.c
 index 5ccd243..4a3f428 100644
 --- a/src/gather.c
 +++ b/src/gather.c
 @@ -240,8 +240,8 @@ gather_deps (DSO *dso, struct prelink_entry *ent)
   if (q != NULL)
 {
   error (0, 0,
 -%s: Could not find one of the dependencies,
 -ent-filename);
 +%s: Could not find one of the dependencies:\n%s,
 +ent-filename, line);
   goto error_out;
 }
 }
 --
 
 
 Thanks 
 Maninder Singh
 

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

Re: [yocto] Kernel Panic: /sbin/init not found

2015-04-06 Thread Smith, Virgil 

 This is not true in the general case. You definitely can use
 IMAGE_INSTALL_append with a leading space to add items to an image, I just
 verified that now.

 I'm not clear on exactly what happened in the case we're discussing, at least
 initially it sounded like IMAGE_INSTALL = rather than IMAGE_INSTALL_append =
 was being used, which would definitely account for the behaviour described.

Digging testing reading
I don't know what happened in Chan Kit's case, but it looks like my earlier 
trouble was using IMAGE_INSTALL +=  from inside local.conf.  
IMAGE_INSTALL_append isn't applied until after parsing completes.  So here is 
one (or rather the) way to overcome the fact that local.conf is *parsed* too 
early for extending variables/configuration introduced later in the *parsing* 
chain.

So, my earlier statement that you can't use/rely on IMAGE_INSTALL_append from 
local.conf is flat wrong.

 The precedence of bb files and order of application of bbappends is controlled
 primarily by layer priorities; the order that layers appear in bblayers.conf
 shouldn't come into that (although it may if you have layers that have exactly
 the same priority set). The order of layers in bblayers.conf can influence the
 order in which bbclass and inc files are found *where files of the same name
 exist across different layers*, since these are found using BBPATH, which is
 prepended or appended to by each layer.conf file and thus the order in which
 those files are parsed is significant.

Thanks Paul, I wasn't sure I had the whole story.



Notice to recipient: This email is meant for only the intended recipient of the 
transmission, and may be a communication privileged by law, subject to export 
control restrictions or that otherwise contains proprietary information. If you 
receive this email by mistake, please notify us immediately by replying to this 
message and then destroy it and do not review, disclose, copy or distribute it. 
Thank you in advance for your cooperation.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto