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#31714 - [valgrind] package x86 support even on x86_64
Attached to Project:
Arch Linux
Opened by Kenneth Graunke (Kayden) - Friday, 28 September 2012, 07:07 GMT
Last edited by Allan McRae (Allan) - Friday, 28 September 2012, 08:33 GMT
Opened by Kenneth Graunke (Kayden) - Friday, 28 September 2012, 07:07 GMT
Last edited by Allan McRae (Allan) - Friday, 28 September 2012, 08:33 GMT
|
DetailsDescription:
After installing valgrind 3.8.1-1 on x86_64, attempting to run 'valgrind <some 32-bit binary>' gives: valgrind: failed to start tool 'memcheck' for platform 'x86-linux': No such file or directory Being able to debug both 32-bit and 64-bit applications is extremely useful for those of us that work on graphics drivers, as we end up dealing with a variety of games built for one architecture or the other. Valgrind already supports installing a single version that can do both. However, Arch's PKGBUILD disables it explicitly: if [ "${CARCH}" = "x86_64" ]; then ./configure --prefix=/usr --mandir=/usr/share/man --enable-only64bit else ./configure --prefix=/usr --mandir=/usr/share/man fi Would it be possible to either have the [multilib] repository provide a version of valgrind built without --enable-only64bit? Or, a second lib32-valgrind package? Thanks! Additional information: - I have the [multilib] repository enabled. |
This task depends upon
Closed by Allan McRae (Allan)
Friday, 28 September 2012, 08:33 GMT
Reason for closing: Won't implement
Additional comments about closing: [extra] is pure x86_64. No-one wants to support it on [multilib]
Friday, 28 September 2012, 08:33 GMT
Reason for closing: Won't implement
Additional comments about closing: [extra] is pure x86_64. No-one wants to support it on [multilib]