OK.

On Tue, Sep 24, 2013 at 11:29 AM, Amit Tomer <amittome...@gmail.com> wrote:

> Yes Jegan ,that's what we did yesterday and we have now non -striped .bins
> Thanks for your response
>
>
> On Tue, Sep 24, 2013 at 10:57 AM, Jegan Chandru <pcje...@gmail.com> wrote:
>
>> Hi Amit,
>>
>> If you want the binaries not to be stripped, try
>> adding INHIBIT_PACKAGE_STRIP = "1" to valgrind recipe.
>> This will disable stripping the binaries as you have mentioned.
>>
>> Cheers,
>> JC
>>
>>
>> On Mon, Sep 23, 2013 at 7:03 PM, Amit Tomer <amittome...@gmail.com>wrote:
>>
>>> Thanks Paul for your response.Below file is nmy valgrind recipe file
>>> which is from poky/meta/valgrind
>>>
>>> DESCRIPTION = "Valgrind memory debugger"
>>> HOMEPAGE = "http://valgrind.org/";
>>> BUGTRACKER = "http://valgrind.org/support/bug_reports.html";
>>> LICENSE = "GPLv2 & GPLv2+ & BSD"
>>> LIC_FILES_CHKSUM = "file://COPYING;md5=c46082167a314d785d012a244748d803 \
>>>
>>> file://include/pub_tool_basics.h;beginline=1;endline=29;md5=6b18ba0139d10678ce3a9969f68e4c6d
>>> \
>>>
>>> file://include/valgrind.h;beginline=1;endline=56;md5=b6bb5ab625a759823e17197ec3e2ee83
>>> \
>>>
>>> file://COPYING.DOCS;md5=8fdeb5abdb235a08e76835f8f3260215"
>>>
>>> X11DEPENDS = "virtual/libx11"
>>> DEPENDS = "${@base_contains('DISTRO_FEATURES', 'x11', '${X11DEPENDS}',
>>> '', d)}"
>>> PR = "r8"
>>>
>>> SRC_URI = "http://www.valgrind.org/downloads/valgrind-${PV}.tar.bz2 \
>>>            file://fix_issue_caused_by_ccache.patch \
>>>            file://fix_unsupporting_kernel_3.patch \
>>>            file://fixed-perl-path.patch \
>>>            file://Added-support-for-PPC-instructions-mfatbu-mfatbl.patch
>>> \
>>>            file://configure-with-newer-glibc.patch \
>>>            file://sepbuildfix.patch \
>>>           "
>>>
>>> SRC_URI[md5sum] = "288758010b271119a0ffc0183f1d6e38"
>>> SRC_URI[sha256sum] =
>>> "473be00576bed311a662b277a2bfbe97d9cca4058e68619a0e420c9fc19958db"
>>>
>>> COMPATIBLE_HOST = '(i.86|x86_64|powerpc|powerpc64).*-linux'
>>> COMPATIBLE_HOST_armv7a = 'arm.*-linux'
>>>
>>> inherit autotools
>>>
>>> EXTRA_OECONF = "--enable-tls --without-mpicc"
>>> EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi
>>> --without-mpicc"
>>> EXTRA_OEMAKE = "-w"
>>> PARALLEL_MAKE = ""
>>>
>>> do_install_append () {
>>>     install -m 644 ${B}/default.supp ${D}/${libdir}/valgrind/
>>> }
>>>
>>> FILES_${PN}-dbg += "${libdir}/${PN}/*/.debug/*"
>>> RRECOMMENDS_${PN}_powerpc += "${TCLIBC}-dbg"
>>> RRECOMMENDS_${PN}_powerpc64 += "${TCLIBC}-dbg"
>>> RRECOMMENDS_${PN}_armv7a += "${TCLIBC}-dbg"
>>>
>>>
>>> Now this file will compile valgrind binary and install it
>>> /usr/lib/valgrind for my package
>>>
>>> Now when I go
>>> to  /tmp/work/${workdir}/image-fzm-k2-debug/1.0-r0/rootfs/usr/lib/valgrind
>>>
>>> I can see the vgpreload_memcheck-arm-linux.so is stripped which should
>>> be non stripped for our valgrind to work well
>>>
>>> file vgpreload_memcheck-arm-linux.so
>>> vgpreload_memcheck-arm-linux.so: ELF 32-bit LSB shared object, ARM,
>>> version 1 (SYSV), stripped
>>>
>>>
>>> Now how our valgrind recipe stripping these images since I am new to
>>> yocto finding it difficult to solve it.
>>>
>>
>>>
>>>
>>> On Mon, Sep 23, 2013 at 6:32 PM, Paul Barker <p...@paulbarker.me.uk>wrote:
>>>
>>>> On 23 September 2013 11:00, Amit Tomer <amittome...@gmail.com> wrote:
>>>> > I am new to OpenEmbedded and facing an issue where our valgrind is not
>>>> > working,
>>>> > Valgrind bin comes as non striped image after compilation but while
>>>> packing
>>>> > it to squashfs image ,it become striped one and fails to run on
>>>> target.
>>>> >
>>>> > So how do we pack it as non striped one ??
>>>> >
>>>>
>>>> It's likely in <packagename>-dbg (so probably valgrind-dbg). Try
>>>> adding that to your IMAGE_INSTALL variable.
>>>>
>>>> --
>>>> Paul Barker
>>>>
>>>> Email: p...@paulbarker.me.uk
>>>> http://www.paulbarker.me.uk
>>>>
>>>
>>>
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
>>>
>>>
>>
>


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

Reply via email to