OK, thanks. I'll add that program to the relevant makefile.am.
Bill.
On 27 September 2012 22:32, Brian Gladman wrote:
> -Original Message- From: Bill Hart
> Sent: Thursday, September 27, 2012 10:06 PM
> To: mpir-devel@googlegroups.com
> Cc: Brian Gladman
>
> Subject: Re: [mpir-devel] Re:
All the tests pass on MinGW32, including the fft tests. So this is good news.
Tomorrow I will try to sort out the tuning issues.
I also just noticed that make speed doesn't work. It seems to be due
to some problems in speed.h. I'll add it to the list of things to fix.
Bill.
On 27 September 2012
-Original Message-
From: Bill Hart
Sent: Thursday, September 27, 2012 10:06 PM
To: mpir-devel@googlegroups.com
Cc: Brian Gladman
Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
Hi Brian,
After discovering that the libtool in MinGW32 is different in version
number by 0.001 and th
On 27 September 2012 21:06, Brian Gladman wrote:
> -Original Message- From: Bill Hart
> Sent: Thursday, September 27, 2012 8:01 PM
> To: mpir-devel@googlegroups.com
>
> Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
>
> Hi Brian,
>
> the file name:
>
> mpir-2.5.1/build.vc10/mpir-t
-Original Message-
From: Bill Hart
Sent: Thursday, September 27, 2012 8:01 PM
To: mpir-devel@googlegroups.com
Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
Hi Brian,
the file name:
mpir-2.5.1/build.vc10/mpir-tests/f.fft_ifft_mfa_truncate_sqrt2/f.fft_ifft_mfa_truncate_sqrt2.vc
Hi Brian,
the file name:
mpir-2.5.1/build.vc10/mpir-tests/f.fft_ifft_mfa_truncate_sqrt2/f.fft_ifft_mfa_truncate_sqrt2.vcxproj
is still too long. The maximum length appears to be 99, so we are
still 1 character over the limit I think.
I think we should change all the truncates to trunc in the ff
-Original Message-
From: Bill Hart
Sent: Thursday, September 27, 2012 5:19 PM
To: Cactus
Cc: mpir-devel@googlegroups.com
Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
Yes, we should change the name of the file in the fft directory and
the test file in the tests/fft directory.
-Original Message-
From: Bill Hart
Sent: Thursday, September 27, 2012 5:19 PM
To: Cactus
Cc: mpir-devel@googlegroups.com
Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
Yes, we should change the name of the file in the fft directory and
the test file in the tests/fft directo
Herewith latest release todo list:
mpir-todo:
==
* fft_combine_bits const warning (see below)
* ../mpn/generic/gcdext.c:238: warning: integer overflow in expression
* _mp_release_macro volker braun reported
* tuning problems with fft cutoffs
* filename
mpir-2.5.1/build.vc10/mpir-tests/ff
Some good news.
If I hack together a tarball on my linux machine for mpir using make
dist then copy this to my MinGW32 machine, it builds no problem.
I still cannot figure out for the life of me what is different between
the two. According to svn, there is no difference!!
It seems we simply cann
-Original Message-
From: Bill Hart
Sent: Thursday, September 27, 2012 5:19 PM
To: Cactus
Cc: mpir-devel@googlegroups.com
Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
Yes, we should change the name of the file in the fft directory and
the test file in the tests/fft directo
Yes, we should change the name of the file in the fft directory and
the test file in the tests/fft directory.
We'll have to use something like:
fft_ifft_mfa_trunc_sqrt2.c, etc
I don't think we can abbreviate much more than that without changing a
whole load of other files to be consistent. I thi
On Thursday, 27 September 2012 16:43:55 UTC+1, Bill Hart wrote:
> More bad news.
>
> The filename
>
> mpir-2.5.1/build.vc10/mpir-tests/fft.fft_ifft_mfa_truncate_sqrt2/fft.fft_ifft_mfa_truncate_sqrt2.vcxproj
>
>
> is apparently too long, so we cannot create a tarball of MPIR.
>
> How do we w
More bad news.
The filename
mpir-2.5.1/build.vc10/mpir-tests/fft.fft_ifft_mfa_truncate_sqrt2/fft.fft_ifft_mfa_truncate_sqrt2.vcxproj
is apparently too long, so we cannot create a tarball of MPIR.
Bill.
On 27 September 2012 15:57, Bill Hart wrote:
> Obviously yasm files cannot be responsible f
Obviously yasm files cannot be responsible for configure not filling
config.h correctly.
And the autom4te.cache files are only to speed up autoreconf, not the
build system itself. (I tried committing these, but this didn't fix
the problem.)
Running autoreconf -i followed by svn commit now yields
Omigosh!!
There was a single \n in the middle of a comment in the config.in
generated on MinGW32 which prevented me from committing it to the
repo. After fixing this I was able to commit the differences to the
autotools files as generated by MinGW32's autoreconf 2.68 over the
Linux autoreconf 2.68
This did not work. The problem is I *cannot* commit the changes to svn
because of Windows line endings.
Changing the svn:eol-style to native for those files does not fix the
problem (this only affects the line style used when the file is
checked out). Making this change to svn properties and then
- Original Message -
From: "Pavel Holoborodko"
To:
Sent: Thursday, September 27, 2012 10:21 PM
Subject: Re: [mpir-devel] Re: MPIR 2.6 release progress
I've selected "Download latest repository catalogues" during the
installation instead of default "Use pre-packaged repository catal
Some possible good news.
The autoconf/autoreconf/automake versions I have on MinGW32 are
*identical* to the ones we have on our linux development machine.
This further confirms my suspicions that this is an extremely
irritating autotools bug. There should be no difference whatsoever in
the config
It's possible to delete posts if you wish. However, I personally see
no problem with this being on list.
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 t
- Original Message -
From: "Sisyphus"
Hi Pavel,
(This is an offlist post.)
Ummm ... perhaps not, though that was my intention ... ;-
Cheers,
Rob
--
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send ema
I've selected "Download latest repository catalogues" during the
installation instead of default "Use pre-packaged repository catalogues".
Plus I've also included MSYS, C++ and Fortran compilers in "Select
Components" window.
Hope this helps.
On Thu, Sep 27, 2012 at 9:11 PM, Sisyphus wrote:
>
- Original Message -
From: "Pavel Holoborodko"
My environment:
1. Windows 7 Ultimate x64.
2. Latest MinGW32 with gcc 4.7.0
(installed from official site:
http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/mingw-get-inst-20120426/mingw-get-inst-20120426.exe/download
)
23 matches
Mail list logo