Message108440
| Author |
lemburg |
| Recipients |
benjamin.peterson, lemburg, ned.deily, ronaldoussoren |
| Date |
2010年06月23日.08:35:51 |
| SpamBayes Score |
5.064521e-08 |
| Marked as misclassified |
No |
| Message-id |
<4C21C765.7030907@egenix.com> |
| In-reply-to |
<1277281477.07.0.232720019536.issue9046@psf.upfronthosting.co.za> |
| Content |
Ronald Oussoren wrote:
>
> Ronald Oussoren <ronaldoussoren@mac.com> added the comment:
>
> That (/usr/local/src) explains why I haven't been able to reproduce the problem, that worried me a little.
>
> W.r.t. to the SDK:
>
> 1) You don't have to use an SDK: use
>
> configure --enable-universalsdk=/ MACOSX_DEPLOYMENT_TARGET=10.5
>
> (or whatever target you wish to support)
Well, we want to build universal binaries, so we do need the SDK.
> 2) The SDK should only affect system files, that is anything in /System
> and /usr (except for /usr/local). /Library is not part of the SDK
> and is not affected by SDK settings.
Sorry, I should have written /System/Library/. You find Tcl
in /System/Library, but not in
/Developer/SDKs/MacOSX10.4u.sdk/System/Library/
Anyway, this doesn't appear to matter, since setup.py picks up the
files from a different dir: /System/Library/Frameworks/Tk.framework
and that is included in the SDK.
As I said: The fix makes the build work, so it's good enough for
now. In the future all this may will have to be revisited. |
|