octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #61024] [mxe-octave] build-markupsafe fails to


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #61024] [mxe-octave] build-markupsafe fails to build if build-python3 is built without libffi
Date: Mon, 9 Aug 2021 14:14:41 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

URL:
  <https://savannah.gnu.org/bugs/?61024>

                 Summary: [mxe-octave] build-markupsafe fails to build if
build-python3 is built without libffi
                 Project: GNU Octave
            Submitted by: jwe
            Submitted on: Mon 09 Aug 2021 06:14:40 PM UTC
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: jwe
        Originator Email: 
             Open/Closed: Open
                 Release: dev
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

I hit the following problem when doing an mxe-octave build on a new system:


[build]    build-markupsafe

Failed to build package build-markupsafe!
------------------------------------------------------------
make[2]: Entering directory '/scratch/build/mxe-octave-w64/default'
rm -rf   '/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe'
'/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe-install'
mkdir -p '/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe'
( cd '/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe' &&  tar xzf
'/share/mxe-octave/pkg-src/MarkupSafe-1.0.tar.gz' ) ||  false 
test ! -d '/home/jwe/src/mxe-octave/src/build-markupsafe' || cp -a
'/home/jwe/src/mxe-octave/src/build-markupsafe'
'/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe'
cd
'/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe/MarkupSafe-1.0'
cd '/scratch/build/mxe-octave-w64/default/tmp-build-markupsafe/MarkupSafe-1.0'
&& python3 setup.py install
--prefix='/scratch/build/mxe-octave-w64/default/usr'
Traceback (most recent call last):
  File "setup.py", linlibffi-dee 6, in <module>
    from setuptools import setup, Extension, Feature
  File
"/scratch/build/mxe-octave-w64/default/usr/lib/python3.8/site-packages/setuptools/__init__.py",
line 20, in <module>
    from setuptools.dist import Distribution, Feature
  File
"/scratch/build/mxe-octave-w64/default/usr/lib/python3.8/site-packages/setuptools/dist.py",
line 35, in <module>
    from setuptools import windows_support
  File
"/scratch/build/mxe-octave-w64/default/usr/lib/python3.8/site-packages/setuptools/windows_support.py",
line 2, in <module>
    import ctypes
  File
"/scratch/build/mxe-octave-w64/default/usr/lib/python3.8/ctypes/__init__.py",
line 7, in <module>
    from _ctypes import Union, Structure, Array
ModuleNotFoundError: No module named '_ctypes'
make[2]: *** [/scratch/build/mxe-octave-w64/default/Makefile:977:
build-only-build-markupsafe] Error 1


After installing libffi-dev on the build system and rebuilding the
build-python3 package in mxe-octave, the problem is gone and the
build-markupsafe package builds successfully.  But maybe we should have rules
to build the libffi package as part of the mxe-octave build rules so we can
control the version that is used and to avoid this problem in the future?





    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61024>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]