No problem at all. Whatever works best for you. It all seems to have
worked fine, which is great!
Good riddance to svn. :-)
Bill
On 25 November 2012 22:20, Brian Gladman wrote:
> On 25/11/2012 23:07, Bill Hart wrote:
>> Hi Brian,
>>
>> great! I've merged this to my repo.
>>
>> By the way, an ad
MPIR has switched to using Git. We are using Git very much like
SVN with most development happening in the master branch.
The repository is found here:
https://github.com/wbhart/mpir
Below is a (hopefully corrected) list of instructions if you wish to
contribute as a developer on *nix or Windows
If it complains, try
git pull bill master
My instructions contained quite a few errors it seems. Sorry about that.
Bill.
On 25 November 2012 23:07, Bill Hart wrote:
> Hi Brian,
>
> great! I've merged this to my repo.
>
> By the way, an additional correction to my instructions:
>
> git remote a
Hi Brian,
great! I've merged this to my repo.
By the way, an additional correction to my instructions:
git remote add https://github.com/wbhart/mpir bill
should be
git remote add bill https://github.com/wbhart/mpir
apparently.
Once you have done this, you should be able to get up-to-date wit
On Sunday, 25 November 2012 21:25:14 UTC, Bill Hart wrote:
>
> Hi all,
>
> I have just finished creating a Git repository for MPIR on GitHub:
>
> https://github.com/wbhart/mpir
>
> We will be using Git very much like SVN, to simplify things for SVN
> users until they get used to the more adva
One additional note:
for GitHub for Windows, you push to the public repo by clicking
"Sync". All commits to your local repo are then pushed out to the
public repo.
Bill.
On 25 November 2012 22:21, Bill Hart wrote:
> There's a correction to the above for Windows. I reproduce the steps
> below wi
There's a correction to the above for Windows. I reproduce the steps
below with the correction for convenience:
* Create your own personal GitHub account (free) on http://github.com/
if you do not have one. (Click the "Sign Up For Free" button at the
upper right, and follow the instructions.)
* F
Hi all,
I have just finished creating a Git repository for MPIR on GitHub:
https://github.com/wbhart/mpir
We will be using Git very much like SVN, to simplify things for SVN
users until they get used to the more advanced features of Git, with
my GitHub page acting as the main development reposit
Hi all,
I collected numerous tickets which were pushed back to the next MPIR
release. In case anyone wants to work on them, here they are:
* have mpir.h define MPIR_H_HAVE_STDINT if _STDINT_H, etc are defined,
then use this flag in mpirxx.h which always includes mpir.h
* generic build option for
Something like this might work. Unfortunately there are widespread
issues with standard C++ header files interacting poorly, and the
obvious thing simply didn't work when we were preparing the release. I
don't recall the specifics.
However, I've added this issue to the todo list for the next relea
Sure. One thing we do need to do is document more clearly the intended
include order and some of these subtleties. We hit these ourselves
when preparing the release.
We thought it would make sense for the test files to be written like
user files without dependence on config.h. Unfortunately, our p
On Sunday, November 25, 2012 6:22:30 PM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Sunday, November 25, 2012 6:15:49 PM UTC+1, Bill Hart wrote:
>>
>> On 25 November 2012 16:22, Jean-Pierre Flori wrote:
>> >
>>
>> > If I understand correctly you'd rather propose to only check for
>> stdint.h a
On Sunday, November 25, 2012 6:15:49 PM UTC+1, Bill Hart wrote:
>
> On 25 November 2012 16:22, Jean-Pierre Flori >
> wrote:
> >
>
> > If I understand correctly you'd rather propose to only check for
> stdint.h at
> > build time, define a macro in mpir.h and then use it?
> > Unless you reall
On 25 November 2012 16:22, Jean-Pierre Flori wrote:
>
> If I understand correctly you'd rather propose to only check for stdint.h at
> build time, define a macro in mpir.h and then use it?
> Unless you really want to run with or without stdint.h on similar hardware
> (but I don't think you distri
The check for stdint.h at build time is not available when using
mpirxx.h from another project. Autotools puts the flag in config.h,
which is not generally available to mpirxx.h.
Bill.
On 25 November 2012 16:22, Jean-Pierre Flori wrote:
>
>
> On Sunday, November 25, 2012 5:02:59 PM UTC+1, Marc w
On Sunday, November 25, 2012 5:02:59 PM UTC+1, Marc wrote:
>
> On Sunday, November 25, 2012 3:35:05 PM UTC+1, Jean-Pierre Flori wrote:
>>
>>
>> On Sunday, November 25, 2012 2:07:24 AM UTC+1, Jean-Pierre Flori wrote:
>>>
>>> Dear all,
>>>
>>> While trying to upgrade MPIR in Sage, we got problems b
On Sunday, November 25, 2012 3:35:05 PM UTC+1, Jean-Pierre Flori wrote:
>
>
> On Sunday, November 25, 2012 2:07:24 AM UTC+1, Jean-Pierre Flori wrote:
>>
>> Dear all,
>>
>> While trying to upgrade MPIR in Sage, we got problems building Linbox on
>> top of MPIR > 2.5.x, including MPIR 2.6.0.
>> You
Good to know. Thanks!
Bill.
On Sunday, 25 November 2012, Jean-Pierre Flori wrote:
>
> On Sunday, November 25, 2012 2:07:24 AM UTC+1, Jean-Pierre Flori wrote:
>>
>> Dear all,
>>
>> While trying to upgrade MPIR in Sage, we got problems building Linbox on
>> top of MPIR > 2.5.x, including MPIR 2.6.
On Sunday, November 25, 2012 2:07:24 AM UTC+1, Jean-Pierre Flori wrote:
>
> Dear all,
>
> While trying to upgrade MPIR in Sage, we got problems building Linbox on
> top of MPIR > 2.5.x, including MPIR 2.6.0.
> You can see the discussion at
> http://trac.sagemath.org/sage_trac/ticket/13137
>
> The
19 matches
Mail list logo
