Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#39890 - [libplist] cannot build the package

Attached to Project: Arch Linux
Opened by Perfect_Gentleman (Perfect_Gentleman) - Wednesday, 16 April 2014, 03:41 GMT
Last edited by Jan de Groot (JGC) - Thursday, 04 June 2015, 10:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
-----------------------------------------------------------------
checking for a Python interpreter with version >= 2.3... python
checking for python... /usr/bin/python
checking for python version... 3.4
checking for python platform... linux
checking for python script directory... ${prefix}/lib/python3.4/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python3.4/site-packages
checking for cython... no
configure: WARNING: cannot find 'cython' program. You should look at http://www.cython.org or install your distribution specific cython package.
checking for python3.4... (cached) /usr/bin/python
checking for a version of Python >= '2.1.0'... yes
checking for the distutils Python package... yes
checking for Python include path... -I/usr/include/python3.4m
checking for Python library path... -L/usr/lib/python3.4 -lpython3.4
checking for Python site-packages path... /usr/lib/python3.4/site-packages
checking python extra libraries... -lpthread -ldl -lutil
checking python extra linking flags... -Xlinker -export-dynamic
checking consistency of all components of python development environment... no
configure: error:
Could not link test program to Python. Maybe the main Python library has been
installed in some non-standard library path. If so, pass it to configure,
via the LDFLAGS environment variable.
Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
============================================================================
ERROR!
You probably have to install the development version of the Python package
for your distribution. The exact name of this package varies among them.
============================================================================

==> ERROR: A failure occurred in build().
---------------------------------------------------------------------------------


Additional info:
* package version(s) - 1.11
* config and/or log files etc.


Steps to reproduce:
makepkg
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 04 June 2015, 10:27 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Wednesday, 16 April 2014, 04:02 GMT
Builds fine for me in a clean chroot, which is all that really matters. Looks like it doesn't build if Python 3 is installed. Adding export PYTHON=python2 does fix it, but it's not required since everything is built in a clean chroot.
Comment by Perfect_Gentleman (Perfect_Gentleman) - Wednesday, 16 April 2014, 04:48 GMT
yes, adding export PYTHON=python2 fixed it.
but i update my system using yaourt -Syub, so for me it is essential
Comment by Doug Newgard (Scimmia) - Wednesday, 16 April 2014, 04:54 GMT
You using an unsupported 3rd party script to update your system does not make this a bug. It's up to the maintainer if they want to make this work outside a chroot or not.
Comment by Perfect_Gentleman (Perfect_Gentleman) - Wednesday, 16 April 2014, 05:21 GMT
i used ABS and makepkg,the result was the same
Comment by mattia (nTia89) - Monday, 17 November 2014, 17:39 GMT
I confirm the bug with libplist-1.11-1
Comment by Kerry (secdef9) - Thursday, 08 January 2015, 17:11 GMT
I think the configure script does not properly determine flags to pass to the linker when compiling a test program.

I solved this by passing PYTHON_LDFLAGS="-lpython3.4m" to the "./configure" line in build()

Loading...