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 an
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
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 th
>> Of course .. that really shouldn't matter if you're just compiling it
>> for yourself for just that cpu.
>>
> On the contrary !
> I'm trying to provide a precompiled build of numpy together with a
> couple a handy
> functions and classes that I made myself,
> to establish Python as a development
On 1/25/07, Steve Lianoglou <[EMAIL PROTECTED]> wrote:
> >> Generally speaking, you need to build binaries on the lowest-
> >> versioned OS X that
> >> you intend to run on.
> >>
> > The problem with building on 10.3 is that it generally comes only with
> > gcc 3.3. I remember that some things re
Sebastian Haase wrote:
> The problem with building on 10.3 is that it generally comes only with
> gcc 3.3. I remember that some things require gcc4 - right ?
No, you're right. I thought this might have been available with 10.3.9 (the only
version in the 10.3 series that can run Universal binarie
>> Generally speaking, you need to build binaries on the lowest-
>> versioned OS X that
>> you intend to run on.
>>
> The problem with building on 10.3 is that it generally comes only with
> gcc 3.3. I remember that some things require gcc4 - right ?
I think that might only bite you if you want
On 1/25/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Sebastian Haase wrote:
> > Hi!
> > When I try running my code on
> > panther (10.3) with a numpy that was built on tiger (10.4)
> > it can't load numpy because of missing symbols
> > in numpy/core/umath.so
> > The symbols are
> > _acoshl$LDBL128
Sebastian Haase wrote:
> Hi!
> When I try running my code on
> panther (10.3) with a numpy that was built on tiger (10.4)
> it can't load numpy because of missing symbols
> in numpy/core/umath.so
> The symbols are
> _acoshl$LDBL128
> _acosl$LDBL128
> _asinhl$LDBL128
>
> (see my post from 5 oct 200
Hi!
When I try running my code on
panther (10.3) with a numpy that was built on tiger (10.4)
it can't load numpy because of missing symbols
in numpy/core/umath.so
The symbols are
_acoshl$LDBL128
_acosl$LDBL128
_asinhl$LDBL128
(see my post from 5 oct 2006:
http://permalink.gmane.org/gmane.comp.pyth
10 matches
Mail list logo
