Jason, Apologies for taking so long to respond, but I wanted to check with management before answering.
Skynet - the network containing the machines you list - is NOT setup for mail. For policy reasons, we do not plan to change this. So sorry - you will have to login to extract data. A suggestion. Using 'expect' you can automate login and extraction of data. Sorry for the negative response, Mariah Lenox Skynet system adminstrator On Mon, Jun 6, 2011 at 1:41 AM, Jason <ja...@njkfrudils.plus.com> wrote: > On Monday 06 June 2011 05:37:44 Jason wrote: >> On Sunday 05 June 2011 17:49:39 Jason wrote: >> > On Sunday 05 June 2011 09:42:35 Jason wrote: >> > > Hi >> > > >> > > MPIR-2.4.0-rc1 is released for testing here >> > > >> > > http://www.mpir.org/mpir-2.4.0-rc1.tar.bz2 >> > > >> > > The main changes are >> > > >> > > Bug Fixes: >> > > * The define __GMP_CC in mpir.h and gmp.h can miss out the the option >> > > >> > > -std=gnu99 >> > > >> > > * Old versions of GAS can fail to assemble the >> > > >> > > mpn/x86_64/core2/popcount.asm * Make install will fail to install the >> > > file gmpxx.h (only needed with the configure options --enable-cxx >> > > --enable-gmpcompat) when built out of the source tree. >> > > >> > > * Add an alias used by MPFR (snprintf -> _snprintf) >> > > * Correct incorrect parameter type for mpz_cdiv_q_2exp >> > > >> > > Speedups: >> > > * Sandybridge and Bobcat have been tuned >> > > * Updated to the latest compiler flags >> > > * Bulldozer cpu detection >> > > >> > > Features: >> > > * Upgrade internal components yasm and autotools >> > > * General cleanups of sourcebase >> > > * Initial support for intmax functions >> > > * Initial support for MSVC command line build >> > >> > And a MSBUILD system for VS2010 >> > >> > > * Much more extensive and automated testing system >> > > >> > > Changes: >> > > * Remove explicit support for arc s390 pa32 pa64 >> > > >> > > Have fun >> > > >> > > The MPIR Team >> > >> > My K8 is out of action for moment and so are my 32 bit linux partitions >> > >> > The rest of my linux systems all pass >> > >> > bobcat-unknown-linux-gnu gcc version 4.4.4(GCC) >> > nehalem-unknown-linux-gnu gcc version 4.4.4 (GCC) >> > atom-unknown-linux-gnu gcc version 4.4.4 (GCC) >> > sandybridge-unknown-linux-gnu gcc version 4.5.2 (GCC) >> > >> > and the above systems all pass the APP tests (mpfr mpfi mpc ecm flint >> > pari) >> > >> > From the GCC farm we get these passes >> > k8-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) (Debian >> > 4.1.2-25) gcc11 >> > >> > k8-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) (Debian >> > 4.1.2-25) gcc12 >> > >> > k8-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) (Debian >> > 4.1.2-25) gcc13 >> > >> > penryn-unknown-linux-gnu gcc version 3.4.6 (Debian 3.4.6-9) gcc version >> > 4.1.3 20080704 (prerelease) (Debian 4.1.2-25) gcc14 >> > >> > westmere-unknown-linux-gnu gcc version 4.3.5 (Debian 4.3.5-4) gcc version >> > 4.4.5 (Debian 4.4.5-8) gcc20.host.farm >> > >> > k102-pc-linux-gnu gcc version 4.1.3 20080704 (prerelease) (Debian >> > 4.1.2-29) gcc version 4.3.5 (Debian 4.3.5-4) gcc version 4.4.5 (Debian >> > 4.4.5-8) gcc45 >> > >> > atom-unknown-linux-gnu gcc version 4.4.5 (Debian 4.4.5-8) gcc47 >> > >> > atom-unknown-linux-gnu gcc version 4.4.5 (Debian 4.4.5-8) gcc46 >> > >> > itanium2-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) >> > (Debian 4.1.2-29) gcc version 4.2.4 (Debian 4.2.4-6) gcc version 4.3.5 >> > (Debian 4.3.5-4) gcc version 4.4.5 (Debian 4.4.5-8) Babe >> > >> > powerpc970-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) >> > (Debian 4.1.2-25) gcc version 4.2.4 (Debian 4.2.4-6) gcc40 >> > >> > ultrasparc2-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) >> > (Debian 4.1.2-25) gcc54 >> > >> > hppa2.0-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) (Debian >> > 4.1.2-25) gcc version 4.2.4 (Debian 4.2.4-6) dingo >> > >> > gcc70 has the known bad compiler that compiles the test get_ux wrong >> > >> > and I'm still waiting for a few more results and then I'll do the APP >> > test on the GCC farm >> > >> > I'll test cygwin tonight as its so slow and mingw* and the CL build for >> > VS2008 >> > >> > skynet and the washington machines are difficult to automate they are >> > missing a few programs , I'll just have to install them locally. >> > >> > Jason >> >> some more >> >> ultrasparct1-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) >> (Debian 4.1.2-25) gcc version 4.2.4 (Debian 4.2.4-6) deluxe >> >> ultrasparc2-unknown-linux-gnu gcc version 4.1.3 20080704 (prerelease) >> (Debian 4.1.2-25) gcc version 4.2.4 (Debian 4.2.4-6) grobluk >> >> ia64-unknown-linux-gnu gcc version 4.1.2 20080704 (Red Hat 4.1.2-44) cleo >> >> ia64-unknown-linux-gnu gcc version 4.1.2 20070115 (prerelease) (SUSE Linux) >> iras >> >> nehalem-unknown-linux-gnu gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) >> (GCC) taurus >> >> core2-unknown-linux-gnu gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) >> eno >> >> k8-unknown-linux-gnu gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) >> flavius >> >> pentium4-pc-linux-gnu gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC) >> cicero >> >> gcc42 a mips passes for gcc-4.1 4.2 but fail for 4.3 due to the configure >> choosing a different ABI for the C++ bit from the C bit , this is an old >> error and can be worked around >> >> for some reason my auto script doesn't run the tests on the rest of skynet >> , you can run the tests manual though >> > > On sextus2 and I assume the others that wont run the command > echo "hello" | mail -s "hello" ja...@njkfrudils.plus.com > just hangs , same for mailx , with lena it doesn't hang but you get a dead > letter in your home directory. Is it possible to fix this ? or should I be > passing some other options? > I know the rest of the script is fine as it's the same one I've been using for > years > > The machines affected are mark mark2 fulvia cato sextus2 and lena. > > Thanks > Jason > >> On cygwin a parallel make of yasm fails , this has happened before but the >> problem went away , but it's back now , before I just worked around it by >> tweeking the scripts >> >> Jason > -- 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.
