Message88825
| Author |
ebehar |
| Recipients |
benjamin.peterson, brett.cannon, brodie, ebehar, erickt, mark.dickinson, rpetrov, tarek |
| Date |
2009年06月03日.20:42:23 |
| SpamBayes Score |
1.2477669e-10 |
| Marked as misclassified |
No |
| Message-id |
<1244061746.04.0.972388442398.issue6154@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|