On Mon, Oct 28, 2013 at 11:02:18PM +0100, Alessandro Ghedini wrote:
> On Thu, Oct 24, 2013 at 08:24:28PM +0200, Alessandro Ghedini wrote:
> > Hi all,
> >
> > long story short, a couple years ago armel builds for valgrind were enabled
> > (despite the fact that valgr
On lun, ott 28, 2013 at 09:36:22 -0400, Jerry Stuckle wrote:
> On 10/28/2013 6:02 PM, Alessandro Ghedini wrote:
> >On Thu, Oct 24, 2013 at 08:24:28PM +0200, Alessandro Ghedini wrote:
> >>Hi all,
> >>
> >>long story short, a couple years ago armel builds for va
On Thu, Oct 24, 2013 at 08:24:28PM +0200, Alessandro Ghedini wrote:
> Hi all,
>
> long story short, a couple years ago armel builds for valgrind were enabled
> (despite the fact that valgrind only supports ARMv7) by building the package
> in
> cross-compile mode and forcing
On gio, ott 24, 2013 at 11:11:52 +0200, Hector Oron wrote:
> Hello,
>
> 2013/10/24 Alessandro Ghedini :
>
> > Hence the idea: what about dropping valgrind from armel? Or alternatively,
> > is
> > there anyone who cares about valgrind on armel and wants to debug and
Hi all,
long story short, a couple years ago armel builds for valgrind were enabled
(despite the fact that valgrind only supports ARMv7) by building the package in
cross-compile mode and forcing the -march=armv7-a option on buildds that didn't
support ARMv7 natively. This was done so that ARMv7 ar
On Thu, Oct 24, 2013 at 08:24:28PM +0200, Alessandro Ghedini wrote:
> Hi all,
>
> long story short, a couple years ago armel builds for valgrind were enabled
> (despite the fact that valgrind only supports ARMv7) by building the package
> in
> cross-compile mode and forcing
6 matches
Mail list logo
