[issue3585] pkg-config support

Changes by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue3585] pkg-config support

Martin v. Löwis added the comment: > Ouch, unfortunately it seems my distribution doesn't package autoconf > 2.61. Is there any risk in installing it from scratch? I usually install it into a private location, such as ~/ac261. This is absolutely safe. -- __

[issue3585] pkg-config support

Antoine Pitrou added the comment: Ouch, unfortunately it seems my distribution doesn't package autoconf 2.61. Is there any risk in installing it from scratch? -- ___ Python tracker _

[issue3585] pkg-config support

Martin v. Löwis added the comment: > I did get that message (and got puzzled by it). > I worked around it by reading the file in universal newlines mode and > saving it again. I believe this has broken part of the configure script. There is an ac_cr variable that is supposed to hold a sole carr

[issue3585] pkg-config support

Antoine Pitrou added the comment: > Yes: it puts a carriage-return character into configure > which completely confuses subversion. > > I'm puzzled how you were able to commit the generated > files; subversion should have reported an error > > svn: File 'configure' has inconsistent newlines >

[issue3585] pkg-config support

Martin v. Löwis added the comment: > Oops, sorry. Are there any known issues with 2.63? Yes: it puts a carriage-return character into configure which completely confuses subversion. I'm puzzled how you were able to commit the generated files; subversion should have reported an error svn: File

[issue3585] pkg-config support

Antoine Pitrou added the comment: > Antoine: Don't use autoconf 2.63 to generate pyconfig.h.in and > configure. Use 2.61 instead (until it is agreed to switch to a newer > version). Oops, sorry. Are there any known issues with 2.63? -- ___ Python tr

[issue3585] pkg-config support

Martin v. Löwis added the comment: Antoine: Don't use autoconf 2.63 to generate pyconfig.h.in and configure. Use 2.61 instead (until it is agreed to switch to a newer version). -- nosy: +loewis ___ Python tracker _

[issue3585] pkg-config support

Antoine Pitrou added the comment: The patch is committed in trunk (r72898) and py3k (r72899). Thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue3585] pkg-config support

Clinton Roy added the comment: Not that I can see, or remember. Revised patch attached. Tyop fixed as well. Please note there seem to be some issues with svn head atm, pyconfig.h.in and configure would seem to be out of whack with configure.in, this patch does not include changes to those gener

[issue3585] pkg-config support

Antoine Pitrou added the comment: Is there any reason in versioning Misc/python.pc, instead of versioning it only on install? -- ___ Python tracker ___ __

[issue3585] pkg-config support

Antoine Pitrou added the comment: Patch looks good here. -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue3585] pkg-config support

sol added the comment: I totally agree. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue3585] pkg-config support

Clinton Roy added the comment: Hi Sol, It's just a data file I suppose, Python should not need a dependency on pkg-config, and neither should there be a python-pkgconfig package that just contains the python.pc file. I think the approach to just always install the python.pc file is the right o

[issue3585] pkg-config support

sol added the comment: >> - Shouldn't this file be installed only if the pkg-config utility is >> present, or if the directory $(LIBDIR)/pkgconfig already exists? > > Technically I suppose so > That would mean that, if you first install Python and afterwards pkg-config, pkg-config would not wor

[issue3585] pkg-config support

Clinton Roy added the comment: Oh, you meant for me to reply =) - Do all unix-like system support pkg-config? Yes. It even works on windows. - Is $(LIBDIR)/pkgconfig the only choice for installing this file? While pkg-config can be told to look in other directories for pc files (via modifyin

[issue3585] pkg-config support

Amaury Forgeot d'Arc added the comment: The patch looks fine to me. I have however some questions to ask to someone more used to pkgconfig: - Do all unix-like system support pkg-config? - Is $(LIBDIR)/pkgconfig the only choice for installing this file? - Shouldn't this file be installed only

[issue3585] pkg-config support

Clinton Roy added the comment: Is there anything I can do to move this forward at all? cheers, ___ Python tracker ___ ___ Python-bugs-list mai

[issue3585] pkg-config support

Clinton Roy <[EMAIL PROTECTED]> added the comment: This version sets Libs.private for static compiles. Any chance this will make it into the 2.6/3.0 release candidates ? cheers, Added file: http://bugs.python.org/file11368/pkgconfig.diff ___ Python tracker

[issue3585] pkg-config support

Clinton Roy <[EMAIL PROTECTED]> added the comment: Thanks for the comments Amaury, this patch uses ${VERSION} throughout so that it can be applied across branches. cheers, Added file: http://bugs.python.org/file11152/pkgconfig.diff ___ Python tracker <[EMAIL

[issue3585] pkg-config support

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I cannot discuss about the feature itself, but the patch should certainly use some macro ($(VERSION) ?) instead of the hardcoded "2.6". Likewise, source files should not contain version number in their names, or they cannot be merged bet

[issue3585] pkg-config support

New submission from Clinton Roy <[EMAIL PROTECTED]>: This patch adds pkg-config support to the python build, a python.pc file is installed in the pkgconfig directory such that autoconf buildsystems can trivially link against the python library. Diff made against revision 65796 -- compon