Re: [mpir-devel] Building MPIR on Raspberry Pi (64-bit)

2022-03-17 Thread Dima Pasechnik
On Thu, Mar 17, 2022 at 8:40 PM 'Bill Hart' via mpir-devel wrote: > > I don't have any insight into the Raspberry Pi build environment. > However there are a lot of errors related to M4 there. Can you ensure > this is installed. > > On the other hand it looks like the autoconf version you have jus

Re: [mpir-devel] Compiling the MPIR

2022-02-08 Thread Dima Pasechnik
On Tue, 8 Feb 2022, 05:54 Gaj Satha, wrote: > Hi: > > I wanted to compile the latest version of MPIR, How do I do it? > > In version 3.0.0, I can do the following and it works: > *configure --prefix=/usr/local* > *make* > *make install* > > > But in the latest version, at https://github.com/wbhar

Re: [mpir-devel] Re: Flint-2.6.0 alpha release (testing requested)

2020-05-21 Thread Dima Pasechnik
On Wed, May 20, 2020 at 5:40 PM 'Bill Hart' via mpir-devel wrote: > > Hi again, > > Commit a960857c7d8e5ea7c4d4c2958e38ec52778d85d9 of the Flint > repository [1] is now flint-2.6.0-alpha2 > > This is the last chance for developers working on related projects to > see if Flint works as expected fo

Re: [mpir-devel] Does the most recent version of MPIR have the same API as the most recent version of GMP?

2019-10-07 Thread Dima Pasechnik
On Mon, Oct 7, 2019 at 3:52 AM zzzhhh wrote: > If the most recent version of MPIR is what I downloaded from github and > the most recent version of GMP is 6.1.2, do they have exactly the same > function API? Thanks. > > my understanding is that APIs are close enough to allow big projects such as

Re: [mpir-devel] MPIR.NET

2019-06-06 Thread Dima Pasechnik
On Thu, Jun 6, 2019 at 6:01 PM Cactus wrote: > I would like to contact Alex Dyachenco (the author of MPIR.NET) as it > needs maintenance in order to work with the current MPIR Windows build. > mpir.net domain name is for sale, it appears. > > I would be grateful If Alex (or anyone else who k

Re: [mpir-devel] Re: MPIR slow on macOS?

2019-03-05 Thread Dima Pasechnik
in such a setting? (GMP is easy to install e.g. via Homebrew, or building from source just like with MPIR) > > On Tuesday, January 15, 2019 at 11:40:46 AM UTC-8, Dima Pasechnik wrote: >> >> Perhaps we can put up this code on MPIR's Travis CI and see how it >> goes on OSX av

Re: [mpir-devel] Re: MPIR slow on macOS?

2019-01-15 Thread Dima Pasechnik
Perhaps we can put up this code on MPIR's Travis CI and see how it goes on OSX available there. Dima On Tue, Jan 15, 2019 at 7:30 PM 'Bill Hart' via mpir-devel wrote: > > One difference is in how jump tables are implemented. But I really don't see > how that would be related to this issue. > >

Re: [mpir-devel] Re: make errors on Cygwin64 terminal

2019-01-10 Thread Dima Pasechnik
On Thu, 10 Jan 2019 18:21 Chintan Joshi Hi Bill, > Thanks for the prompt response. Any recommendations on how do I check > where the unsupported characters are coming from? > Where have you installed your Cygwin64 in? What is the path? Does it by any chances has non-ascii characters in it, or spa

[mpir-devel] Re: Flint, Nemo and MPIR websites down

2016-06-06 Thread Dima Pasechnik
On Monday, June 6, 2016 at 1:21:24 PM UTC+1, Bill Hart wrote: > > Hi all, > > As of yesterday, the Flint, MPIR and Nemo websites are all currently down. > We are unsure of the cause at this stage, but major hardware failure is > among them (they are all hosted on the same remotely administered

Re: [mpir-devel] MPIR-2.7.1 released

2015-11-20 Thread Dima Pasechnik
On Thursday, 19 November 2015 17:37:12 UTC, Bill Hart wrote: > > You can understand my confusion then, as in MPIR 2.7.0 we had: > > LIBGMP_LT_CURRENT = 16 > LIBGMP_LT_REVISION = 0 > LIBGMP_LT_AGE = 6 > > and in MPIR-2.7.1 we have: > > LIBGMP_LT_CURRENT = 16 > LIBGMP_LT_REVISION = 1 > LIBGMP_LT_A

Re: [sage-devel] Re: [mpir-devel] MPIR-2.7.1 released

2015-11-19 Thread Dima Pasechnik
On Thursday, 19 November 2015 14:30:06 UTC, John Cremona wrote: > > On 19 November 2015 at 09:05, 'Bill Hart' via sage-devel > > wrote: > > Hmm, actually, I have > > > > LIBGMP_LT_CURRENT = 16 > > LIBGMP_LT_REVISION = 1 > > LIBGMP_LT_AGE = 6 > > > > I don't see where the 10 is coming from

Re: [mpir-devel] Re: MPIR-2.7.0 alpha12

2014-11-18 Thread Dima Pasechnik
Thanks! On Tuesday, 18 November 2014 14:58:28 UTC, Jeroen Demeyer wrote: > > See https://gcc.gnu.org/gcc-4.9/porting_to.html, section > Header changes > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop re

[mpir-devel] Re: MPIR-2.7.0 alpha12

2014-11-18 Thread Dima Pasechnik
I see a c++11 problem (same as with 2.6, in fact) using gcc-4.9.2. Namely, I get >mpir-2.7.0$ g++ -std=c++11 -I. -c b.cpp In file included from ./mpir.h:54:0, from ./mpirxx.h:44, from b.cpp:1: /home/scratch/dimpase/sage/sage6.3/local/include/c++/4.9.2/cstddef:5

[mpir-devel] Fwd: reporting Xcode 4 problems to Apple

2012-06-07 Thread Dima Pasechnik
On Thursday, 7 June 2012 12:31:30 UTC+2, Dima Pasechnik wrote: > > Dear all, > Are there bug reports filed regarding issues with Xcode 4? > Someone who works at Apple asked me for details of the troubles we > have with building Sage using Xcode 4, so I would like to supply as &

Re: [mpir-devel] Re: [sage-devel] Re: how do I build sage-5.0 on virtualbox?

2012-05-18 Thread Dima Pasechnik
On Friday, 18 May 2012 18:35:04 UTC+2, Bill Hart wrote: > > On 18 May 2012 17:26, Jeroen Demeyer wrote: > > On 2012-05-18 17:29, Bill Hart wrote: > >> I'm not sure how virtual boxes work. Do they emulate the CPU as well as > the OS? > >> > >> Unfortunately, there isn't really a lot we can d

[mpir-devel] Re: [sage-devel] Re: [sage-windows] Re: Cygwin attempt with sage-4.8.alpha3

2011-12-04 Thread Dima Pasechnik
On Sunday, December 4, 2011 5:12:21 PM UTC+8, jason wrote: > > On Sunday 04 December 2011 08:50:21 Volker Braun wrote: > > When I tracked down the yasm bug I made a trac ticket at > > http://trac.sagemath.org/sage_trac/ticket/11844 > > > > On Saturday, December 3, 2011 11:54:03 PM UTC, jason wro

[mpir-devel] fixed (?) movq -> movd ( Re: assembler errors on MacOSX 10.6 / (64 bit) XCode 4 (MPIR 2.3.1))

2011-04-15 Thread Dima Pasechnik
replacing each "movq" with "movd" in mpn/popcount.asm makes the errors go away, and all tests (make check) pass. So this looks like the right fix for this. Dmitrii On Apr 15, 1:59 am, Dima Pasechnik wrote: > is this known? > > >  gcc -std=gnu99 -c -DHAV

[mpir-devel] assembler errors on MacOSX 10.6 / (64 bit) XCode 4 (MPIR 2.3.1)

2011-04-14 Thread Dima Pasechnik
is this known? gcc -std=gnu99 -c -DHAVE_CONFIG_H -O2 -m64 -march=core2 -mtune=core2 - D__GMP_WITHIN_GMP -I.. -DOPERATION_popcount -I. -I.. tmp-popcount.s - fno-common -DPIC -o .libs/popcount.o tmp-popcount.s:54:suffix or operands invalid for `movq' tmp-popcount.s:57:suffix or operands invali