valgrind-native

valgrind-native

[Woronicz, Bartosz ( NSN - PL/Wroclaw)]

Any ideas why I cannot build native valgrind ? http://pastebin.com/e2h6AWxN
"Missing or unbuildable dependency chain was: ['valgrind-native', 
'glibc-dbg-native']"

Also tried bitbake glibc-dbg . nothing provides that, but it is required 
in recipe


-- 
Kind regards,
Bartosz Woronicz
Engineer, Software Configuration (SCM)
NSN - PL/Wroclaw

Re: valgrind-native

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]

Hi,

On 11 February 2016 at 10:44, Woronicz, Bartosz ( NSN - PL/Wroclaw) <
bartosz.woronicz@nokia.com> wrote:

> Any ideas why I cannot build native valgrind ?
> http://pastebin.com/e2h6AWxN
> "Missing or unbuildable dependency chain was: ['valgrind-native',
> 'glibc-dbg-native']"
>
> Also tried bitbake glibc-dbg . nothing provides that, but it is required
> in recipe
>

The short answer is because valgrind doesn't have a native form yet.
Presumably you added BBCLASSEXTEND=native yourself, so you get to fix it. :)

valgrind RRECOMMENDS $(TCLIBC)-dbg as without debugging symbols it's fairly
useless, and TCLIBC is the variable for the libc being used (in your case,
glibc).  As a recommends, it will be built.

However, native recipes don't usually depend on the C library (base.bbclass
handles the addition of those core dependencies, and doesn't run on native
builds) so you've hit a new corner case.

The easy fix would be to remove the recommends in the native build case:

RRECOMMENDS_${PN}_class-native = ""

Surprisingly enough it then builds!

Also remember that we strip the native sysroot, so if you want a native
valgrind to be useful in any way you'll have to disable that too
(INHIBIT_SYSROOT_STRIP).

(it would probably be easier to use the host valgrind, to be honest)

Ross

[-- Attachment #2: Type: text/html, Size: 2331 bytes --]

Re: valgrind-native

[Woronicz, Bartosz ( NSN - PL/Wroclaw)]

[-- Attachment #1: Type: text/plain, Size: 2113 bytes --]

Hi Ross,

many thanks for nice explanation. At my shallow research, I notice, that 
valgrind is somewhat special demanding packages with debugging symbols, 
sooo... I actually don't need all packages to be unstripped. Only those 
I am developing and testing. Therefore i might need create some class 
that will require debug symbols.
And, propalby I will also need glibc with DBG symbols... or not ?


"Presumably you added BBCLASSEXTEND=native yourself, so you get to fix 
it. :)"
Indeed, I did so ;-]

Kind regards,
Bartosz Woronicz
Engineer, Software Configuration (SCM)
NSN - PL/Wroclaw

On 11.02.2016 11:57, EXT Burton, Ross wrote:
> Hi,
>
> On 11 February 2016 at 10:44, Woronicz, Bartosz ( NSN - PL/Wroclaw) 
> <bartosz.woronicz@nokia.com <mailto:bartosz.woronicz@nokia.com>> wrote:
>
>     Any ideas why I cannot build native valgrind ?
>     http://pastebin.com/e2h6AWxN
>     "Missing or unbuildable dependency chain was: ['valgrind-native',
>     'glibc-dbg-native']"
>
>     Also tried bitbake glibc-dbg . nothing provides that, but it is
>     required in recipe
>
>
> The short answer is because valgrind doesn't have a native form yet.  
> Presumably you added BBCLASSEXTEND=native yourself, so you get to fix 
> it. :)
>
> valgrind RRECOMMENDS $(TCLIBC)-dbg as without debugging symbols it's 
> fairly useless, and TCLIBC is the variable for the libc being used (in 
> your case, glibc). As a recommends, it will be built.
>
> However, native recipes don't usually depend on the C library 
> (base.bbclass handles the addition of those core dependencies, and 
> doesn't run on native builds) so you've hit a new corner case.
>
> The easy fix would be to remove the recommends in the native build case:
>
> RRECOMMENDS_${PN}_class-native = ""
>
> Surprisingly enough it then builds!
>
> Also remember that we strip the native sysroot, so if you want a 
> native valgrind to be useful in any way you'll have to disable that 
> too (INHIBIT_SYSROOT_STRIP).
>
> (it would probably be easier to use the host valgrind, to be honest)
>
> Ross


[-- Attachment #2: Type: text/html, Size: 4431 bytes --]

Re: valgrind-native

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 713 bytes --]

On 11 February 2016 at 12:38, Woronicz, Bartosz ( NSN - PL/Wroclaw) <
bartosz.woronicz@nokia.com> wrote:

> many thanks for nice explanation. At my shallow research, I notice, that
> valgrind is somewhat special demanding packages with debugging symbols,
> sooo... I actually don't need all packages to be unstripped. Only those I
> am developing and testing. Therefore i might need create some class that
> will require debug symbols.
> And, propalby I will also need glibc with DBG symbols... or not ?
>

Yes, if you set INHIBIT_SYSROOT_STRIP then all of the sysroots will be
unstripped, but you'll want all the debug symbols for the libraries that
are used from the host (such as glibc).

Ross

[-- Attachment #2: Type: text/html, Size: 1154 bytes --]