valgrind-users

[Valgrind-users] cross compiling valgrind

[Naveen K. <g_n...@ya...>]

Hi
  I am trying to cross compile valgrind on a host x86 pc for a target power
pc platform. I have all cross tools in place(gcc,ar, ld, etc)
and
they are named as ppc_XXX-gcc ppc_XXX-ld etc. Is there a way to specify
to ./configure to use these tools instead of the host default. ?
I tried giving --host=ppc_XXX and --host=powerpc-linux but neither worked. 

Thanks
Naveen



       
____________________________________________________________________________________Pinpoint customers who are looking for what you sell. 
http://searchmarketing.yahoo.com/

[Valgrind-users] cross compiling valgrind

[Jerry O. <jo...@on...>]

Having difficulty (valgrind newbie) configuring valgrind for a cross compile for my armv5/Linux embedded target. (Host/target and config information shown below) Doubt my configuration was correct but could find little documentation or examples online. Guessed at the required config options.

My host machine is running Ubuntu:
inux joram-Latitude-E6440 3.19.0-25-generic #26-Ubuntu SMP Fri Jul 24 21:17:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

My target machine is running an older linux distro on a 32 bit armv5 processor
Linux Evolution.example.com 2.6.18_pro500-davinci_IPNC_DM368_2.6.0 #1 PREEMPT Fri Apr 24 12:17:38 BST 2015 armv5tejl GNU/Linux

My configuration script looks like this:
sudo ./configure --prefix=/home/joram/valgrind/bin \                                                                                     --host=x86_64-ubuntu-linux --target=armv5-linux  \
CC=/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc \
AR=/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-ar

 (montavista toolchain)
Not sure I got that right although the configure script didn't complain, the end of it's output did
not look right:

        Maximum build arch: amd64
        Primary build arch: amd64
      Secondary build arch:
                  Build OS: linux
      Primary build target: AMD64_LINUX
    Secondary build target:
          Platform variant: vanilla
     Primary -DVGPV string: -DVGPV_amd64_linux_vanilla=1
        Default supp files: exp-sgcheck.supp xfree-3.supp xfree-4.supp glibc-2.X-drd.supp glibc-2.34567-NPTL-helgrind.supp glibc-2.5.sup
p

/*have no idea where the amd64 came from, my host machine is an  x86_64*/
 When I ran make it chugged through most of the build ok before it crapped out on:

make[3]: Entering directory '/home/joram/valgrind/valgrind-3.11.0/coregrind' with a ton of compiler errors:

/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I../include -I../VEX/pub -I../VEX/pub
-DVGA_amd64=1 -DVGO_linux=1 -DVGP_amd64_linux=1 -DVGPV_amd64_linux_vanilla=1 -I../coregrind -DVG_LIBDIR="\"/home/joram/valgrind/bin/lib/
valgrind"\" -DVG_PLATFORM="\"amd64-linux\""  -O2 -g -std=gnu99 -Wall -Wmissing-prototypes -Wshadow -Wpointer-arith -Wstrict-prototypes -W
missing-declarations -Wcast-align -Wcast-qual -Wwrite-strings -Wformat -Wformat-security -fno-stack-protector -fno-strict-aliasing -fno-b
uiltin  -fomit-frame-pointer   -MT libcoregrind_amd64_linux_a-m_addrinfo.o -MD -MP -MF .deps/libcoregrind_amd64_linux_a-m_addrinfo.Tpo -c
-o libcoregrind_amd64_linux_a-m_addrinfo.o `test -f 'm_addrinfo.c' || echo './'`m_addrinfo.c
In file included from ../include/pub_tool_vki.h:49,
                from pub_core_vki.h:44,
                from pub_core_threadstate.h:44,
                from m_addrinfo.c:44:
../include/vki/vki-linux.h: In function ‘__vki_cmsg_nxthdr’:
../include/vki/vki-linux.h:677: warning: cast increases required alignment of target type
In file included from ../include/pub_tool_vki.h:60,
                from pub_core_vki.h:44,
                from pub_core_threadstate.h:44,
                from m_addrinfo.c:44:
../include/vki/vki-xen.h:84:2: error: #error "Need to define per-ARCH Xen types for this platform"
In file included from ../include/pub_tool_vki.h:60,
                from pub_core_vki.h:44,
                from pub_core_threadstate.h:44,
                from m_addrinfo.c:44:
../include/vki/vki-xen.h: At top level:
../include/vki/vki-xen.h:87: error: ‘void’ must be the only parameter
../include/vki/vki-xen.h:87: warning: data definition has no type or storage class
../include/vki/vki-xen.h:87: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:88: warning: data definition has no type or storage class
../include/vki/vki-xen.h:88: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:88: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen.h:88: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:89: warning: data definition has no type or storage class
../include/vki/vki-xen.h:89: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:89: warning: parameter names (without types) in function declaration
../include/vki/vki-xen.h:89: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:91: error: expected ‘)’ before ‘unsigned’
../include/vki/vki-xen.h:91: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:93: error: expected ‘)’ before ‘vki_int16_t’
../include/vki/vki-xen.h:93: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:94: error: expected ‘)’ before ‘vki_int32_t’
../include/vki/vki-xen.h:94: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:95: error: expected ‘)’ before ‘vki_int64_t’
../include/vki/vki-xen.h:95: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:97: error: expected ‘)’ before ‘vki_uint8_t’
../include/vki/vki-xen.h:97: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:98: error: expected ‘)’ before ‘vki_uint16_t’
../include/vki/vki-xen.h:98: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:99: error: expected ‘)’ before ‘vki_uint32_t’
../include/vki/vki-xen.h:99: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:100: error: expected ‘)’ before ‘vki_uint64_t’
../include/vki/vki-xen.h:100: error: expected ‘)’ before ‘const’
../include/vki/vki-xen.h:103: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
In file included from ../include/vki/vki-xen.h:107,
                from ../include/pub_tool_vki.h:60,
                from pub_core_vki.h:44,
                from pub_core_threadstate.h:44,
                from m_addrinfo.c:44:
../include/vki/vki-xen-domctl.h:135: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:148: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:148: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:148: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:148: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:154: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:167: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:167: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:167: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:167: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:173: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:187: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:187: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:187: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:187: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:198: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:198: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:198: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:198: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:201: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:248: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-domctl.h:255: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:260: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-domctl.h:270: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:286: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:317: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:329: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:349: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:352: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:352: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:352: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:352: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:356: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-domctl.h:359: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:359: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:359: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:359: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:364: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-domctl.h:367: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:367: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:367: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:367: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:370: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-domctl.h:375: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:419: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:454: error: expected specifier-qualifier-list before ‘vki_xen_pfn_t’
../include/vki/vki-xen-domctl.h:460: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-domctl.h:463: warning: data definition has no type or storage class
../include/vki/vki-xen-domctl.h:463: warning: type defaults to ‘int’ in declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen-domctl.h:463: error: conflicting types for ‘___DEFINE_VKI_XEN_GUEST_HANDLE’
../include/vki/vki-xen.h:87: error: previous declaration of ‘___DEFINE_VKI_XEN_GUEST_HANDLE’ was here
../include/vki/vki-xen-domctl.h:463: error: expected ‘)’ before ‘const’
../include/vki/vki-xen-domctl.h:468: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
In file included from ../include/vki/vki-xen.h:108,
                from ../include/pub_tool_vki.h:60,
                from pub_core_vki.h:44,
                from pub_core_threadstate.h:44,
                from m_addrinfo.c:44:
../include/vki/vki-xen-sysctl.h:54: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:67: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:76: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:85: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:112: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:118: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:125: error: expected specifier-qualifier-list before ‘VKI_XEN_GUEST_HANDLE_64’
../include/vki/vki-xen-sysctl.h:137: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
../include/vki/vki-xen-sysctl.h:153: error: expected specifier-qualifier-list before ‘vki_xen_uint64_aligned_t’
In file included from ../include/vki/vki-xen.h:109,
                from ../include/pub_tool_vki.h:60,
(truncated)





This communication is for the exclusive use of the addressee and may contain information that is private and confidential. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication and its attachments is strictly prohibited. If you have received this information in error please contact the sender and delete the communication from your system. Any views or opinions presented are solely those of the author and do not necessarily represent those of Oncam Grandeye unless specifically stated.


This message has been scanned for malware by Websense. www.websense.com

Re: [Valgrind-users] cross compiling valgrind

[John R. <jr...@bi...>]

> My target machine is running an older linux distro on a 32 bit armv5 processor
> Linux Evolution.example.com 2.6.18_pro500-davinci_IPNC_DM368_2.6.0 #1 PREEMPT Fri Apr 24 12:17:38 BST 2015 armv5tejl GNU/Linux

armv5* is not officially supported as a target.  The hardware is deficient
because it does not provide reasonable support for threads.
There are unsupported patches (see the bug tracker) which enable support
for single-threaded ONLY, and memcheck ONLY; but you yourself
must support them (including adapt as needed from 2 or 3 years ago.)
armv7 is the minimal supported hardware.

Perhaps someone else can explain the failed attempt at configuration
(all the complaints from gcc, etc.)

Re: [Valgrind-users] cross compiling valgrind

[Bryan S. <bsc...@sa...>]

Naveen Kumar <g_naveen_k <at> yahoo.com> writes:


> 
> Hi
>   I am trying to cross compile valgrind on a host x86 pc for a target power
> pc platform. I have all cross tools in place(gcc,ar, ld, etc)
> and
> they are named as ppc_XXX-gcc ppc_XXX-ld etc. Is there a way to specify
> to ./configure to use these tools instead of the host default. ?
> I tried giving --host=ppc_XXX and --host=powerpc-linux but neither worked. 
> 


Hello,  I had problem similar except I am crosscompiling from an x86 windows
box, but resolving that is another story.  Here is how I got it to use another
set of tools

./configure  --prefix=/valgrind
CC=/opt/montavista/pro_adk/devkit/x86/pentium4/bin/pentium4-gcc --target=i486
--host=i686-intel-linux --disable-tls

Replace the path listed in CC with your path and it seems to figure out
everything else OK.

Good luck