I had the same problem the other day. It's a recent bug.

Does that directory with three mpir's actually exist on your machine?

I'm on IPhone only in county Durham ATM, so no proper Internet to check it out.

Bill.

On 28/12/2008, ja...@njkfrudils.plus.com <ja...@njkfrudils.plus.com> wrote:
>
> 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
>
> running ./configure && make distclean is not enough to fix it
> but ./configure && make && make distclean works
>
> this on K8-linux and athlon-linux
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to