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 bennoleslie
Recipients bennoleslie, georg.brandl, loewis, orsenthil
Date 2013-01-06.01:44:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357436671.27.0.668965418711.issue16866@psf.upfronthosting.co.za>
In-reply-to
Content
I was using this in the case where I just want to link against libpython.a and for me it is a limited case where I don't really need the functionality of python-config; so for me this is certainly the best approach. But I concede this use case is probably a very little general interest.

If the goal is to have a working python-config, then I guess libainstall should depend on bininstall.

I'm not too fussed which approach is taken, I just think that (make && make libainstall) should work.

I'm happy to fashion a patch for whichever approach is thought to be best.
History
Date User Action Args
2013-01-06 01:44:31bennolesliesetrecipients: + bennoleslie, loewis, georg.brandl, orsenthil
2013-01-06 01:44:31bennolesliesetmessageid: <1357436671.27.0.668965418711.issue16866@psf.upfronthosting.co.za>
2013-01-06 01:44:31bennoleslielinkissue16866 messages
2013-01-06 01:44:30bennolesliecreate