Sebastian Haase wrote: > On 1/26/07, Robert Kern <[EMAIL PROTECTED]> wrote: >> Sebastian Haase wrote: >> >>> The easiest would be to be able to disable the long double functions. >> Actually, there are a number of other configuration items that are >> discovered by >> compiling small C programs and running them. There are a number of them that >> might give different answers on 10.3.9 if they could be compiled there. You >> would have to replace that configuration system with something that could >> load >> the configuration from a file or some other source. >> >> Since that's a big project, you might be content with modifying the code to >> hard-code the results for your own builds and documenting the differences >> from >> the result of a build from official sources. > > I have to admit that I don't know what "configuration items" are -
It's a general term, not a specific technical one. Look in the function generate_config_h() in numpy/core/setup.py (it's inside the function configuration()). All of the calls to config_cmd.try_run() and config_cmd.check_func() are constructing small C programs, building them, and trying to run them to see if they work. There may be others scattered around, but I don't think so. > but I can report that the simple approach of copying libmx.A.dyso > from a 10.4 system to a directory which I added to DYLD_LIBRARY_PATH > seems to work > on the 10.3.9 PPC machine for the first tests I ran so far. AFAIK, you can't redistribute that file legally. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco _______________________________________________ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion
