|
From: Julian S. <js...@ac...> - 2010-10-15 10:06:57
|
I just created the stable branch for the 3.6.x line. Please try it out on platforms and configurations that are important to you. Unless there are reports of serious breakage, I will release 3.6.0 final on Monday. To check out the branch, do svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_6_BRANCH branch36 or alternatively a test tarball of it is available at http://www.valgrind.org/downloads/valgrind-3.6.0-test2.tar.bz2 It should be buildable and usable on the following targets: {x86,amd64,ppc32,ppc64,arm}-linux, {x86,amd64}-darwin. J |
|
From: Maynard J. <may...@us...> - 2010-10-15 15:15:29
|
Julian Seward wrote: > > I just created the stable branch for the 3.6.x line. Please try it > out on platforms and configurations that are important to you. > Unless there are reports of serious breakage, I will release 3.6.0 > final on Monday. > > To check out the branch, do > > svn co svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_6_BRANCH branch36 > > or alternatively a test tarball of it is available at > > http://www.valgrind.org/downloads/valgrind-3.6.0-test2.tar.bz2 > > It should be buildable and usable on the following targets: > > {x86,amd64,ppc32,ppc64,arm}-linux, {x86,amd64}-darwin. I tested this branch on POWER6 SLES 10 SP2, SLES 11 SP1, and RHEL 6 beta. Test results all seem pretty reasonable, aside from some known issues and a few (apparently) distro-specific issues that I'll need to investigate -- probably not worth holding up a release for. There is the problem with the ppc64 VMX test failure (bug 250038) that I really would like to fix before the release. But I doubt I'll have a breakthrough on debugging this before Monday. -Maynard > > J > > ------------------------------------------------------------------------------ > Download new Adobe(R) Flash(R) Builder(TM) 4 > The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly > Flex(R) Builder(TM)) enable the development of rich applications that run > across multiple browsers and platforms. Download your free trials today! > http://p.sf.net/sfu/adobe-dev2dev > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |
|
From: Julian S. <js...@ac...> - 2010-10-15 23:28:18
|
I notice that the compile command doesn't have -marm in it, and
it should. What happens if you add -marm to AM_CCASFLAGS_ARM_LINUX
at Makefile.all.am:157, do make distclean, and rebuild?
J
On Friday, October 15, 2010, Vince Weaver wrote:
> On Fri, 15 Oct 2010, Julian Seward wrote:
> > It should be buildable and usable on the following targets:
> > {x86,amd64,ppc32,ppc64,arm}-linux, {x86,amd64}-darwin.
>
> compiling on an armv7l system I get the following compile failure:
>
> This is a Beagle Board running Debian Sid, gcc 4.4.5, binutils 2.20.1
>
> make[3]: Entering directory `/arm/vince/valgrind/coregrind'
> gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub -DVGA_arm=1
> -DVGO_linux=1 -DVGP_arm_linux=1 -I../coregrind
> -DVG_LIBDIR="\"/usr/local/lib/valgrind"\" -DVG_PLATFORM="\"arm-linux\""
> -I.. -I../include -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1
> -I../coregrind -DVG_LIBDIR="\"/usr/local/lib/valgrind"\"
> -DVG_PLATFORM="\"arm-linux\"" -g -Wno-long-long -MT
> libcoregrind_arm_linux_a-dispatch-arm-linux.o -MD -MP -MF
> .deps/libcoregrind_arm_linux_a-dispatch-arm-linux.Tpo -c -o
> libcoregrind_arm_linux_a-dispatch-arm-linux.o `test -f
> 'm_dispatch/dispatch-arm-linux.S' || echo
> './'`m_dispatch/dispatch-arm-linux.S m_dispatch/dispatch-arm-linux.S:
> Assembler messages:
> m_dispatch/dispatch-arm-linux.S:66: Error: internal_relocation (type:
> OFFSET_IMM) not fixed up m_dispatch/dispatch-arm-linux.S:90: Error:
> internal_relocation (type: OFFSET_IMM) not fixed up
> m_dispatch/dispatch-arm-linux.S:135: Error: internal_relocation (type:
> OFFSET_IMM) not fixed up m_dispatch/dispatch-arm-linux.S:184: Error:
> internal_relocation (type: OFFSET_IMM) not fixed up make[3]: ***
> [libcoregrind_arm_linux_a-dispatch-arm-linux.o] Error 1 make[3]: Leaving
> directory `/arm/vince/valgrind/coregrind'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/arm/vince/valgrind/coregrind'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/arm/vince/valgrind'
> make: *** [all] Error 2
|
|
From: Julian S. <js...@ac...> - 2010-10-18 18:12:47
|
Thanks for the confirmation. Committed as r11457.
J
On Monday, October 18, 2010, Vince Weaver wrote:
> On Sat, 16 Oct 2010, Julian Seward wrote:
> > I notice that the compile command doesn't have -marm in it, and
> > it should. What happens if you add -marm to AM_CCASFLAGS_ARM_LINUX
> > at Makefile.all.am:157, do make distclean, and rebuild?
>
> yes, adding -marm to AM_CCASFLAGS_ARM_LINUX fixes things, and
> Valgrind runs properly after the build finishes.
>
> (sorry for the delay in responding, a power outage at work meant I
> couldn't access the machine to test this until this morning).
>
>
> Vince
>
> > On Friday, October 15, 2010, Vince Weaver wrote:
> > > On Fri, 15 Oct 2010, Julian Seward wrote:
> > > > It should be buildable and usable on the following targets:
> > > > {x86,amd64,ppc32,ppc64,arm}-linux, {x86,amd64}-darwin.
> > >
> > > compiling on an armv7l system I get the following compile failure:
> > >
> > > This is a Beagle Board running Debian Sid, gcc 4.4.5, binutils 2.20.1
> > >
> > > make[3]: Entering directory `/arm/vince/valgrind/coregrind'
> > > gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include -I../VEX/pub
> > > -DVGA_arm=1 -DVGO_linux=1 -DVGP_arm_linux=1 -I../coregrind
> > > -DVG_LIBDIR="\"/usr/local/lib/valgrind"\" -DVG_PLATFORM="\"arm-linux\""
> > > -I.. -I../include -I../VEX/pub -DVGA_arm=1 -DVGO_linux=1
> > > -DVGP_arm_linux=1 -I../coregrind
> > > -DVG_LIBDIR="\"/usr/local/lib/valgrind"\"
> > > -DVG_PLATFORM="\"arm-linux\"" -g -Wno-long-long -MT
> > > libcoregrind_arm_linux_a-dispatch-arm-linux.o -MD -MP -MF
> > > .deps/libcoregrind_arm_linux_a-dispatch-arm-linux.Tpo -c -o
> > > libcoregrind_arm_linux_a-dispatch-arm-linux.o `test -f
> > > 'm_dispatch/dispatch-arm-linux.S' || echo
> > > './'`m_dispatch/dispatch-arm-linux.S m_dispatch/dispatch-arm-linux.S:
> > > Assembler messages:
> > > m_dispatch/dispatch-arm-linux.S:66: Error: internal_relocation (type:
> > > OFFSET_IMM) not fixed up m_dispatch/dispatch-arm-linux.S:90: Error:
> > > internal_relocation (type: OFFSET_IMM) not fixed up
> > > m_dispatch/dispatch-arm-linux.S:135: Error: internal_relocation (type:
> > > OFFSET_IMM) not fixed up m_dispatch/dispatch-arm-linux.S:184: Error:
> > > internal_relocation (type: OFFSET_IMM) not fixed up make[3]: ***
> > > [libcoregrind_arm_linux_a-dispatch-arm-linux.o] Error 1 make[3]:
> > > Leaving directory `/arm/vince/valgrind/coregrind'
> > > make[2]: *** [all] Error 2
> > > make[2]: Leaving directory `/arm/vince/valgrind/coregrind'
> > > make[1]: *** [all-recursive] Error 1
> > > make[1]: Leaving directory `/arm/vince/valgrind'
> > > make: *** [all] Error 2
|