>
>
>
>> The change above have the effect of inhibiting the package strip even if
>> ptest is not enabled at all. I think this have to be something specific to
>> ptest.
>> You may consider using INSANE_SKIP_${PN}-ptest [1] and add unstripped
>> binaries needed for ptest in {PN}-ptest (along with the original - stripped
>> - ones)
>>
>
> I didn't get how unstripped and stripped binaries can co-exist in a single
> package called ${PN}-test.
> The split_and_strip_files function keeps files containing debug symbols in
> a separate directory
> ( like ../.debug/..). Do you mean to say include files containing debug
> symbols (i,e debugdirectory) in ${PN}-test package and
> set INSANE_SKIP_${PN}-ptest += "debug-files"
> to prevent packaging .debug directories in non -dbg package.
>
> This doesn't help, as run-coredump-unwind requires unstripped "crasher"
> program to be present at target, to get procedure names using libuwind
> APIs.
>
>
> or simply consider the appropriate tests as XFAIL for openembedded.
>>
> Yes, for such test (e.g: run-coredump-unwind) XFAIL is fine, if
> INHIBIT_PACKAGE_STRIP = "1" is
> not used.
>
>
However, I have sent a v2 patch, marking test cases which depend on
unstripped binaries as expected failures and removed INHIBIT_PACKAGE_STRIP
= "1" line from the earlier patch.
Made sure run-check-namespace test passes with libunwind library containing
debug symbols.
Regards,
Jagadeesh
>
>>
>
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
