This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients ned.deily, ronaldoussoren, srid, tarek
Date 2009-06-02.10:12:48
SpamBayes Score 1.1401135e-08
Marked as misclassified No
Message-id <1243937571.03.0.994273453921.issue6170@psf.upfronthosting.co.za>
In-reply-to
Content
I found the issue.

In r72899 antoine.pitrou checked in a change that adds these two lines 
to the bininstall target in Makefile.pre.in:

   -rm -f $(DESTDIR)$(LIBPC)/python3.pc
   (cd $(DESTDIR)$(LIBPC); $(LN) -s python-$(VERSION).pc python3.pc)

This exposes a bug in the configure script, which causes target 
'bininstall' to run before 'libainstall' when your doing a framework 
install.  The latter target is the one that creates python-
$(VERSION).pc, which is why we get build failures.

What I don't understand is why I've been able to install frameworks all 
along and didn't notice this before. 

I'm working on a patch, and will check that in after I've full tested 
it.

The important bit of the patch is this change to configure.in:

-		FRAMEWORKALTINSTALLFIRST="frameworkinstallstructure 
bininstall maninstall"
+		FRAMEWORKALTINSTALLFIRST="frameworkinstallstructure "
History
Date User Action Args
2009-06-02 10:12:51ronaldoussorensetrecipients: + ronaldoussoren, tarek, ned.deily, srid
2009-06-02 10:12:51ronaldoussorensetmessageid: <1243937571.03.0.994273453921.issue6170@psf.upfronthosting.co.za>
2009-06-02 10:12:48ronaldoussorenlinkissue6170 messages
2009-06-02 10:12:48ronaldoussorencreate