No luck with getting autotools to work. I've already worked around one known bug in autotools and figured out how to suppress another error (no idea if it is a valid fix or not)!
But from there it doesn't actually get far when I try to do make dist. Bombs out after a few seconds claiming some directory it is trying to create already exists. All attempts to debug the makefiles which autotools spews out have failed on my part. I just don't know enough about how they work. So we don't have any choice but to wait until Jason can do this, as his autotools works and no other that I have access to does. Bill. 2009/12/12 Bill Hart <goodwillh...@googlemail.com>: > I've updated the details on the website and also the NEWS, ChangeLog > and AUTHORS files in svn for the release. > > 4 things remaining. > > I'm now going to look into the automake error I get on sage.math and > see if we can use it to do autotools stuff (for now). If I can get > that to work then I can put up RC4 on the website ready for testing. > > Bill. > > 2009/12/12 Bill Hart <goodwillh...@googlemail.com>: >> 1 is done. It already chooses a lowest common denominator when doing a >> fat binary. The issue with Sage which caused us to think that maybe we >> weren't doing this, seems to have been resolved - at least for MPIR >> anyhow. >> >> So that leaves only 5 things left to do. >> >> I am going to update the website now (at least the contributor section >> and list links to various papers of people whose code we have used). >> >> Bill. >> >> 2009/12/12 Bill Hart <goodwillh...@googlemail.com>: >>> In order for us to issue a new release, here is what is left: >>> >>> 1) Look into the issue with compiler options used in a fat build - I >>> will do that now. >>> >>> 2) Run autoheader, autoconf, automake, autowhatever - these run on >>> sage.math, but there is a single error when running automake, which >>> presumably doesn't happen on Jason's machine. >>> >>> 3) Update the website. >>> >>> 4) Begin another full round of build testing on linux and Windows. >>> >>> 5) Do a quick code review of all files added or modified since the last >>> release. >>> >>> 6) Release. >>> >>> 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-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.
