Re: [mpir-devel] Link error when attempting to interface to Matlab MEX on Mac OS X

2010-04-10 Thread Willem Jan Palenstijn
On Sat, Apr 10, 2010 at 06:47:51AM -0700, Nicholas Kinar wrote: > Hello--- > > >> mex -I/usr/local/include T_Zeta.cpp mpreal.cpp /usr/local/lib/libgmp.a > >> /usr/local/lib/libmpfr.a Mex files are basically shared libraries, so I think you shouldn't be linking the non-PIC static versions of mpir

[mpir-devel] Re: MPIR 1.1.1 release candidate 1

2009-04-22 Thread Willem Jan Palenstijn
On Wed, Apr 22, 2009 at 01:38:13AM -0700, Cactus wrote: > On Apr 22, 9:15?am, Willem Jan Palenstijn wrote: > > svn checkouthttp://modular.math.jmu.edu/svn/mpir/mpir/trunkmpir-trunk > > cp -a mpir-trunk mpir-1.1 > > cd mpir-1.1 > > svn switchhttp://modular.math.jmu

[mpir-devel] Re: MPIR 1.1.1 release candidate 1

2009-04-22 Thread Willem Jan Palenstijn
On Wed, Apr 22, 2009 at 09:21:30AM +0100, Bill Hart wrote: > I wonder actually if we do use switch whether making changes to the > currently "switched" branch also automatically makes those changes to > trunk. I guess not, as that would probably be illogical. But then > again, I don't know how it

[mpir-devel] Re: MPIR 1.1.1 release candidate 1

2009-04-22 Thread Willem Jan Palenstijn
On Wed, Apr 22, 2009 at 08:54:42AM +0100, Jason Moxham wrote: > > Hi > > It's hard to believe that svn(or the others) dont have a solution for this. > How about something like this > > Brian wants branch-xyz , he logs into svn server , runs a diff of trunk > directory against branch to create

[mpir-devel] Re: svn

2009-03-19 Thread Willem Jan Palenstijn
On Thu, Mar 19, 2009 at 07:37:51PM +, Jason Moxham wrote: > > > Hi , I've just tried to merge a branch and I'm getting this > > > Rconfigfsf.sub > Uconfigure > Rmpn/x86_64/core2/sub_n.as > Ampn/x86_64/core2/penryn > Ampn/x86_64/core2/penryn/gmp-mparam.h > Dmpn/x86_6

[mpir-devel] Re: mpir-1.0 yasm problems

2009-03-18 Thread Willem Jan Palenstijn
On Wed, Mar 18, 2009 at 10:20:52AM -0400, Mariah Lenox wrote: > > mpir-1.0 is failing to configure on two archectures > that I have tried. Both failures seem to be related to > yasm. > > On a pentium4-pc-linux-gnu: > > config.status: linking ../mpir-1.0/yasm_mac.inc.nofat to yasm_mac.inc > ===

[mpir-devel] Re: build-time CPU detection fails on kvm/qemu amd64 virtual machine

2009-02-05 Thread Willem Jan Palenstijn
On Thu, Feb 05, 2009 at 08:20:04PM +, Bill Hart wrote: > > I don't understand why you don't get ABI=64 when you select > -host=x86_64-blah. It *should* give you ABI = 64. If not there is some > other problem here. ./configure --host=x86_64-unknown-linux-gnu does result in ABI=64. -Willem J

[mpir-devel] build-time CPU detection fails on kvm/qemu amd64 virtual machine

2009-02-05 Thread Willem Jan Palenstijn
Hi, When building the mpir shipped with sage 3.3.alpha5 (r1555) on a kvm/qemu amd64 virtual machine I get a 32-bit libgmp.so. The two config*.guess scripts report: [r...@localhost src]# bash config.guess athlon-unknown-linux-gnu [r...@localhost src]# bash configfsf.guess x86_64-unknown-linux-gnu