Evan Behar <beh...@gmail.com> added the comment:
Nevermind, my bad. With Brett's patch, the build does not work with
--enable-framework
It appears that configure.in makes no assignment to FRAMEWORKLINK or
AC_SUBST call with it, and so it is deposited in the final Makefile
verbatim as @FRAMEWORKLINK@
If --enable-framework is defined, then this compiler command in
Makefile.pre:461 gets executed:
$(CC) -o $(LDLIBRARY) -dynamiclib \
-isysroot "${UNIVERSALSDK}" \
-all_load $(LIBRARY) -Wl,-single_module \
-install_name
$(DESTDIR)$(PYTHONFRAMEWORKINSTALLDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK)
\
-compatibility_version $(VERSION) \
-current_version $(VERSION) \
$(FRAMEWORKLINK);
Which expands $(FRAMEWORKLINK) to @FRAMEWORKLINK@ because of this.
This makes no use of LIBS or any other environment variable that might
contain -lintl or -framework CoreFoundation, and the build will fail
with linker errors citing undefined intl and CFString symbols.
Attached is a patch that fixes this issue; it combines brett's lintl
patch with the fix for --enable-framework.
----------
Added file: http://bugs.python.org/file14174/darwin_lintl_framework.patch
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue6154>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
