The yasm failures look like this: Test nasm_test: ./out_test.sh: test: argument expected FAIL: modules/parsers/nasm/tests/nasm_test.sh Test nasm_test: ./out_test.sh: test: argument expected FAIL: modules/parsers/nasm/tests/worphan/nasm_worphan_test.sh Test nasmpp_test: ./out_test.sh: test: argument expected FAIL: modules/preprocs/nasm/tests/nasmpp_test.sh Test dwarf2_pass32_test: ./out_test.sh: test: argument expected FAIL: modules/dbgfmts/dwarf2/tests/pass32/dwarf2_pass32_test.sh Test dwarf2_pass64_test: ./out_test.sh: test: argument expected FAIL: modules/dbgfmts/dwarf2/tests/pass64/dwarf2_pass64_test.sh Test dwarf2_passwin64_test: ./out_test.sh: test: argument expected FAIL: modules/dbgfmts/dwarf2/tests/passwin64/dwarf2_passwin64_test.sh Test stabs_test: ./out_test.sh: test: argument expected FAIL: modules/dbgfmts/stabs/tests/stabs_test.sh Test bin_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/bin/tests/bin_test.sh Test bin_multi_test: ./modules/objfmts/bin/tests/multisect/bin_multi_test.sh: test: argument expected FAIL: modules/objfmts/bin/tests/multisect/bin_multi_test.sh Test elf_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/elf/tests/elf_test.sh Test elf_amd64_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/elf/tests/amd64/elf_amd64_test.sh Test elf_gas32_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/elf/tests/gas32/elf_gas32_test.sh Test elf_gas64_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/elf/tests/gas64/elf_gas64_test.sh Test coff_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/coff/tests/coff_test.sh Test macho_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/macho/tests/gas32/gas_macho32_test.sh Test macho_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/macho/tests/gas64/gas_macho64_test.sh Test macho_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/macho/tests/nasm32/macho32_test.sh Test macho_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/macho/tests/nasm64/macho64_test.sh Test rdf_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/rdf/tests/rdf_test.sh Test win32_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/win32/tests/win32_test.sh Test win64_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/win64/tests/win64_test.sh Test win64_gas_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/win64/tests/gas/win64_gas_test.sh Test xdf_test: ./out_test.sh: test: argument expected FAIL: modules/objfmts/xdf/tests/xdf_test.sh Test bitvect_test: ... +3-0/3 100% PASS: bitvect_test Test floatnum_test: ........ +8-0/8 100% PASS: floatnum_test Test leb128_test: ................................ +32-0/32 100% PASS: leb128_test Test splitpath_test: ................................................ +48-0/48 100% PASS: splitpath_test Test combpath_test: ..................................... +37-0/37 100% PASS: combpath_test Test uncstring_test: .................... +20-0/20 100% PASS: uncstring_test Test libyasm_test: ./out_test.sh: test: argument expected FAIL: libyasm/tests/libyasm_test.sh
Looks like a script problem though, not a problem with the assembler as such. Bill. 2009/3/11 Bill Hart <goodwillh...@googlemail.com>: > The error is the same with Sun cc: > > cc -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. > -DOPERATION_fat_redc_basecase -m64 -xO4 -c fat_redc_basecase.c -o > fat_redc_basecase.o >/dev/null 2>&1 > /bin/bash ../libtool --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. > -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo fat_sqr_basecase | > sed 's/_$//'` -m64 -xO4 -c -o fat_sqr_basecase.lo > fat_sqr_basecase.c > cc -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. > -DOPERATION_fat_sqr_basecase -m64 -xO4 -c fat_sqr_basecase.c -KPIC > -DPIC -o .libs/fat_sqr_basecase.o > "../mpn/generic/sqr_basecase.c", line 273: undefined struct/union > member: SQR_KaRaTSUBa_THRESHOLD > cc: acomp failed for fat_sqr_basecase.c > *** Error code 1 > make: Fatal error: Command failed for target `fat_sqr_basecase.lo' > Current working directory /home/wbhart/mpir-fulvia/mpn > *** Error code 1 > > Bill. > > 2009/3/11 Bill Hart <goodwillh...@googlemail.com>: >> I managed to tease out what kind of machine it is, and it is >> definitely a Core2. No idea why it only has an amd directory for >> libraries. >> >> Anyhow, here is the failure with gcc -4.3.3 on fulvia: >> >> /bin/bash ../libtool --tag=CC --mode=compile gcc -std=gnu99 >> -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. -DOPERATION_`echo >> fat_sqr_basecase | sed 's/_$//'` -O2 -m64 -c -o fat_sqr_basecase.lo >> fat_sqr_basecase.c >> gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -D__GMP_WITHIN_GMP -I.. >> -DOPERATION_fat_sqr_basecase -O2 -m64 -c fat_sqr_basecase.c -fPIC >> -DPIC -o .libs/fat_sqr_basecase.o >> In file included from .././mpn/x86_64/fat/sqr_basecase.c:23, >> from fat_sqr_basecase.c:9: >> ../mpn/generic/sqr_basecase.c: In function '__gmpn_sqr_basecase_fat': >> ../mpn/generic/sqr_basecase.c:273: error: 'struct cpuvec_t' has no >> member named 'SQR_KaRaTSUBa_THRESHOLD' >> make[2]: *** [fat_sqr_basecase.lo] Error 1 >> make[2]: Leaving directory `/home/wbhart/mpir-fulvia/mpn' >> make[1]: *** [all-recursive] Error 1 >> >> Bill. >> >> >> 2009/3/11 Bill Hart <goodwillh...@googlemail.com>: >>> Config.guess identifies fulvia as a core2, yet the only gcc library >>> files that seem to be present for 64 bit are labelled amd64. That is >>> probably something to do with the failures. >>> >>> I'm unable to get cat /proc/cpuinfo being a Sun, but here is the >>> result of uname -a >>> >>> SunOS fulvia 5.10 Generic_127128-11 i86pc i386 i86pc >>> >>> Not very helpful sorry. >>> >>> Bill. >>> >>> 2009/3/11 Bill Hart <goodwillh...@googlemail.com>: >>>> I did make clean. I just tried it again and it definitely passes on varro. >>>> >>>> I don't think I'd be too worried about it. The issues on fulvia are >>>> certainly worth worrying about. I'll paste the failures here in a few >>>> hours (I'm tied up with something else right now). >>>> >>>> Bill. >>>> >>>> 2009/3/11 <ja...@njkfrudils.plus.com>: >>>>> >>>>> On Wednesday 11 March 2009 03:36:15 Bill Hart wrote: >>>>>> Here are the results of tests so far on SkyNet: >>>>>> >>>>>> eno - 4.3.0 n f / 4.3.3 n f >>>>>> cicero 4.3.0 n f >>>>>> cato 4.1.2 n >>>>>> varro A 4.0.1 n f / 4.3.3 n f >>>>>> fulvia 4.3.3 n * *** / S n ** *** ; >>>>>> menas 4.2.1 n f / 4.3.3 n f >>>>>> iras 4.1.2 n / 4.3.3 n >>>>>> cleo 4.1.2 n / 4.3.3 n >>>>>> rm mark 4.3.3 n / S >>>>>> >>>>>> * 30/36 yasm tests fail!! >>>>>> ** make check failed for yasm >>>>>> *** make failed for --enable-fat >>>>>> >>>>>> where: >>>>>> >>>>>> A = Apple CC >>>>>> S = Sun CC >>>>>> 4.x.y = gcc version >>>>>> n = normal build passed >>>>>> f = fat build passed >>>>>> >>>>>> I haven't been able to figure out a combination of PATH and >>>>>> $LD_LIBRARY_PATH to get the Sun CC and linker working on Mark. I've >>>>>> done it before by copying all the relevant binaries to directories in >>>>>> my home dir, but surely there is a way to get it to work. Anyone know? >>>>>> >>>>>> I don't think I had directories wrong for gcc 4.3.3 on Fulvia, so I >>>>>> think this is a real build failure. I may have gotten the Sun >>>>>> directories wrong however. But likely if it doesn't build with gcc it >>>>>> won't with Sun CC. >>>>>> >>>>>> I'm pretty surprised that fat binary worked on varro, as it is a PPC, >>>>>> not an x86. Perhaps fat binary just does nothing on unsupported archs. >>>>>> >>>>> >>>>> Looking at configure , fat build should fail on non x86 , it doesn't set >>>>> the >>>>> paths right. Did you make clean between builds ? >>>>> >>>>>> Bill. >>>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>> >> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
