On 30-dec-04, at 21:01, Bob Ippolito wrote:
On Dec 30, 2004, at 2:52 PM, Ronald Oussoren wrote:
On 30-dec-04, at 18:49, Bob Ippolito wrote:
On Dec 30, 2004, at 11:44 AM, Jack Jansen wrote:
On 30-dec-04, at 10:02, Ronald Oussoren wrote:
In the quick-and-dirty-hacks category: you could write two simp
On Dec 30, 2004, at 2:52 PM, Ronald Oussoren wrote:
On 30-dec-04, at 18:49, Bob Ippolito wrote:
On Dec 30, 2004, at 11:44 AM, Jack Jansen wrote:
On 30-dec-04, at 10:02, Ronald Oussoren wrote:
In the quick-and-dirty-hacks category: you could write two simple
shell-scripts that start the compiler wi
On 30-dec-04, at 18:49, Bob Ippolito wrote:
On Dec 30, 2004, at 11:44 AM, Jack Jansen wrote:
On 30-dec-04, at 10:02, Ronald Oussoren wrote:
In the quick-and-dirty-hacks category: you could write two simple
shell-scripts that start the compiler with the right environment
variables:
run-cc:
#!
On Dec 30, 2004, at 11:44 AM, Jack Jansen wrote:
On 30-dec-04, at 10:02, Ronald Oussoren wrote:
In the quick-and-dirty-hacks category: you could write two simple
shell-scripts that start the compiler with the right environment
variables:
run-cc:
#!/bin/sh
env MACOSX_DEPLOYMENT_TARGET=10.
On 30-dec-04, at 10:02, Ronald Oussoren wrote:
In the quick-and-dirty-hacks category: you could write two simple
shell-scripts that start the compiler with the right environment
variables:
run-cc:
#!/bin/sh
env MACOSX_DEPLOYMENT_TARGET=10.3 gcc "[EMAIL PROTECTED]"
run-c++:
#!/bin
On 30-dec-04, at 0:25, Jack Jansen wrote:
On 29-dec-04, at 11:40, Bob Ippolito wrote:
[Bob notes that my PantherPythonFix installer will break C++
compilation because distutils simply replaces the first component of
LDSHARED with "c++"]
Any suggestions as to what to do to get c++ compilation fixe
