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 shlomif
Recipients shlomif, zach.ware
Date 2017-07-12.19:51:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499889099.43.0.350164863962.issue30912@psf.upfronthosting.co.za>
In-reply-to
Content
Running "make" in cpython git master on mageia linux v6 x86-64 gives me this problem with ffi:

<<<<<<<<
running build
running build_ext
Header file /usr/include/ffi.h does not define LIBFFI_H or ffi_wrapper_h
INFO: Could not locate ffi libs and/or headers

The following modules found by detect_modules() in setup.py, have been
built by the Makefile instead, as configured by the Setup files:
atexit                pwd                   time


Failed to build these modules:
_ctypes

running build_scripts
copying and adjusting /home/shlomif/Download/unpack/prog/python/cpython/Tools/scripts/pydoc3 -> build/scripts-3.7
copying and adjusting /home/shlomif/Download/unpack/prog/python/cpython/Tools/scripts/idle3 -> build/scripts-3.7
copying and adjusting /home/shlomif/Download/unpack/prog/python/cpython/Tools/scripts/2to3 -> build/scripts-3.7
copying and adjusting /home/shlomif/Download/unpack/prog/python/cpython/Tools/scripts/pyvenv -> build/scripts-3.7
changing mode of build/scripts-3.7/pydoc3 from 644 to 755
changing mode of build/scripts-3.7/idle3 from 644 to 755
changing mode of build/scripts-3.7/2to3 from 644 to 755
changing mode of build/scripts-3.7/pyvenv from 644 to 755
renaming build/scripts-3.7/pydoc3 to build/scripts-3.7/pydoc3.7
renaming build/scripts-3.7/idle3 to build/scripts-3.7/idle3.7
renaming build/scripts-3.7/2to3 to build/scripts-3.7/2to3-3.7
renaming build/scripts-3.7/pyvenv to build/scripts-3.7/pyvenv-3.7
>>>>>>>

<<<<<<
commit d1cc037d1442cc35d1b194ec8e50901514360949
Author: Victor Stinner <victor.stinner@gmail.com>
Date:   Wed Jul 12 16:05:43 2017 +0200

    bpo-30908: Fix dangling thread in test_os.TestSendfile (#2680)

    tearDown() now clears explicitly the self.server variable to make
    sure that the thread is completely cleared when tearDownClass()
    checks if all threads have been cleaned up.

    Fix the following warning:

    $ ./python -m test --fail-env-changed -m test.test_os.TestSendfile.test_keywords -R 3:1 test_os
    (...)
    Warning -- threading_cleanup() failed to cleanup 0 threads after 3 sec (count: 0, dangling: 2)
    (...)
    Tests result: ENV CHANGED
>>>>>

The problem is that my /usr/include/ffi.h looks like this:

<<<<
#define _MULTIARCH_HEADER ffi.h
#include <multiarch-dispatch.h>
>>>>
History
Date User Action Args
2017-07-12 19:51:39shlomifsetrecipients: + shlomif, zach.ware
2017-07-12 19:51:39shlomifsetmessageid: <1499889099.43.0.350164863962.issue30912@psf.upfronthosting.co.za>
2017-07-12 19:51:39shlomiflinkissue30912 messages
2017-07-12 19:51:39shlomifcreate