Hi Bob,
On Jan 26, 2006, at 10:44 PM, Bob Ippolito wrote:
[snip]
> Another approach would be to write a little front-end for GCC that
> knows how to mangle the arguments properly so that it ends up
> running GCC 3.3 against the 10.3 SDK then GCC 4 against the
> universal SDK and lipo the o
Hi Bob,
On Jan 26, 2006, at 10:55 PM, Bob Ippolito wrote:
[snip]
>> Sorry, I wasn't really thinking about extensions. By Panther I did
>> mean building against the 10.3.9 SDK, which would give the desired
>> results for the Python binary itself, but as you said extending
>> that to correct
On Jan 26, 2006, at 10:39 PM, Kevin Ollivier wrote:
> On Jan 26, 2006, at 7:02 PM, Bob Ippolito wrote:
>
> [snip]
>
>>> IMHO, what would be cool is to allow the user to pass the SDK in as
>>> some sort of configure flag or maybe a shell variable, something
>>> like:
>>>
>>> ./configure MACOSX_
On Jan 26, 2006, at 7:02 PM, Bob Ippolito wrote:
>
> On Jan 26, 2006, at 6:28 PM, Kevin Ollivier wrote:
>
>> On Jan 26, 2006, at 12:48 AM, Ronald Oussoren wrote:
>>
>> [snip]
>>
>>> I'm (very slowly) playing around with adding '-arch ppc -arch i386'
>>> to the build flags and building on an intel
Hi Bob,
On Jan 26, 2006, at 7:02 PM, Bob Ippolito wrote:
[snip]
>> IMHO, what would be cool is to allow the user to pass the SDK in as
>> some sort of configure flag or maybe a shell variable, something
>> like:
>>
>> ./configure MACOSX_SDK=/my/path/to/SDK
>>
>> This, along with the addition
Hi,
On Jan 26, 2006, at 7:22 PM, bear wrote:
> Ronald Oussoren wrote:
>> That part is easy enough. If you want a framework build you'll
>> have to
>> patch Makefile.pre.in because it contains a hardcoded '-arch ppc' in
>> the section that builds that actual framework. Otherwise it should
>> jus
Ronald Oussoren wrote:
> That part is easy enough. If you want a framework build you'll have to
> patch Makefile.pre.in because it contains a hardcoded '-arch ppc' in
> the section that builds that actual framework. Otherwise it should
> just build (assuming you have an intel mac of course, cros
On Jan 26, 2006, at 6:28 PM, Kevin Ollivier wrote:
> On Jan 26, 2006, at 12:48 AM, Ronald Oussoren wrote:
>
> [snip]
>
>> I'm (very slowly) playing around with adding '-arch ppc -arch i386'
>> to the build flags and building on an intel host. That way you won't
>> have to use SDKs, which makes it
Hi Ronald,
On Jan 26, 2006, at 12:48 AM, Ronald Oussoren wrote:
[snip]
> I'm (very slowly) playing around with adding '-arch ppc -arch i386'
> to the build flags and building on an intel host. That way you won't
> have to use SDKs, which makes it less likely that configure picks up
> other infor
Hi folks,
I'm trying to write an example screensaver in PyObjC which is a bit
more complex than the existing example. One of the things I've added
is a sheet to configure the screensaver. I'm doing something wrong
there (was doing more things wrong, but I found some of them) and the
scre
David M. Cooke wrote:
> I don't know specifically about the G5, but Numeric, numarray, and
> numpy are routinely compiled and run on 64-bit Athlon machines, so a
> lot of the bugs and such have already been shaken out.
>
> If possible, you should move from Numeric to numpy; one of the goals
> for
Michael Barber <[EMAIL PROTECTED]> writes:
> I have been using Python for scientific computing on a variety of
> systems, Mac and otherwise, with a recent focus on properties of
> interaction networks. Until now, I have not needed to use more than
> roughly 1 GB of RAM at a time. Thanks to s
I have been using Python for scientific computing on a variety of
systems, Mac and otherwise, with a recent focus on properties of
interaction networks. Until now, I have not needed to use more than
roughly 1 GB of RAM at a time. Thanks to some fairly straightforward
scaling properties, it
> [EMAIL PROTECTED] (s) wrote:
>s> Apparently the readline library in MacOSX isn't really readline. It's a
>s> renamed libedit. Not having encountered this deception before, Python's
>s> build procedure doesn't know to test the capability of readline. I suggest
>s> you just comment out the
On 26-jan-2006, at 0:47, bear wrote:
> Bob Ippolito wrote:
>> One thing to note is that you can probably build with minimal
>> patching
>> (via the universal SDK), but the result will only run on Mac OS X
>> 10.4
>> and later. It requires major patching in order to create a Python
>> binary
15 matches
Mail list logo
