Bug#701691: valgrind: support for ARMv5/v6
Hi Alessandro,
2013.11.13. 11:06, Alessandro Ghedini gh...@debian.org ezt írta:
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?
Sure. I meant this could be a very basic regression test which would run on
buildd machines now with dropping the special case armel arch and could
help people rebuilding Valgrind with changed dependencies.
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'
Bug#701691: valgrind: support for ARMv5/v6
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
Bug#701691: Re: Bug#701691: valgrind: support for ARMv5/v6
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... Thanks, Balint signature.asc Description: OpenPGP digital signature
Bug#701691: valgrind: support for ARMv5/v6
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.
Cheers
--
perl -E '$_=q;$/= @{[@_]};and s;\S+;inidehG ordnasselA;eg;say~~reverse'
signature.asc
Description: Digital signature
Bug#701691: valgrind: support for ARMv5/v6
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? may be override_dh_auto_test: : # do nothing for now should be tuned up to run at least few really quick tests to guarantee that valgrind works to at least some degree on a given platform, and if not -- fail that build thus avoiding users' frustration with useless package. Meanwhile removing all the builds for unsupported architectures. NB I have been enabling build-time testing for all of my packages and yes -- it does give more work to make package suitable for testing/stable BUT it provides a guarantee against many bugs being unraveled on users systems after. Cheers, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable'), (100, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages valgrind depends on: ii libc6 2.17-7 ii libc6-dbg 2.17-7 Versions of packages valgrind recommends: ii gdb 7.6-5 pn valgrind-dbg none Versions of packages valgrind suggests: pn alleyoop none pn kcachegrind none pn valgrind-mpi none pn valkyrie none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
