This still doesn't make any sense to me. Green should mean:
./configure make make check all pass *assuming the system is sane*. The failure on fulvia was because the system was not sane. The same with the failures on machines with gcc 4.3.2. Maybe we aren't being clear here: * failure on fulvia - this is due to LD_LIBRARY_PATH being set incorrectly *on the system*, not in MPIR. Problem is not with MPIR. Fix the system and MPIR will pass. The error says that the system lib_gcc has the wrong elfclass. Note lib_gcc is not part of MPIR!! * failure on gcc 4.3.2 systems - this is due to a bug in gcc 4.3.2. It will fail on *any* 64 bit system with gcc 4.3.2. It has nothing to do with the architecture or operating system and it has nothing to do with MPIR. Fix the compiler and MPIR will pass. Again, gcc is not part of MPIR. If we can't find a system which is sane for a given arch/OS combination, then we simply leave it white (unavailable). There's no sense in reporting either pass (green) or red (failure) on a broken system. We had this problem with t2 for ages. It was misconfigured and every version of GMP or MPIR, past or present failed on that system because it was misconfigured. When the system was configured correctly, every MPIR passed without any modifications being made to MPIR. Bill. On 9 June 2010 03:25, Minh Nguyen <[email protected]> wrote: > Hi Bill, > > On Wed, Jun 9, 2010 at 10:29 AM, Bill Hart <[email protected]> > wrote: > > <SNIP> > >> It's better to talk about specific examples. Which ones do you think >> we should give a red and why? Remember this matrix is supposed to >> indicate which kinds of arch/OS combinations a user should expect MPIR >> to work out of the box on (assuming their compiler works and their >> machine is set up correctly). > > In light of this, here is how I would color each cell in the test matrix. > > * FreeBSD, k8: build: yes; check: pass; tune: yes; test suite failed > with FAIL. Therefore, green. > > * Linux, Itanium (iras): build: yes; check: pass; tune: yes; test > suite failed with FAIL. Therefore, green. > > * Linux, ultrasparc2 (gcc54): build: yes; check: pass; tune: yes; test > suite failed with FAIL. Therefore, green. > > * Solaris, core2 (fulvia): build: yes. Therefore, green. > > You have to excuse my misunderstanding here, but let me try to define > how colouring for cells in the test matrix works: > > * white -- system unavailable for testing. > > * green -- at least these commands run successfully: ./configure && make > > * orange -- some issue with this command: make tune > > * red -- ./configure fails; or if it succeeds and make fails. > > I have edited the test matrix according to the above rules for colour coding. > > -- > Regards > Minh Van Nguyen > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
