Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 618382 - dev-util/valgrind-3.10.1 requires glibc 2.2-2.22
Summary: dev-util/valgrind-3.10.1 requires glibc 2.2-2.22
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Anthony Basile
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-13 19:45 UTC by Matthew Millar
Modified: 2017-06-10 18:13 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Millar 2017-05-13 19:45:43 UTC
Configuration fails for Valgrind 3.10.1 when glibc is 2.23+.

This problem doesn't for Valgrind 3.11.0 because configure checks for 2.2*), rather than specific 2.# versions.

Therefore:
1) Valgrind-3.10.1 requires a glibc dependency of >=2.2 and <2.23 (needs to be tested, because configure reports 2.2-2.19).
2) Valgrind-3.11.0 and prbably later requires a glibc dependency of >=2.2.
Comment 1 Austin English (RETIRED) gentoo-dev 2017-05-27 05:54:58 UTC
valgrind-3.10.1.ebuild
valgrind-3.11.0.ebuild
valgrind-3.12.0.ebuild

all build for me with sys-libs/glibc-2.23-r3
Comment 2 Austin English (RETIRED) gentoo-dev 2017-06-05 22:41:58 UTC
(In reply to Austin English from comment #1)
> valgrind-3.10.1.ebuild
> valgrind-3.11.0.ebuild
> valgrind-3.12.0.ebuild
> 
> all build for me with sys-libs/glibc-2.23-r3

These three also all build for me with glibc 2.21-r2 in an old chroot I still had.

I'm unable to reproduce this at all. @blueness, can you?
Comment 3 Anthony Basile gentoo-dev 2017-06-10 18:13:19 UTC
(In reply to Austin English from comment #2)
> (In reply to Austin English from comment #1)
> > valgrind-3.10.1.ebuild
> > valgrind-3.11.0.ebuild
> > valgrind-3.12.0.ebuild
> > 
> > all build for me with sys-libs/glibc-2.23-r3
> 
> These three also all build for me with glibc 2.21-r2 in an old chroot I
> still had.
> 
> I'm unable to reproduce this at all. @blueness, can you?

i finished stabilizing 3.12.0 and dropped 3.10.1 and 3.11.1.  we should be all good now.