|
From: pavanks <sud...@gm...> - 2008-05-13 04:37:27
|
Hi Iam trying to cross compile for ppc-32 on my linux desktop.
My machine details are
Linux version 2.4.34 (Red Hat Linux 3.3.2-1)) #1 SMP Thu Jun 28 19:39:26 IST
2007
iam using
valgrind-3.3.0
i did
export CC=/opt/eldk/usr/bin/ppc_82xx-gcc
./configure gives warning
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
make gives the following errors, please help me.
/opt/eldk/usr/bin/ppc_82xx-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include
-I../VEX/pub -DVGA_ppc32=1 -DVGO_linux=1 -DVGP_ppc32_linux=1 -O2 -g
-Wmissing-prototypes -Wall -Wshadow -Wpointer-arith -Wstrict-prototypes
-Wmissing-declarations -fno-strict-aliasing -O -g -fpic
-fno-omit-frame-pointer -fno-strict-aliasing -O2 -Wno-long-long -c -o
vgpreload_memcheck_ppc32_linux_so-mc_replace_strmem.o `test -f
'mc_replace_strmem.c' || echo './'`mc_replace_strmem.c
mc_replace_strmem.c: In function `_vgwZU_libcZdsoZa_putenv':
mc_replace_strmem.c:743: unknown register name `xer' in `asm'
mc_replace_strmem.c:745: Internal compiler error:
mc_replace_strmem.c:745: GOT/TOC register marker not removed:
(parallel[
(set (reg:SI 29 r29)
(asm_operands/v ("mr 11,%1
lwz 3,4(11)
lwz 11,0(11)
rlwinm 0,0,3,0,0 ; rlwinm 0,0,13,0,0
rlwinm 0,0,29,0,0 ; rlwinm 0,0,19,0,0
or 3,3,3
mr %0,3") ("=r") 0[
(reg:SI 29 r29)
]
[
(asm_input:SI ("r"))
] ("mc_replace_strmem.c") 743))
(clobber (reg:QI 13 r13))
(clobber (reg:QI 12 r12))
(clobber (reg:QI 11 r11))
(clobber (reg:QI 10 r10))
(clobber (reg:QI 9 r9))
(clobber (reg:QI 8 r8))
(clobber (reg:QI 7 r7))
(clobber (reg:QI 6 r6))
(clobber (reg:QI 5 r5))
(clobber (reg:QI 4 r4))
(clobber (reg:QI 3 r3))
(clobber (reg:QI 2 r2))
(clobber (reg:QI 0 r0))
(clobber (reg:QI 75 cr7))
(clobber (reg:QI 74 cr6))
(clobber (reg:QI 73 cr5))
(clobber (reg:QI 72 cr4))
(clobber (reg:QI 71 cr3))
(clobber (reg:QI 70 cr2))
(clobber (reg:QI 69 cr1))
(clobber (reg:QI 68 cr0))
(clobber (reg:QI 66 ctr))
(clobber (reg:QI 65 lr))
(clobber (mem:BLK (scratch) 0))
(clobber (reg:QI 68 cr0))
] )
make[3]: *** [vgpreload_memcheck_ppc32_linux_so-mc_replace_strmem.o] Error 1
make[3]: Leaving directory
`/home/sudarshan/software/valgrind-3.3.0/memcheck'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
`/home/sudarshan/software/valgrind-3.3.0/memcheck'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/sudarshan/software/valgrind-3.3.0'
make: *** [all] Error 2
regards,
pavan
--
View this message in context: http://www.nabble.com/crosscompile-to-ppc-with-valgrind-3.3.0-tp17143876p17143876.html
Sent from the Valgrind - Users mailing list archive at Nabble.com.
|
|
From: Bart V. A. <bar...@gm...> - 2008-05-13 17:25:09
|
On Tue, May 13, 2008 at 6:37 AM, pavanks <sud...@gm...> wrote: > > Hi Iam trying to cross compile for ppc-32 on my linux desktop. Hello Pavan, As far as I know currently you can't cross-compile Valgrind -- you have to compile it natively. Bart. |
|
From: Peter K. <ja...@su...> - 2008-05-16 08:02:29
|
>>>>> "Bart" == Bart Van Assche <bar...@gm...> writes: Bart> On Tue, May 13, 2008 at 6:37 AM, pavanks <sud...@gm...> wrote: >> >> Hi Iam trying to cross compile for ppc-32 on my linux desktop. Bart> Hello Pavan, Bart> As far as I know currently you can't cross-compile Valgrind -- Bart> you have to compile it natively. We've had a valgrind package in buildroot for quite some time which works for me on PPC - It's still at 3.2.3 though. http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi/trunk/buildroot/package/valgrind/ -- Bye, Peter Korsgaard |
|
From: Bart V. A. <bar...@gm...> - 2008-05-16 08:53:29
|
On Fri, May 16, 2008 at 10:02 AM, Peter Korsgaard <ja...@su...> wrote: > > Bart Van Assche <bar...@gm...> writes: > > As far as I know currently you can't cross-compile Valgrind -- > > you have to compile it natively. > > We've had a valgrind package in buildroot for quite some time which > works for me on PPC - It's still at 3.2.3 though. > > http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi/trunk/buildroot/package/valgrind/ Hello Peter, Does the uclibc package only include Valgrind or does it include both Valgrind and VEX ? It is indeed possible to cross-compile Valgrind by specifying --enable-tls / --disable-tls to ./configure, but during compilation of VEX a program called genoffsets.c is compiled and run. This is why cross-compilation of VEX currently fails. Bart. |
|
From: Sudarshan S. <sud...@gm...> - 2008-05-16 12:55:10
|
Thank you so much Bart.It worked On 5/16/08, Peter Korsgaard <ja...@su...> wrote: > >>>>> "Bart" == Bart Van Assche <bar...@gm...> writes: > > > Bart> On Tue, May 13, 2008 at 6:37 AM, pavanks <sud...@gm...> wrote: > >> > >> Hi Iam trying to cross compile for ppc-32 on my linux desktop. > > > Bart> Hello Pavan, > > Bart> As far as I know currently you can't cross-compile Valgrind -- > Bart> you have to compile it natively. > > We've had a valgrind package in buildroot for quite some time which > works for me on PPC - It's still at 3.2.3 though. > > http://buildroot.uclibc.org/cgi-bin/viewcvs.cgi/trunk/buildroot/package/valgrind/ > > > -- > Bye, Peter Korsgaard > |
|
From: Bart V. A. <bar...@gm...> - 2008-05-16 13:03:44
|
On Fri, May 16, 2008 at 2:54 PM, Sudarshan Soma <sud...@gm...> wrote: > Thank you so much Bart.It worked Do you mean that you got cross-compilation working ? Can you please post the output of the following command: uname -a && file VEX/auxprogs/genoffsets && file coregrind/valgrind Thanks, Bart. |
|
From: Sudarshan S. <sud...@gm...> - 2008-05-19 03:28:57
|
Iam so sorry for the confusion, I meant it ran using valgrind-3.2.3 version not valgrind-3.3.0 thanks again for your help. Regards, Sudarshan On 5/16/08, Bart Van Assche <bar...@gm...> wrote: > On Fri, May 16, 2008 at 2:54 PM, Sudarshan Soma <sud...@gm...> wrote: > > Thank you so much Bart.It worked > > > Do you mean that you got cross-compilation working ? Can you please > post the output of the following command: > > uname -a && file VEX/auxprogs/genoffsets && file coregrind/valgrind > > Thanks, > > > Bart. > |
|
From: Bart V. A. <bar...@gm...> - 2008-05-19 14:46:50
|
On Mon, May 19, 2008 at 5:29 AM, Sudarshan Soma <sud...@gm...> wrote: > Iam so sorry for the confusion, I meant it ran using valgrind-3.2.3 > version not valgrind-3.3.0 No problem. By this time I have filed a bug report which contains a patch that makes cross-compilation of Valgrind 3.3.0 / 3.3.1 possible. I hope it will be possible to integrate this patch in Valgrind 3.4.0. See also: https://bugs.kde.org/show_bug.cgi?id=162295 Bart. |