|
From: Stutz O. <Oli...@ca...> - 2010-10-04 09:58:35
|
Dear Valgrind Users, I would like to know if there are any AIX Binaries for version 5.3. I have tried to download the valgrind 3.5.0 package but the configure step isn't working while the script tries to execute cc --version (This argument is not taken by cc (IBM XL C compiler)). Thanks for the reply, Oliver Message: ## ----------- ## ## Core tests. ## ## ----------- ## configure:1395: checking for a BSD-compatible install configure:1450: result: ./install-sh -c configure:1461: checking whether build environment is sane configure:1504: result: yes configure:1569: checking for gawk configure:1598: result: no configure:1569: checking for mawk configure:1598: result: no configure:1569: checking for nawk configure:1585: found /usr/bin/nawk configure:1595: result: nawk configure:1605: checking whether make sets $(MAKE) configure:1625: result: yes configure:1794: checking whether to enable maintainer-specific portions of Makefiles configure:1803: result: no configure:1824: checking whether ln -s works configure:1828: result: yes configure:1881: checking for gcc configure:1910: result: no configure:1961: checking for cc configure:1977: found /usr/vac/bin/cc configure:1987: result: cc configure:2151: checking for C compiler version configure:2154: cc --version </dev/null >&5 cc: 1501-216 command option --version is not recognized - passed to ld Based on previous e-mail correspondence with you and/or an agreement reached with you, we consider ourselves authorized to contact you via unsecured e-mail. Warning: (a) E-mails can involve SUBSTANTIAL RISKS, e.g. lack of confidentiality, potential manipulation of contents and/or sender's address, incorrect recipient (misdirection), viruses etc. We assume no responsi-bility for any loss or damage resulting from the use of e-mails. We recommend in particular that you do NOT SEND ANY SENSITIVE INFORMATION, that you do not include details of the previous message in any reply, and that you enter e-mail address(es) manually every time you write an e-mail. (b) As a matter of principle, we do NOT accept any ORDERS, revocations of orders or authorizations, blocking of credit cards, etc., sent by e-mail Should such an e-mail nevertheless be received, we are not obliged to act on or respond to the e-mail. Please notify us immediately if you received this e-mail by mistake or if you do not wish to receive any further e-mail correspondence. If you have received this e-mail by mistake, please completely delete it (and any attachments) and do not forward it or inform any other person of its contents. |
|
From: Stutz O. <Oli...@ca...> - 2010-10-05 04:30:54
|
Thanks to everybody who has replied on my issue that AIX is not a supported Platform.
I have now taken an alternative way and used a different AIX machine with a GCC compiler, it actually creates all the Objects but with one it has a problem.
The variable important for the object file mode "OBJECT_MODE" it set to 32 while it can't find a gcc compiler for 64bit. (running ./configure won't work with the 64 setting).
I have met the same but with all the Objects if I don't set the Object Mode on compile but force it to be 64 bit via the configure parameters. Maybe somebody has met this issue while it seems to be a "pure" compiler issue rather than a showstopper.
Thanks for the help,
Oliver
Compile Log:
/usr/bin/ar cru libvex-ppc32-aix5.a libvex_ppc32_aix5_a-main_globals.o libvex_ppc32_aix5_a-main_main.o libvex_ppc32_aix5_a-main_util.o libvex_ppc32_aix5_a-ir_defs.o libvex_ppc32_aix5_a-ir_match.o libvex_ppc32_aix5_a-ir_opt.o libvex_ppc32_aix5_a-guest_generic_bb_to_IR.o libvex_ppc32_aix5_a-guest_generic_x87.o libvex_ppc32_aix5_a-guest_x86_helpers.o libvex_ppc32_aix5_a-guest_x86_toIR.o libvex_ppc32_aix5_a-guest_amd64_helpers.o libvex_ppc32_aix5_a-guest_amd64_toIR.o libvex_ppc32_aix5_a-guest_ppc_helpers.o libvex_ppc32_aix5_a-guest_ppc_toIR.o libvex_ppc32_aix5_a-guest_arm_helpers.o libvex_ppc32_aix5_a-guest_arm_toIR.o libvex_ppc32_aix5_a-host_generic_regs.o libvex_ppc32_aix5_a-host_generic_simd64.o libvex_ppc32_aix5_a-host_generic_reg_alloc2.o libvex_ppc32_aix5_a-host_x86_defs.o libvex_ppc32_aix5_a-host_x86_isel.o libvex_ppc32_aix5_a-host_amd64_defs.o libvex_ppc32_aix5_a-host_amd64_isel.o libvex_ppc32_aix5_a-host_ppc_defs.o libvex_ppc32_aix5_a-host_ppc_isel.o libvex_ppc32_aix5_a-host_arm_defs.o libvex_ppc32_aix5_a-host_arm_isel.o
ar: 0707-126 libvex_ppc32_aix5_a-main_globals.o is not valid with the current object file mode.
Use the -X option to specify the desired object mode.
gmake[3]: *** [libvex-ppc32-aix5.a] Error 1
gmake[3]: Leaving directory `/opt/valgrind-3.5.0/VEX'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/opt/valgrind-3.5.0/VEX'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/opt/valgrind-3.5.0'
gmake: *** [all] Error 2
Based on previous e-mail correspondence with you and/or an agreement reached with you, we consider ourselves authorized to contact you via unsecured e-mail.
Warning:
(a) E-mails can involve SUBSTANTIAL RISKS, e.g. lack of confidentiality, potential manipulation of contents and/or sender's address, incorrect recipient (misdirection), viruses etc. We assume no responsi-bility for any loss or damage resulting from the use of e-mails. We recommend in particular that you do NOT SEND ANY SENSITIVE INFORMATION, that you do not include details of the previous message in any reply, and that you enter e-mail address(es) manually every time you write an e-mail.
(b) As a matter of principle, we do NOT accept any ORDERS, revocations of orders or authorizations, blocking of credit cards, etc., sent by e-mail Should such an e-mail nevertheless be received, we are not obliged to act on or respond to the e-mail.
Please notify us immediately if you received this e-mail by mistake or if you do not wish to receive any further e-mail correspondence. If you have received this e-mail by mistake, please completely delete it (and any attachments) and do not forward it or inform any other person of its contents. |
|
From: Julian S. <js...@ac...> - 2010-10-06 09:45:16
|
3.5.0 will not compile on AIX. 3.4.1 _might_ work. You can get it from http://www.valgrind.org/downloads/valgrind-3.4.1.tar.bz2 If that doesn't work, can you build and debug your software on Linux instead? J On Tuesday, October 05, 2010, Stutz Oliver wrote: > Thanks to everybody who has replied on my issue that AIX is not a supported > Platform. > > I have now taken an alternative way and used a different AIX machine with a > GCC compiler, it actually creates all the Objects but with one it has a > problem. The variable important for the object file mode "OBJECT_MODE" it > set to 32 while it can't find a gcc compiler for 64bit. (running > ./configure won't work with the 64 setting). > > I have met the same but with all the Objects if I don't set the Object Mode > on compile but force it to be 64 bit via the configure parameters. Maybe > somebody has met this issue while it seems to be a "pure" compiler issue > rather than a showstopper. > > Thanks for the help, > > Oliver > > Compile Log: > /usr/bin/ar cru libvex-ppc32-aix5.a libvex_ppc32_aix5_a-main_globals.o > libvex_ppc32_aix5_a-main_main.o libvex_ppc32_aix5_a-main_util.o > libvex_ppc32_aix5_a-ir_defs.o libvex_ppc32_aix5_a-ir_match.o > libvex_ppc32_aix5_a-ir_opt.o libvex_ppc32_aix5_a-guest_generic_bb_to_IR.o > libvex_ppc32_aix5_a-guest_generic_x87.o > libvex_ppc32_aix5_a-guest_x86_helpers.o > libvex_ppc32_aix5_a-guest_x86_toIR.o > libvex_ppc32_aix5_a-guest_amd64_helpers.o > libvex_ppc32_aix5_a-guest_amd64_toIR.o > libvex_ppc32_aix5_a-guest_ppc_helpers.o > libvex_ppc32_aix5_a-guest_ppc_toIR.o > libvex_ppc32_aix5_a-guest_arm_helpers.o > libvex_ppc32_aix5_a-guest_arm_toIR.o > libvex_ppc32_aix5_a-host_generic_regs.o > libvex_ppc32_aix5_a-host_generic_simd64.o > libvex_ppc32_aix5_a-host_generic_reg_alloc2.o > libvex_ppc32_aix5_a-host_x86_defs.o libvex_ppc32_aix5_a-host_x86_isel.o > libvex_ppc32_aix5_a-host_amd64_defs.o > libvex_ppc32_aix5_a-host_amd64_isel.o libvex_ppc32_aix5_a-host_ppc_defs.o > libvex_ppc32_aix5_a-host_ppc_isel.o libvex_ppc32_aix5_a-host_arm_defs.o > libvex_ppc32_aix5_a-host_arm_isel.o ar: 0707-126 > libvex_ppc32_aix5_a-main_globals.o is not valid with the current object > file mode. Use the -X option to specify the desired object mode. > gmake[3]: *** [libvex-ppc32-aix5.a] Error 1 > gmake[3]: Leaving directory `/opt/valgrind-3.5.0/VEX' > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory `/opt/valgrind-3.5.0/VEX' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/opt/valgrind-3.5.0' > gmake: *** [all] Error 2 > > > Based on previous e-mail correspondence with you and/or an agreement > reached with you, we consider ourselves authorized to contact you via > unsecured e-mail. Warning: > (a) E-mails can involve SUBSTANTIAL RISKS, e.g. lack of confidentiality, > potential manipulation of contents and/or sender's address, incorrect > recipient (misdirection), viruses etc. We assume no responsi-bility for > any loss or damage resulting from the use of e-mails. We recommend in > particular that you do NOT SEND ANY SENSITIVE INFORMATION, that you do not > include details of the previous message in any reply, and that you enter > e-mail address(es) manually every time you write an e-mail. (b) As a > matter of principle, we do NOT accept any ORDERS, revocations of orders or > authorizations, blocking of credit cards, etc., sent by e-mail Should such > an e-mail nevertheless be received, we are not obliged to act on or > respond to the e-mail. Please notify us immediately if you received this > e-mail by mistake or if you do not wish to receive any further e-mail > correspondence. If you have received this e-mail by mistake, please > completely delete it (and any attachments) and do not forward it or inform > any other person of its contents. |