On Tue, Nov 12, 2013 at 11:13:54PM +0100, Balint Reczey wrote: > Hi, > > On 08/07/2013 11:01 AM, Alessandro Ghedini wrote: > > On mar, ago 06, 2013 at 01:14:19 -0400, Yaroslav Halchenko wrote: > >> Package: valgrind > >> Version: 1:3.8.1-4 > >> Followup-For: Bug #701691 > >> > >> Just ran into this issue on our build box abel -- I was genuinly surprised > >> to > >> see valgrind available for that architecture so immediately jumped to > >> install > >> it -- but as this report shows, it is next to useless on armel, so why we > >> carry > >> armel build at all thus confusing poor users? > > > > It was enabled to let armel users with ARMv7 hardware to use valgrind. At > > least > > that's what I understood from #592614, but I wasn't the maintainer at the > > time. > > > >> may be > >> > >> override_dh_auto_test: > >> : # do nothing for now > >> > >> should be tuned up to run at least few really quick tests > > > > There's no such thing as "quick tests" in valgrind sources, and the > > regression > > and performance test suites (intended for the valgrind developers) are way > > too > > heavy and fragile to be enabled on Debian's buildds. > Something as little as "valgrind ls" would do it. > It could have saved some time from me when I tried running valgrind on > armel on Wheezy...
Did you read the other part of my email?
> > It was enabled to let armel users with ARMv7 hardware to use valgrind. At
> > least
> > that's what I understood from #592614, but I wasn't the maintainer at the
> > time.
Obviously running valgrind on the armel buildd wouldn't have worked since thay
are not ARMv7. Building armel ARMv7-only valgrind on ARMv5 was *by design*, to
let people with armel ARMv7 systems use it.
In any case valgrind is no longer built on armel, and will be removed from
there soon.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;<inidehG ordnasselA>;eg;say~~reverse'
signature.asc
Description: Digital signature
