This issue is not relevant for MPIR 1.0.0 as we don't build yasm that
way any more.
So assuming Sage release their 3.4.1 today we'll make the current
release candidate of MPIR the final release. I'm just sitting next to
the build manager for Sage, and he tells me by tomorrow morning he
should have some feedback for us by tomorrow morning. Using MPIR in a
big project like that is really a strong acid test. {fingers crossed}
Bill.
2009/3/29 mabshoff <michael.absh...@mathematik.uni-dortmund.de>:
>
>
>
> On Mar 29, 2:43 pm, Bill Hart <goodwillh...@googlemail.com> wrote:
>> I've put release candidate 4 up. This fixes the yasm configure error
>> when -pc is present in the hostname.
>>
>> 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
>> * 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 32/64 systems
>> (harmless)
>> * On some Darwin Tiger systems a linker bug will cause make check to
>> fail.
>> * Old versions of the GNU assembler on Cygwin32 will have a problem
>> with dive1.s (doesn't know how to handle relocations)
>
>
> There is one more issue: We hard code make into a couple places
> instead of using ${MAKE}. The following patch by Peter Jeremy should
> fix that.
>
> --- gmp-mpir-0.9/src/yasmbuild/Makefile~ 2009-02-10 13:13:55.000000000
> +1100
> +++ gmp-mpir-0.9/src/yasmbuild/Makefile 2009-03-01 18:51:50.778359197
> +1100
> @@ -18,12 +18,12 @@
> # 02110-1301, USA.
>
> default:
> - cd ../yasm; ./configure; make
> + cd ../yasm; ./configure; ${MAKE}
> all: default
> clean:
> - cd ../yasm; make clean
> + cd ../yasm; ${MAKE} clean
> distclean:
> - cd ../yasm; make distclean
> + cd ../yasm; ${MAKE} distclean
> check-recursive:
> check:
> install:
>
> This isn't a very high priority fix, but it would be nice to have in
> MPIR 1.0.
>
>> We are uncertain whether the final issue needs to be fixed before a
>> final release or not.
>>
>> Bill.
>
> Cheers,
>
> Michael
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
