Done
On Wednesday 08 April 2009 09:30:04 Bill Hart wrote:
> I think I prefer building the library instead of the symlink. That
> seems cleaner.
>
> I'll wait for you to change this. Michael didn't get time for the
> final test yet either, so we'll do all that tomorrow.
>
> Bill.
>
> 2009/4/7 Jas
I think I prefer building the library instead of the symlink. That
seems cleaner.
I'll wait for you to change this. Michael didn't get time for the
final test yet either, so we'll do all that tomorrow.
Bill.
2009/4/7 Jason Moxham :
>
> On Tuesday 07 April 2009 23:10:09 mabshoff wrote:
>> On Apr
On Tuesday 07 April 2009 23:10:09 mabshoff wrote:
> On Apr 7, 3:04 pm, Bill Hart wrote:
> > What do you guys think about changing the name back to --enable-
> > gmpcompat now that we actually build the library and not just provide
> > symlinks?
>
> +1 from me.
>
> The current behavior is also con
On Apr 7, 3:04 pm, Bill Hart wrote:
> What do you guys think about changing the name back to --enable-
> gmpcompat now that we actually build the library and not just provide
> symlinks?
+1 from me.
The current behavior is also consistent with the fact that gmp.h was
never a link to mpir.h.
What do you guys think about changing the name back to --enable-
gmpcompat now that we actually build the library and not just provide
symlinks?
I will need to update the documentation to reflect the fact that we
build the library now, as I think it still says that we use symlinks.
I'll do this l
On Apr 5, 7:46 pm, Jason Moxham wrote:
> On Monday 06 April 2009 03:15:46 mabshoff wrote:
Hi Jason,
> I don't understand why it works , surely we have
> libmpir.so.3.4.1 in linux
> libmpir.3.4.1.dylib in OSX
> so a
> libmpir.${shared_ext}.3.4.1
>
> shouldn't work ?
I have no idea *why* you
On Monday 06 April 2009 03:15:46 mabshoff wrote:
> On Apr 5, 7:11 pm, Jason Moxham wrote:
> > There doesn't seem to be an easy way to this.
> >
> > I can do another hack for OSX , but then we will need another hack for
> > cygwin, and for each system which names it libraries differently, and
> >
rev 1854 , should be there , I just building it on varro now
On Monday 06 April 2009 03:18:35 mabshoff wrote:
> On Apr 5, 7:15 pm, mabshoff
> dortmund.de> wrote:
> > On Apr 5, 7:11 pm, Jason Moxham wrote:
>
>
>
> > I've svn'ed into mpir-1.0.0 branch
>
> I am not seeing it in the 1.0.0 branch.
On Apr 5, 7:15 pm, mabshoff wrote:
> On Apr 5, 7:11 pm, Jason Moxham wrote:
> I've svn'ed into mpir-1.0.0 branch
I am not seeing it in the 1.0.0 branch. The top of "svn log" in 1.0.0
says:
r1837 | jasonmoxham | 2009-0
On Apr 5, 7:11 pm, Jason Moxham wrote:
> There doesn't seem to be an easy way to this.
>
> I can do another hack for OSX , but then we will need another hack for cygwin,
> and for each system which names it libraries differently, and looking at
> libtool there are quite a few.
>
> The libtool -
There doesn't seem to be an easy way to this.
I can do another hack for OSX , but then we will need another hack for cygwin,
and for each system which names it libraries differently, and looking at
libtool there are quite a few.
The libtool --mode=installoption doesn't have a option for r
On Apr 5, 2:46 pm, Jason Moxham wrote:
> Varro on Skynet is Darwin , so perhaps I can test it , if I can get past the
> make install needing root access . I remember reading somewhere that you can
> set the install path .
Use --prefix to do that.
The names on OSX in general need to be dylib,
Varro on Skynet is Darwin , so perhaps I can test it , if I can get past the
make install needing root access . I remember reading somewhere that you can
set the install path .
On Sunday 05 April 2009 22:26:25 Jason Moxham wrote:
> Hi ,
> I pretty much thought this would be the case.
> Can you
Hi ,
I pretty much thought this would be the case.
Can you send me a list of the files that need these links.It's trivial to put
the links in once I know the file names . The same for any other OS that does
not use *.so etc , perhaps Cygwin?
I've looked before but I cant find the part of the co
14 matches
Mail list logo
