iras,eno,cleo all done both gcc versions etc 
just waiting on varro


On Sunday 15 March 2009 20:48:59 Jason Moxham wrote:
> cuda1 is done gcc-4.2 and 3.4
> box1 is done gcc-4.2.4
>
>
>
>
> I using the script below , another one without fat for powerpc etc , and
> another one with export CC="gcc-???" for all the installed gcc's
>
> this tests in/out of the src tree fat,cxx,NOASM,asserts
>
> mkdir testdir && cd testdir && ../configure && $MAKE && $MAKE check &&
> $MAKE clean && $MAKE distclean && cd .. && rm -rf testdir && \
> mkdir testdir && cd testdir
> && ../configure --enable-cxx --enable-assert --enable-alloca=debug && $MAKE
> && $MAKE check && $MAKE clean && $MAKE distclean && cd .. && rm -rf testdir
> && \
> mkdir testdir && cd testdir
> && ../configure --enable-cxx --enable-assert --enable-alloca=debug
> --build=none && $MAKE && $MAKE check && $MAKE clean && $MAKE distclean &&
> cd .. && rm -rf testdir &&  \
> mkdir testdir && cd testdir
> && ../configure --enable-cxx --enable-assert --enable-alloca=debug
> --enable-fat && $MAKE && $MAKE check && $MAKE clean && $MAKE distclean &&
> cd .. && rm -rf testdir &&  \
> ./configure --enable-cxx --enable-assert --enable-alloca=debug && $MAKE &&
> $MAKE check && $MAKE clean && $MAKE distclean && \
> ./configure --enable-cxx --enable-assert --enable-alloca=debug --build=none
> && $MAKE && $MAKE check && $MAKE clean && $MAKE distclean && \
> ./configure --enable-cxx --enable-assert --enable-alloca=debug --enable-fat
> && $MAKE && $MAKE check && $MAKE clean && $MAKE distclean && \
> rm -f fat.h && cd mpn && rm -f fat_* amd64_* core2_* x86_64_* && cd .. && \
> ./configure && $MAKE && $MAKE check && cd tests/devel && $MAKE try &&
> cd ../../tune && $MAKE speed tuneup
>
> On Sunday 15 March 2009 20:33:24 Bill Hart wrote:
> > OK, it is working for me, so I'll do that one. Does this work for you:
> >
> > Jason:
> >
> > eno - 4.3.0 n f
> > varro A 4.0.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
> >
> > Bill:
> >
> > cato 4.1.2 n
> > mark 4.3.3 n / S
> > cicero 4.3.0 n f
> > fulvia 4.3.3 n f / S n f
> > menas 4.2.1 n f / 4.3.3 n f
> >
> > Bill.
> >
> > 2009/3/15 Jason Moxham <ja...@njkfrudils.plus.com>:
> > > I cant access cato either :(
> > >
> > > On Sunday 15 March 2009 19:59:54 Bill Hart wrote:
> > >> I've updated NEWS, Authors an ChangeLog in trunk. Let me know if I
> > >> missed anything. Is Jason the only new code contributor we need to
> > >> acknowledge?
> > >>
> > >> Is everyone happy that their licensing info is up-to-date?
> > >>
> > >> Bill.
> > >>
> > >> 2009/3/15 Bill Hart <goodwillh...@googlemail.com>:
> > >> > Sure. We'll put it in rc2.
> > >> >
> > >> > Bill.
> > >> >
> > >> > 2009/3/15 Cactus <rieman...@googlemail.com>:
> > >> >> On Mar 15, 7:09 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
> > >> >>> Is it my browser playing up, or do our posts seem to be be going
> > >> >>> all over the place in the threads. I start a thread called Release
> > >> >>> Candidate 1 and the discussion gets continued in the thread on
> > >> >>> Toom-4 !! Perhaps google mail doesn't sort properly by thread.
> > >> >>>
> > >> >>> Anyhow, here are the links to the tarball, in case I posted the
> > >> >>> wrong ones (I don't see them anywhere in this thread). This is the
> > >> >>> tarball and pdf doc for release candidate 1:
> > >> >>>
> > >> >>> http://sage.math.washington.edu/home/wbhart/mpir-1.0.tar.gz
> > >> >>>
> > >> >>> http://sage.math.washington.edu/home/wbhart/mpir.pdf
> > >> >>
> > >> >> I have found a configuration error in the MSVC build in the
> > >> >> tarball. I have not added the tests for the new functions into the
> > >> >> SVN trunk (I have them locally).
> > >> >>
> > >> >> Should I correct this in trunk?
> > >> >>
> > >> >>   Brian
>
> 


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to