Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1203 - VALGRIND 2.0.0 / NPTL
Attached to Project:
Arch Linux
Opened by TORIN Daniel (torindan) - Thursday, 29 July 2004, 11:05 GMT
Last edited by Dale Blount (dale) - Thursday, 29 July 2004, 12:00 GMT
Opened by TORIN Daniel (torindan) - Thursday, 29 July 2004, 11:05 GMT
Last edited by Dale Blount (dale) - Thursday, 29 July 2004, 12:00 GMT
|
DetailsI have NPTL enabled glibc, and when launching valgring a receive following error:
true: relocation error: /usr/lib/valgrind/valgrind.so: symbol __libc_accept, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Tried to makepkg with PKGBUILD from ABS, got errors (maybe due gcc3.4.1) The only solution is to upgrade to 2.1.2 (development release) which compiles cleanly and works fine (for me) Valgrind's webpage says that it supports NPTL and gcc3.4.1, so it's definitly better then 2.0.0. Don't know if arch will include dev.release into official packages, but we can try. Anyway people that use valgrind are developers and can take the risk. |
This task depends upon
Closed by Aurelien Foret (aurelien.foret)
Saturday, 04 September 2004, 21:34 GMT
Reason for closing: Fixed
Saturday, 04 September 2004, 21:34 GMT
Reason for closing: Fixed
Comment by Aurelien Foret (aurelien.foret) -
Saturday, 04 September 2004, 21:34 GMT
Fixed with package upgrade to 2.2.0