dev-util/valgrind-3.7.0-r4 and glibc

09-14-2012, 07:48 PM

I got this message in elog:

* Messages for package dev-util/valgrind-3.7.0-r4:

* Valgrind will not work if glibc does not have debug symbols.
* To fix this you can add splitdebug to FEATURES in make.conf
* and remerge glibc. See:
* https://bugs.gentoo.org/show_bug.cgi?id=214065
* https://bugs.gentoo.org/show_bug.cgi?id=274771
* https://bugs.gentoo.org/show_bug.cgi?id=388703

but my glibc has no splitdebug USE flags:

[i] sys-libs/glibc

Installed versions: 2.15-r2(2.2)^s(08:44:11 08/10/12)(multilib -
crosscompile_opts_headers-only -debug -gd -hardened -profile -selinux -
vanilla)

As a matter of fact nothing has:

$ euse -i splitdebug
global use flags (searching: splitdebug)
************************************************** **********
no matching entries found

local use flags (searching: splitdebug)
************************************************** **********
no matching entries found

Is this a typo?
--
Regards,
Mick

09-14-2012, 07:59 PM

Mick <michaelkintzios@gmail.com> writes:

> I got this message in elog:
>
> * Messages for package dev-util/valgrind-3.7.0-r4:
>
> * Valgrind will not work if glibc does not have debug symbols.
> * To fix this you can add splitdebug to FEATURES in make.conf
> * and remerge glibc. See:
> * https://bugs.gentoo.org/show_bug.cgi?id=214065
> * https://bugs.gentoo.org/show_bug.cgi?id=274771
> * https://bugs.gentoo.org/show_bug.cgi?id=388703
>
> but my glibc has no splitdebug USE flags:
>
> [i] sys-libs/glibc
>
> Installed versions: 2.15-r2(2.2)^s(08:44:11 08/10/12)(multilib -
> crosscompile_opts_headers-only -debug -gd -hardened -profile -selinux -
> vanilla)
>
>
> As a matter of fact nothing has:
>
> $ euse -i splitdebug
> global use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
> local use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
>
> Is this a typo?

It's not a use flag. It's a portage feature that's added in
make.conf. Just add 'FEATURES=splitdebug' to your make.conf.

09-14-2012, 07:59 PM

On Fri, Sep 14, 2012 at 2:48 PM, Mick <michaelkintzios@gmail.com> wrote:
> I got this message in elog:
>
> * Messages for package dev-util/valgrind-3.7.0-r4:
>
> * Valgrind will not work if glibc does not have debug symbols.
> * To fix this you can add splitdebug to FEATURES in make.conf
> * and remerge glibc. See:
> * https://bugs.gentoo.org/show_bug.cgi?id=214065
> * https://bugs.gentoo.org/show_bug.cgi?id=274771
> * https://bugs.gentoo.org/show_bug.cgi?id=388703
>
> but my glibc has no splitdebug USE flags:
>
> [i] sys-libs/glibc
>
> Installed versions: 2.15-r2(2.2)^s(08:44:11 08/10/12)(multilib -
> crosscompile_opts_headers-only -debug -gd -hardened -profile -selinux -
> vanilla)
>
>
> As a matter of fact nothing has:
>
> $ euse -i splitdebug
> global use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
> local use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
>
> Is this a typo?

Please read it again, it says add it to FEATURES in make.conf, not a
USE flag.

09-14-2012, 08:01 PM

No, it's not a typo - you have to add splitdebug to FEATURES variable
in /etc/make.conf (or /etc/portage/make.conf). Splitdebug is not a USE
flag.

On 14 September 2012 21:48, Mick <michaelkintzios@gmail.com> wrote:
> I got this message in elog:
>
> * Messages for package dev-util/valgrind-3.7.0-r4:
>
> * Valgrind will not work if glibc does not have debug symbols.
> * To fix this you can add splitdebug to FEATURES in make.conf
> * and remerge glibc. See:
> * https://bugs.gentoo.org/show_bug.cgi?id=214065
> * https://bugs.gentoo.org/show_bug.cgi?id=274771
> * https://bugs.gentoo.org/show_bug.cgi?id=388703
>
> but my glibc has no splitdebug USE flags:
>
> [i] sys-libs/glibc
>
> Installed versions: 2.15-r2(2.2)^s(08:44:11 08/10/12)(multilib -
> crosscompile_opts_headers-only -debug -gd -hardened -profile -selinux -
> vanilla)
>
>
> As a matter of fact nothing has:
>
> $ euse -i splitdebug
> global use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
> local use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
>
> Is this a typo?
> --
> Regards,
> Mick

09-14-2012, 08:04 PM

Am Freitag, 14. September 2012, 20:48:23 schrieb Mick:

> I got this message in elog:

>

> * Messages for package dev-util/valgrind-3.7.0-r4:

>

> * Valgrind will not work if glibc does not have debug symbols.

> * To fix this you can add splitdebug to FEATURES in make.conf

> * and remerge glibc. See:

> * https://bugs.gentoo.org/show_bug.cgi?id=214065

> * https://bugs.gentoo.org/show_bug.cgi?id=274771

> * https://bugs.gentoo.org/show_bug.cgi?id=388703

>

> but my glibc has no splitdebug USE flags:

>

> [i] sys-libs/glibc

>

> Installed versions: 2.15-r2(2.2)^s(08:44:11 08/10/12)(multilib -

> crosscompile_opts_headers-only -debug -gd -hardened -profile -selinux -

> vanilla)

>

>

> As a matter of fact nothing has:

>

> $ euse -i splitdebug

> global use flags (searching: splitdebug)

> ************************************************** **********

> no matching entries found

>

> local use flags (searching: splitdebug)

> ************************************************** **********

> no matching entries found

>

>

> Is this a typo?

*

Actually not, splitdebug is not a USE-Flag but rather a FEATURE of

the package manager.

*

See [1] and [2] for explanations. [2] actually show how to enable

splitdebug _just_ for valgrind.

*

Cheers

Sascha

*

[1]http://www.baptiste-wicht.com/2012/04/install-valgrind-on-gentoo-linux/

[2] http://us.generation-nt.com/answer/gentoo-user-per-package-splitdebug-feature-help-204537341.html

09-14-2012, 08:09 PM

Mick <michaelkintzios@gmail.com> wrote:

> I got this message in elog:
>
> * Messages for package dev-util/valgrind-3.7.0-r4:
>
> * Valgrind will not work if glibc does not have debug symbols.
> * To fix this you can add splitdebug to FEATURES in make.conf
> * and remerge glibc. See:
> * https://bugs.gentoo.org/show_bug.cgi?id=214065
> * https://bugs.gentoo.org/show_bug.cgi?id=274771
> * https://bugs.gentoo.org/show_bug.cgi?id=388703
>
> but my glibc has no splitdebug USE flags:
>
> [i] sys-libs/glibc
>
> Installed versions: 2.15-r2(2.2)^s(08:44:11 08/10/12)(multilib -
> crosscompile_opts_headers-only -debug -gd -hardened -profile -selinux -
> vanilla)
>
>
> As a matter of fact nothing has:
>
> $ euse -i splitdebug
> global use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
> local use flags (searching: splitdebug)
> ************************************************** **********
> no matching entries found
>
>
> Is this a typo?

Nope, it goes in make.conf as a feature -- see the man page for more
details. Mine is
FEATURES="${FEATURES} -stricter -distcc -ccache splitdebug"

Hope this helps.

--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici
covici@ccs.covici.com

09-14-2012, 08:13 PM

Am Fri, 14 Sep 2012 20:48:23 +0100
schrieb Mick <michaelkintzios@gmail.com>:

> I got this message in elog:
>
> * Messages for package dev-util/valgrind-3.7.0-r4:
>
> * Valgrind will not work if glibc does not have debug symbols.
> * To fix this you can add splitdebug to FEATURES in make.conf
> * and remerge glibc. See:
> * https://bugs.gentoo.org/show_bug.cgi?id=214065
> * https://bugs.gentoo.org/show_bug.cgi?id=274771
> * https://bugs.gentoo.org/show_bug.cgi?id=388703
>
> but my glibc has no splitdebug USE flags:
[...]
> Is this a typo?

No, it's a FEATURE

. It even says as much in the emerge output. It's
explained in the mentioned bugs and of course in the man pages portage(5) and
make.conf(5).

But to summarize: as a valgrind user myself I have FEATURES="${FEATURES}
splitdebug" in /etc/portage/env/sys-libs/glibc.

HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup

09-14-2012, 08:19 PM

On 14/09/12 22:48, Mick wrote:

I got this message in elog:

* Messages for package dev-util/valgrind-3.7.0-r4:

* Valgrind will not work if glibc does not have debug symbols.
* To fix this you can add splitdebug to FEATURES in make.conf
* and remerge glibc. See:
* https://bugs.gentoo.org/show_bug.cgi?id=214065
* https://bugs.gentoo.org/show_bug.cgi?id=274771
* https://bugs.gentoo.org/show_bug.cgi?id=388703

but my glibc has no splitdebug USE flags

What the other posters said, except that you shouldn't add "splitdebug"
in your make.conf. If you do that, it will affect all packages.

What you do instead is put this text into
/etc/portage/env/sys-libs/glibc (yes, it must be a text file, not a
directory):

CFLAGS="${CFLAGS} -g"
CXXFLAGS="${CXXFLAGS} -g"
FEATURES="${FEATURES} splitdebug"

09-14-2012, 08:44 PM

On Fri, Sep 14, 2012 at 4:19 PM, Nikos Chantziaras <realnc@gmail.com> wrote:
> On 14/09/12 22:48, Mick wrote:
>>
>> I got this message in elog:
>>
>> * Messages for package dev-util/valgrind-3.7.0-r4:
>>
>> * Valgrind will not work if glibc does not have debug symbols.
>> * To fix this you can add splitdebug to FEATURES in make.conf
>> * and remerge glibc. See:
>> * https://bugs.gentoo.org/show_bug.cgi?id=214065
>> * https://bugs.gentoo.org/show_bug.cgi?id=274771
>> * https://bugs.gentoo.org/show_bug.cgi?id=388703
>>
>> but my glibc has no splitdebug USE flags
>
>
> What the other posters said, except that you shouldn't add "splitdebug" in
> your make.conf. If you do that, it will affect all packages.
>
> What you do instead is put this text into /etc/portage/env/sys-libs/glibc
> (yes, it must be a text file, not a directory):
>
> CFLAGS="${CFLAGS} -g"
> CXXFLAGS="${CXXFLAGS} -g"
> FEATURES="${FEATURES} splitdebug"

I'm fairly sure (I could be wrong) that splitdebug doesn't cause -g or
a derivative to be added to CFLAGS. Hence why I have "-ggdb" in my
CFLAGS.

(All in make.conf. Given splitdebug, I haven't heard a solid reason not to.)

--
:wq

09-14-2012, 10:43 PM

On Friday 14 Sep 2012 21:44:43 Michael Mol wrote:
> On Fri, Sep 14, 2012 at 4:19 PM, Nikos Chantziaras <realnc@gmail.com> wrote:
> > On 14/09/12 22:48, Mick wrote:
> >> I got this message in elog:
> >>
> >> * Messages for package dev-util/valgrind-3.7.0-r4:
> >> * Valgrind will not work if glibc does not have debug symbols.
> >> * To fix this you can add splitdebug to FEATURES in make.conf
> >> * and remerge glibc. See:
> >> * https://bugs.gentoo.org/show_bug.cgi?id=214065
> >> * https://bugs.gentoo.org/show_bug.cgi?id=274771
> >> * https://bugs.gentoo.org/show_bug.cgi?id=388703
> >>
> >> but my glibc has no splitdebug USE flags
> >
> > What the other posters said, except that you shouldn't add "splitdebug"
> > in your make.conf. If you do that, it will affect all packages.
> >
> > What you do instead is put this text into /etc/portage/env/sys-libs/glibc
> > (yes, it must be a text file, not a directory):
> >
> > CFLAGS="${CFLAGS} -g"
> > CXXFLAGS="${CXXFLAGS} -g"
> > FEATURES="${FEATURES} splitdebug"
>
> I'm fairly sure (I could be wrong) that splitdebug doesn't cause -g or
> a derivative to be added to CFLAGS. Hence why I have "-ggdb" in my
> CFLAGS.
>
> (All in make.conf. Given splitdebug, I haven't heard a solid reason not
> to.)

Thank you all for your answers. I should have slowed down to read the elog
more carefully!
--
Regards,
Mick