The iras failure is my test script fault

gcc-4.5.0 has a ICE when used at -O3 so in the mpir configure mechanism if we 
are on itanium then we choose -O2 , this works when we build with
nothing
--build=ia64-*
--build=none-unknown-linux-gnu

but NOT when
--build=long-unknown-linux-gnu
--build=longlong-unknown-linux-gnu

t2 also didn't like longlong builds , so I've changed these back to none 
builds , we still test long builds but only if we set ABI=32 in the script

Jason



On Thursday 27 May 2010 16:04:38 Minh Nguyen wrote:
> Hi folks,
>
> At this wiki page [1] is the build and test results on over 24
> machines of various hardware/platform combinations. Unfortunately, on
> about 8 of these machines, you find that MPIR r2978 builds fine, make
> check passes, make tune completes successfully, and the test suite
> pass. The other machines have some form of failure when running make
> check, make tune, or the test suite. But overall, MPIR r2978 builds OK
> on all the said machines so far with the usual mantra:
>
> $ ./configure && make
>
> On FreeBSD 8.0, running the test suite mpirtest resulted in
>
> [mv...@gcc101 test_stuff]$ ./mpirtest ../mpir-r2978
> bash: ./mpirtest: /bin/bash: bad interpreter: No such file or directory
>
> This is because the header of mpirtest is
>
> #!/bin/bash
>
> This is unportable and can break on systems such FreeBSD. A more
> portable header is to use the line
>
> #!/usr/bin/env bash
>
> And also to change the line
>
> SHE=/bin/bash
>
> to
>
> SHE=`which bash`
>
> If you agree, then I could make the change and commit it to the
> test_stuff branch of SVN.
>
> [1] http://wiki.sagemath.org/mpir/BuildFarm/mpir-2.1.0
>
> --
> 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 mpir-de...@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.

Reply via email to