Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Fri, Apr 18, 2008 at 1:43 AM, David Cournapeau <[EMAIL PROTECTED]> wrote: > David Cournapeau wrote: > > So it *may* be unrelated to msvc runtime; maybe it just caused a problem > > which has always been there. I will try to see if valgrind says anything > > useful for sparsetools under linux.

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

David Cournapeau wrote: > So it *may* be unrelated to msvc runtime; maybe it just caused a problem > which has always been there. I will try to see if valgrind says anything > useful for sparsetools under linux. > Ok, I think it is unlikely to be caused by msvc runtime problems. Valgrind rep

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

> > > That was in case we publish binaries made with Visual Studio, as David > > asked about this matter. The debugging symbols are indeed different, > > but if it is possible to use Visual Studio, why shouldn't we ? > > > Well, because it is not available freely and is not open source. I am > real

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Robert Kern wrote: > > Quite possibly. Can you run the segfaulting code in a debugger so we > can try to isolate the actual cause? It is possible that we can patch > it up to work with msvcr71. I finally managed to do something, for reference: - I hacked distutils to put -g everywhere (using t

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Matthieu Brucher wrote: > > > 2008/4/18, Robert Kern <[EMAIL PROTECTED] > >: > > On Fri, Apr 18, 2008 at 12:57 AM, Matthieu Brucher > <[EMAIL PROTECTED] > > wrote: > > I can help with packaging at least numpy with Visual Studio 20

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Fri, Apr 18, 2008 at 1:15 AM, Matthieu Brucher <[EMAIL PROTECTED]> wrote: > > > 2008/4/18, Robert Kern <[EMAIL PROTECTED]>: > > On Fri, Apr 18, 2008 at 12:57 AM, Matthieu Brucher > > <[EMAIL PROTECTED]> wrote: > > > I can help with packaging at least numpy with Visual Studio 2003 (well, > I > >

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

2008/4/18, Robert Kern <[EMAIL PROTECTED]>: > > On Fri, Apr 18, 2008 at 12:57 AM, Matthieu Brucher > <[EMAIL PROTECTED]> wrote: > > I can help with packaging at least numpy with Visual Studio 2003 (well, > I > > have to check the EULA if I'm allowed to do that !). For scipy, it is a > > matter of F

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Fri, Apr 18, 2008 at 12:57 AM, Matthieu Brucher <[EMAIL PROTECTED]> wrote: > I can help with packaging at least numpy with Visual Studio 2003 (well, I > have to check the EULA if I'm allowed to do that !). For scipy, it is a > matter of Fortran compiler :| That probably won't work. I believe th

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

2008/4/18, David Cournapeau <[EMAIL PROTECTED]>: > > Robert Kern wrote: > > > > Well, if the official mingw team is committed to not supporting the > > features that we need, then yes, absolutely. This appears to be the > > case. > > > > > Well, this does not seem to work either with gcc 4.3* relea

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

David Cournapeau wrote: > > > Ok, I will have to take a look at how to do that, then, I don't really > have experience with debugger, much less on windows. Will get back one I > understand how this works. > Ok, this is great: when run in gdb, no crash. But when run in cmd.exe, it always cras

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Robert Kern wrote: > On Thu, Apr 17, 2008 at 11:49 PM, David Cournapeau > <[EMAIL PROTECTED]> wrote: > >> Robert Kern wrote: >> > >> > Well, if the official mingw team is committed to not supporting the >> > features that we need, then yes, absolutely. This appears to be the >> > case. >> >>

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Thu, Apr 17, 2008 at 11:49 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Robert Kern wrote: > > > > Well, if the official mingw team is committed to not supporting the > > features that we need, then yes, absolutely. This appears to be the > > case. > > Well, this does not seem to work

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Robert Kern wrote: > > Well, if the official mingw team is committed to not supporting the > features that we need, then yes, absolutely. This appears to be the > case. > Well, this does not seem to work either with gcc 4.3* releases. I got segfaults too. So should we use VS built instead for

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Thu, Apr 17, 2008 at 11:33 PM, Charles R Harris <[EMAIL PROTECTED]> wrote: > Question. How does numpy link against the python library when there is only > a static version present? However distutils tells it to. The information is contained in /usr/local/lib/python2.6/config/Makefile, mostly in

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Question. How does numpy link against the python library when there is only a static version present? I compiled/installed python2.6.2a and the only library it generated was /usr/local/lib/python2.6/config/libpython2.6.a. Furthermore, I didn't see the python library specifically linked by any of th

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Thu, Apr 17, 2008 at 10:56 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Robert Kern wrote: > > > > It seems that Giovanni is getting his gcc from here: > > > > http://www.tdragon.net/recentgcc/ > > > > which also appears to have gfortran binaries, too. > > Would that be acceptable

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Robert Kern wrote: > > It seems that Giovanni is getting his gcc from here: > > http://www.tdragon.net/recentgcc/ > > which also appears to have gfortran binaries, too. > > Would that be acceptable to use for numpy/scipy ? I mean, is it enough if we say to people: you need to install mingw f

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Thu, Apr 17, 2008 at 9:36 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > I also found an unofficial installer for gcc 4.*, which at least claim > to care about python: > > http://www.develer.com/oss/GccWinBinaries > > The problems with the new official (but beta) 4.* builds is the lack of

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

David Cournapeau wrote: > > Distutils uses some tests function to see wether a particular set of > float functions is available (FUNCTIONS_TO_CHECK dict in > numpy/core/setup.py), detects a particular set is not available on mingw > (say 'HAVE_INVERSE_HYPERBOLIC'), and define all of them. The pr

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Robert Kern wrote: > On Thu, Apr 17, 2008 at 9:36 PM, David Cournapeau > <[EMAIL PROTECTED]> wrote: > >> Robert Kern wrote: >> > >> > Ah, this problem again. The build of mingw that you are using were >> > written with msvcrt in mind. For the most part they are compatible >> > with msvcr71,

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Thu, Apr 17, 2008 at 9:36 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Robert Kern wrote: > > > > Ah, this problem again. The build of mingw that you are using were > > written with msvcrt in mind. For the most part they are compatible > > with msvcr71, but there are a few places where

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

Robert Kern wrote: > > Ah, this problem again. The build of mingw that you are using were > written with msvcrt in mind. For the most part they are compatible > with msvcr71, but there are a few places where they reference a table > that is different between the two runtimes, namely iostream in C++

Re: [Numpy-discussion] Distutils: using different linker options for c++ and c code

On Thu, Apr 17, 2008 at 6:34 AM, David Cournapeau <[EMAIL PROTECTED]> wrote: > Hi, > > I cannot seem to make scipy.sparse works on windows with mingw32, > and it seems related to the msvc runtime. I always get segfaults in the > sparsetools module (c++); if I build the module manually to cont

[Numpy-discussion] Distutils: using different linker options for c++ and c code

Hi, I cannot seem to make scipy.sparse works on windows with mingw32, and it seems related to the msvc runtime. I always get segfaults in the sparsetools module (c++); if I build the module manually to control the options precisely and remove the -lmsvc71 from the build command, I cannot r