FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 09-14-2012, 07:48 PM
Mick
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 
Old 09-14-2012, 07:59 PM
Ellen Taylor
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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.
 
Old 09-14-2012, 07:59 PM
Paul Hartman
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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.
 
Old 09-14-2012, 08:01 PM
Mariusz Ceier
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 
Old 09-14-2012, 08:04 PM
Sascha Cunz
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 
Old 09-14-2012, 08:09 PM
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 
Old 09-14-2012, 08:13 PM
Marc Joliet
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 
Old 09-14-2012, 08:19 PM
Nikos Chantziaras
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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"
 
Old 09-14-2012, 08:44 PM
Michael Mol
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 
Old 09-14-2012, 10:43 PM
Mick
 
Default dev-util/valgrind-3.7.0-r4 and glibc

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
 

Thread Tools




All times are GMT. The time now is 09:14 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org