| View previous topic :: View next topic |
| Author |
Message |
trapni
Retired Dev
Joined: 16 May 2002
Posts: 251
Location: Germany/Berlin
|
 Posted: Wed Jan 14, 2004 8:53 am Post subject: valgrind doesn't emerge :( |
 |
|
hi,
I was using valgrind in kernel 2.4 environment, but now, I can't emerge it anylonger.
My current system is
- Linux battousai 2.6.0 #2 SMP Mon Jan 5 23:09:21 CET 2004 i686 AMD Athlon(tm) XP 1700+ AuthenticAMD GNU/Linux
- gcc version 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
- sys-libs/glibc-2.3.3_pre20031222
(with useflag nptl enabled, just if matters).
valgrind's emerge compiler error is | Code: | [.....]
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./demangle -I../include -DVG_LIBDIR="\"/usr/lib"\" -Winline -Wall -Wshadow -O -fno-omit-frame-pointer -mpreferred-stack-boundary=2 -g -fpic -MT vg_scheduler.o -MD -MP -MF ".deps/vg_scheduler.Tpo" \
-c -o vg_scheduler.o `test -f 'vg_scheduler.c' || echo './'`vg_scheduler.c; \
then mv -f ".deps/vg_scheduler.Tpo" ".deps/vg_scheduler.Po"; \
else rm -f ".deps/vg_scheduler.Tpo"; exit 1; \
fi
vg_scheduler.c: In function `release_one_thread_waiting_on_mutex':
vg_scheduler.c:1986: error: union has no member named `__m_owner'
vg_scheduler.c:1991: error: union has no member named `__m_count'
vg_scheduler.c:1992: error: union has no member named `__m_owner'
vg_scheduler.c:1998: error: union has no member named `__m_owner'
vg_scheduler.c:1998: error: `_pthread_descr' undeclared (first use in this function)
vg_scheduler.c:1998: error: (Each undeclared identifier is reported only once
vg_scheduler.c:1998: error: for each function it appears in.)
vg_scheduler.c:1998: error: syntax error before "i"
vg_scheduler.c: In function `do_pthread_mutex_lock':
vg_scheduler.c:2042: error: union has no member named `__m_kind'
vg_scheduler.c:2052: error: union has no member named `__m_count'
[........] |
*hmpf*
can anyone help?
many thanks,
Christian Parpart. |
|
| Back to top |
|
 |
Anime_Fan
Guru
Joined: 01 Jul 2003
Posts: 366
Location: Linköping, Sweden
|
|
| Back to top |
|
|
()
l33t
Joined: 25 Nov 2002
Posts: 610
|
| Posted: Thu Jan 15, 2004 2:58 pm Post subject: |
|
|
| This is an NPTL problem, still unresolved alas. |
|
| Back to top |
|
|
trapni
Retired Dev
Joined: 16 May 2002
Posts: 251
Location: Germany/Berlin
|
| Posted: Thu Jan 22, 2004 12:42 pm Post subject: |
|
|
| () wrote: | | This is an NPTL problem, still unresolved alas. |
Yeah, unfortunately, I googled a bit around, and found out, that this is even marked as a BUG in their bugzilla-base.
It's really bad to switch back to LinuxThreads on my desktop till this issue has been solved 
thx anyway 
trapni. |
|
| Back to top |
|
|
regeya
Apprentice
Joined: 28 Jul 2002
Posts: 270
Location: Desoto, IL, USA
|
| Posted: Sat Jan 24, 2004 6:18 am Post subject: |
|
|
| Heh. Noticed when Googling that a Gentoo developer had posted a question about valgrind to a Fedora mailing list. Naughty, naughty. |
|
| Back to top |
|
|
()
l33t
Joined: 25 Nov 2002
Posts: 610
|
| Posted: Sat Jan 24, 2004 10:31 am Post subject: |
|
|
| Probably because NPTL is initially a RedHat project? |
|
| Back to top |
|
|
regeya
Apprentice
Joined: 28 Jul 2002
Posts: 270
Location: Desoto, IL, USA
|
| Posted: Sat Jan 24, 2004 4:18 pm Post subject: |
|
|
| () wrote: | | Probably because NPTL is initially a RedHat project? |
I really must stop posting smartass comments with a wink because it seems that nobody understands that smartass comment + wink means that more than likely I understand why, but I've decided to be a wiseass anyway. *sigh*
Yes, yes. NPTL is initially a RedHat project. They would be likely to know how to build valgrind. I just thought it was a bit funny that a Gentoo developer had posted to Fedora's mailing list asking for help, though right now I'm having trouble remembering why I thought it was funny. Isn't this about the point in the conversation when Lovechild pops in and says "I don't use Gentoo anymore because I like Fedora now"? Heh...just kidding, Lovechild, everyone else.
This wouldn't be a problem for me if I weren't stubbornly trying to run KDE 3.2rc1 on an NPTL system, and trying to install digikam. For some reason, when I try to emerge digikam while accepting the ~x86 keyword, kdesdk requires a new version of valgrind. Ungh.
Temporary stopgap measure: gtkam worksforme. |
|
| Back to top |
|
|
()
l33t
Joined: 25 Nov 2002
Posts: 610
|
| Posted: Sat Jan 24, 2004 5:23 pm Post subject: |
|
|
| Yeah, I figured it was ironically meant. But anyway, posting to a Fedora list is probably not such a bad idea. It might catch the attention of someone actually involved with NPTL, such as Ulrich Drepper. As far as I know the Valgrind guys have been aware of the issue for some time, and probably Mr. Drepper as well. |
|
| Back to top |
|
|
tommydmc
n00b
Joined: 10 Aug 2003
Posts: 4
Location: Annapolis, MD
|
| Posted: Mon Feb 09, 2004 4:06 pm Post subject: valgrind and NPTL |
|
|
POSIX spec says the different types like 'pthread_attr_t' are opaque, allowing for different implementations. Sadly, valgrind, an AWESOME tool, relies on the implementation specific details of the glibc pthreads library. I looked at the nptl implementation hoping to create a patch but found the implementation details grossly different.
What does that mean: if you want valgrind and associated cool tools like kcachegrind, DON'T use nptl until the valgrind team provides a patch, which may or may not happen anytime soon. Or, if you want a non-threading valgrind, let me know and i can cut it up as a community service  ...BUT this would not support pthreads which i rely on often.
-tom
ps - hopefully they will prove me wrong, because my dev box uses nptl and i want my valgrind back!
_________________
[b]Doh![\b] |
|
| Back to top |
|
|
phlashback
Tux's lil' helper
Joined: 27 Jul 2002
Posts: 142
Location: Normal
|
| Posted: Wed Feb 11, 2004 10:11 pm Post subject: |
|
|
there is active work going on to fix this.... there is currently a patch against cvs
http://bugs.kde.org/show_bug.cgi?id=69616
no there is no ebuild 
_________________
The terrible thing about hell is that when you're there you can't even tell as you move through this life you love so you could be there and not even know |
|
| Back to top |
|
|
_puck_
Tux's lil' helper
Joined: 12 May 2002
Posts: 111
Location: Kaiserslautern / Germany
|
| Posted: Thu Mar 11, 2004 3:33 pm Post subject: |
|
|
The bug under
http://bugs.kde.org/show_bug.cgi?id=69616
seems to be closed
| Quote: |
------- Additional Comment #46 From Nicholas Nethercote 2004-03-10 15:29 -------
No complaints about the commit in 12 days, so I'll close this.
|
I have build up with nptl-support and need to have kdesdk emerged. valgrind is a dependency to kdesdk. Does anyone know a workarround for emerging kdesdk?
_________________
regards
puck
___________________________
#There is more than one way to do it. |
|
| Back to top |
|
|
schnake
n00b
Joined: 03 Dec 2003
Posts: 49
Location: Siegburg / Germany
|
| Posted: Thu Mar 11, 2004 4:06 pm Post subject: |
|
|
You may try something like
| Code: | prompt# emerge inject dev-util/calltree-0.9.6
prompt# DO_NOT_COMPILE="kcachegrind" emerge kdesdk |
I do not know what kdesdk component(s) depend on calltree (which in turn depends on valgrind), so "kcachegrind" is just a wild guess to start with.
[EDIT]Changed inject from valgrind to calltree.[/EDIT] |
|
| Back to top |
|
|
_puck_
Tux's lil' helper
Joined: 12 May 2002
Posts: 111
Location: Kaiserslautern / Germany
|
| Posted: Fri Mar 12, 2004 12:19 am Post subject: |
|
|
Just to keep you informed ...
kdesdk compiled flawlessly with your trick ... kcachgrind seems to be the only application depending on valgrind and calltree.
_________________
regards
puck
___________________________
#There is more than one way to do it. |
|
| Back to top |
|
|
schnake
n00b
Joined: 03 Dec 2003
Posts: 49
Location: Siegburg / Germany
|
| Posted: Fri Mar 12, 2004 9:06 am Post subject: |
|
|
Thanks for your feedback.
Good to know that this works, 'cause I'll need it myself as soon as the other KDE 3.2.1 components finish compile. |
|
| Back to top |
|
|
_puck_
Tux's lil' helper
Joined: 12 May 2002
Posts: 111
Location: Kaiserslautern / Germany
|
| Posted: Sat Mar 20, 2004 12:57 pm Post subject: valgrind-2.1.1 |
|
|
I copied the valgrind-2.1.0.ebuild to valgrind-2.1.1.ebuild and made a digest for it ... then it emerged just fine.
Seems they have fixed those ntpl problems. I just have to check, if it also operates like normal.
I thought, maybe this is from interesting for you.
edit: FYI ... kdesdk-3.2.1 compiles fine against it.
_________________
regards
puck
___________________________
#There is more than one way to do it. |
|
| Back to top |
|
|
[::Shansa::]
n00b
Joined: 16 Mar 2004
Posts: 37
|
| Posted: Sat Mar 20, 2004 11:58 pm Post subject: Re: valgrind-2.1.1 |
|
|
| _puck_ wrote: | I copied the valgrind-2.1.0.ebuild to valgrind-2.1.1.ebuild and made a digest for it ... then it emerged just fine.
Seems they have fixed those ntpl problems. I just have to check, if it also operates like normal.
I thought, maybe this is from interesting for you.
edit: FYI ... kdesdk-3.2.1 compiles fine against it. |
Too bas calltree 0.9.6 ebuild still wants valgrind 2.0.0 -- Is Caleb Dead or what? |
|
| Back to top |
|
|
pandaemonium
n00b
Joined: 05 Apr 2004
Posts: 6
|
| Posted: Mon Apr 05, 2004 12:11 am Post subject: Re: valgrind-2.1.1 |
|
|
| [::Shansa::] wrote: |
Too bas calltree 0.9.6 ebuild still wants valgrind 2.0.0 -- Is Caleb Dead or what? |
Too bad there is no ebuild for either calltree 0.9.7 or valgrind 2.1.1 yet...
cause those both are the latest versions and work fine and stable for me...
but... just copying calltree 0.9.6 / valgrind 2.1.0 ebuilds too latest version numbers and recreating digest lets you emerge them without pain...
edit:
since yesterday ebuilds for both are available... just had to help Caleb a bit by providing him some to add... hehe |
|
| Back to top |
|
|
|
Portage & Programming
