On Monday 16 March 2009 02:56:46 Bill Hart wrote:
> Probably tickets 87 and 95 no longer apply too, but we should check I
> guess.

#95 is definitely dead , mpir configure runs yasm configure so all make target 
are there on all machines


>
> Bill.
>
> 2009/3/16 Bill Hart <goodwillh...@googlemail.com>:
> > That would be it. I'll close the ticket and update the website.
> >
> > Bill.
> >
> > 2009/3/16 Jason Moxham <ja...@njkfrudils.plus.com>:
> >> On Monday 16 March 2009 01:56:28 Bill Hart wrote:
> >>> Nope, you are using it right. It doesn't tell you more than we know.
> >>> Besides, you were the one who reported it.
> >>
> >> The closest one I could find is this from thread "trunk distclean
> >> broken" from 29/12/08 , this has been fixed for a while
> >>
> >> after doing
> >>  ./configure --build=none && make && make check
> >>
> >> make distclean fails with
> >>  rm -f *.lo
> >>  rm -f *.tab.c
> >>  test -z "" || rm -f
> >>  rm -f libtool
> >>  rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> >>  rm -f Makefile
> >>  make[1]: Leaving directory `/root/mpir/mpir/mpir/trunk/mpz'
> >>  Making distclean in mpn
> >>  make[1]: Entering directory `/root/mpir/mpir/mpir/trunk/mpn'
> >>  rm -rf .libs _libs
> >>  test -z "libmpn.la" || rm -f libmpn.la
> >>  rm -f "./so_locations"
> >>  rm -f *.o
> >>  test "" = "" || rm -f *_.c
> >>  rm -f *.lo
> >>  rm -f *.tab.c
> >>  test -z "" || rm -f
> >>  rm -f libtool
> >>  rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
> >>  rm -f Makefile
> >>  make[1]: Leaving directory `/root/mpir/mpir/mpir/trunk/mpn'
> >>  Making distclean in yasmbuild
> >>  make[1]: Entering directory `/root/mpir/mpir/mpir/trunk/yasmbuild'
> >>  cd ../yasm; make distclean
> >>  make[2]: Entering directory `/root/mpir/mpir/mpir/trunk/yasm'
> >>  make[2]: *** No rule to make target `distclean'.  Stop.
> >>  make[2]: Leaving directory `/root/mpir/mpir/mpir/trunk/yasm'
> >>  make[1]: *** [distclean] Error 2
> >>  make[1]: Leaving directory `/root/mpir/mpir/mpir/trunk/yasmbuild'
> >>  make: *** [distclean-recursive] Error 1
> >>
> >>> Bill.
> >>>
> >>> 2009/3/16 Jason Moxham <ja...@njkfrudils.plus.com>:
> >>> > Ticket 110
> >>> > A generic build (no assembly, i.e. host=none) fails on x86_64
> >>> > machines. This is a problem in configure.
> >>> >
> >>> > this is all it says , unless I'm using it wrong
> >>> >
> >>> > On Monday 16 March 2009 01:22:07 Bill Hart wrote:
> >>> >> Do you mean details of these issues? If so, there are trac tickets
> >>> >> for each of them. Below the red ones.
> >>> >>
> >>> >> Bill.
> >>> >>
> >>> >> 2009/3/16 Jason Moxham <ja...@njkfrudils.plus.com>:
> >>> >> > On Monday 16 March 2009 00:38:00 Bill Hart wrote:
> >>> >> >> Here is the link to release candidate 2 tarball:
> >>> >> >>
> >>> >> >> http://sage.math.washington.edu/home/wbhart/mpir-1.0.tar.gz
> >>> >> >>
> >>> >> >> and docs:
> >>> >> >>
> >>> >> >> http://sage.math.washington.edu/home/wbhart/mpir.pdf
> >>> >> >>
> >>> >> >> If no further bugs are found, this will become the final release.
> >>> >> >>
> >>> >> >> Known Issues:
> >>> >> >>
> >>> >> >> * MSYS and mingw32: --enable-fat build failure
> >>> >> >> * Cygwin32: make check fails if build path contained spaces
> >>> >> >> * X86 32 bit Apple gcc: no PIC support in assembly code
> >>> >> >> * Make tune will core dump with small probability on loaded
> >>> >> >> machines * Possible memory leak in t-locale
> >>> >> >> * Generic (without assembly support) build (--host=none) fails on
> >>> >> >> x86_64
> >>> >> >
> >>> >> > This works OK as far as I can tell , do we have more details
> >>> >> >
> >>> >> >> * Berkeley MP functions temporarily unsupported in this release
> >>> >> >> * Fat binary x86_64 build will fail with old GNU and Sun
> >>> >> >> assembler versions
> >>> >> >> * 30/36 Yasm tests will fail on some Sun x86 and x86_64 systems
> >>> >> >> (harmless)
> >>> >> >>
> >>> >> >> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to