On Wed, May 11, 2011 at 11:42:54AM +0200, Loïc Minier wrote:
> On Wed, May 11, 2011, Pierre Habouzit wrote:
> > Looks like the easiest road is:
> > - armv7*)
> > + arm*)
> > In the configure case "${host}" in. I'll upload a -3 with that patch and
> > we'll see how far it goes
>
> Yep, but u
On Wed, May 11, 2011, Pierre Habouzit wrote:
> Looks like the easiest road is:
> - armv7*)
> + arm*)
> In the configure case "${host}" in. I'll upload a -3 with that patch and
> we'll see how far it goes
Yep, but upstream specifically want to test for arm >= v7 as to fail
the build on <= 6
On Wed, May 11, 2011, Pierre Habouzit wrote:
> https://buildd.debian.org/status/fetch.php?pkg=valgrind&arch=armel&ver=1%3A3.6.1-2&stamp=1305095779
configure.in tests whether host_cpu matches armv7*; I think this is
incorrect to start with as it should be fine to configure valgrind with
"--host=
On Wed, May 11, 2011 at 09:38:44AM +0200, Pierre Habouzit wrote:
> On Wed, May 11, 2011 at 10:32:51AM +0300, Riku Voipio wrote:
> > On Wed, May 11, 2011 at 09:24:53AM +0200, Pierre Habouzit wrote:
> > > Sadly it doesn't work:
> > > https://buildd.debian.org/status/fetch.php?pkg=valgrind&arch=armel&
On Wed, May 11, 2011 at 10:32:51AM +0300, Riku Voipio wrote:
> On Wed, May 11, 2011 at 09:24:53AM +0200, Pierre Habouzit wrote:
> > Sadly it doesn't work:
> > https://buildd.debian.org/status/fetch.php?pkg=valgrind&arch=armel&ver=1%3A3.6.1-2&stamp=1305095779
>
> > I have an arm at home so I'll tr
On Wed, May 11, 2011 at 09:24:53AM +0200, Pierre Habouzit wrote:
> Sadly it doesn't work:
> https://buildd.debian.org/status/fetch.php?pkg=valgrind&arch=armel&ver=1%3A3.6.1-2&stamp=1305095779
> I have an arm at home so I'll try to see if I'm able to understand how
> to cheat it, but if you have a
On Tue, May 10, 2011 at 04:54:11PM +0200, Loïc Minier wrote:
> On Tue, May 10, 2011, Pierre Habouzit wrote:
> > What should be done for that, s/arm/armel/ and add -marmv7a to the
> > CFLAGS at configure time, that's it?
>
> Yup; ideally, you would test whether the toolchain config supports
> ARM
On Tue, May 10, 2011 at 06:02:59PM +0300, Riku Voipio wrote:
> On Tue, May 10, 2011 at 03:28:36PM +0200, Pierre Habouzit wrote:
> > I'm mostly clueless about which arm CPU versions Debian is supposed to
> > support, should I wrap valgrind in some shell script that checks if the
> > CPU is recent en
On Tue, May 10, 2011 at 03:28:36PM +0200, Pierre Habouzit wrote:
> I'm mostly clueless about which arm CPU versions Debian is supposed to
> support, should I wrap valgrind in some shell script that checks if the
> CPU is recent enough to run valgrind and fail gracefully if not? and if
> thats a goo
On Tue, May 10, 2011, Pierre Habouzit wrote:
> What should be done for that, s/arm/armel/ and add -marmv7a to the
> CFLAGS at configure time, that's it?
Yup; ideally, you would test whether the toolchain config supports
ARMv7, and if it doesn't you add -march=armv7-a to the CFLAGS. This
means
What should be done for that, s/arm/armel/ and add -marmv7a to the
CFLAGS at configure time, that's it?
I'm mostly clueless about which arm CPU versions Debian is supposed to
support, should I wrap valgrind in some shell script that checks if the
CPU is recent enough to run valgrind and fail grace
Hi,
Current svn snapshots of valgrind seem to work fine on arm(v7).
I'd follow The advice from Loïc and build valgrind with -marmv7a
for now.
Riku
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
12 matches
Mail list logo
