Arch Linux User Repository

I'm currently unable to build this, every time I try the computer slow to a crawl, and fail with an error.

IF any of you can build this succesfully and test it works as intended, please tell me. I will appoint a comantainer. Thanks for understainding.

When I attempt to build 1.26.1-2 I get the following failure.

efl/eo/efl.eo.c: In function ‘__pyx_tp_dealloc_3efl_2eo_Eo’:
efl/eo/efl.eo.c:5443:104: error: implicit declaration of function ‘_PyGC_FINALIZED’ [-Wimplicit-function-declaration]
 5443 |   if (unlikely(PyType_HasFeature(Py_TYPE(o), Py_TPFLAGS_HAVE_FINALIZE) && Py_TYPE(o)->tp_finalize) && !_PyGC_FINALIZED(o)) {
      |                                                                                                        ^~~~~~~~~~~~~~~
efl/eo/efl.eo.c: In function ‘__Pyx_PyInt_As_int’:
efl/eo/efl.eo.c:9221:27: error: too few arguments to function ‘_PyLong_AsByteArray’
 9221 |                 int ret = _PyLong_AsByteArray((PyLongObject *)v,
      |                           ^~~~~~~~~~~~~~~~~~~
In file included from /usr/include/python3.13/longobject.h:107,
                 from /usr/include/python3.13/Python.h:81,
                 from efl/eo/efl.eo.c:38:
/usr/include/python3.13/cpython/longobject.h:111:17: note: declared here
  111 | PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
      |                 ^~~~~~~~~~~~~~~~~~~
efl/eo/efl.eo.c: In function ‘__Pyx_PyInt_As_long’:
efl/eo/efl.eo.c:9493:27: error: too few arguments to function ‘_PyLong_AsByteArray’
 9493 |                 int ret = _PyLong_AsByteArray((PyLongObject *)v,
      |                           ^~~~~~~~~~~~~~~~~~~
/usr/include/python3.13/cpython/longobject.h:111:17: note: declared here
  111 | PyAPI_FUNC(int) _PyLong_AsByteArray(PyLongObject* v,
      |                 ^~~~~~~~~~~~~~~~~~~
error: command '/usr/bin/gcc' failed with exit code 1
==> ERROR: A failure occurred in build().
    Aborting...

there's an undeclared python-setuptools dependency, otherwise builds with no problems.

Updated package, and it fixes python 3.11 errors. Please test!

Python-efl 1.26.1 is finally out, and should fix build issues on py3.11

I get build error

running build_ext
building 'efl.eo' extension
creating build/temp.linux-x86_64-cpython-311
creating build/temp.linux-x86_64-cpython-311/efl
creating build/temp.linux-x86_64-cpython-311/efl/eo
gcc -DNDEBUG -g -fwrapv -O3 -Wall -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -ffat-lto-objects -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -g -ffile-prefix-map=/build/python/src=/usr/src/debug/python -flto=auto -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.11 -c efl/eo/efl.eo.c -o build/temp.linux-x86_64-cpython-311/efl/eo/efl.eo.o -I/usr/include/eo-1 -I/usr/include/eina-1 -I/usr/include/eina-1/eina -pthread -fno-var-tracking-assignments -Wno-misleading-indentation -Wno-deprecated-declarations -Wno-unused-variable -Wno-format-security
efl/eo/efl.eo.c: In function ‘__Pyx_PyErr_GetTopmostException’:
efl/eo/efl.eo.c:7417:21: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7417 |     while ((exc_info->exc_type == NULL || exc_info->exc_type == Py_None) &&
      |                     ^~
efl/eo/efl.eo.c:7417:51: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7417 |     while ((exc_info->exc_type == NULL || exc_info->exc_type == Py_None) &&
      |                                                   ^~
efl/eo/efl.eo.c: In function ‘__Pyx__ExceptionSave’:
efl/eo/efl.eo.c:7431:21: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7431 |     *type = exc_info->exc_type;
      |                     ^~
efl/eo/efl.eo.c:7433:19: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_traceback’
 7433 |     *tb = exc_info->exc_traceback;
      |                   ^~
efl/eo/efl.eo.c: In function ‘__Pyx__ExceptionReset’:
efl/eo/efl.eo.c:7447:24: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7447 |     tmp_type = exc_info->exc_type;
      |                        ^~
efl/eo/efl.eo.c:7449:22: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_traceback’
 7449 |     tmp_tb = exc_info->exc_traceback;
      |                      ^~
efl/eo/efl.eo.c:7450:13: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7450 |     exc_info->exc_type = type;
      |             ^~
efl/eo/efl.eo.c:7452:13: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_traceback’
 7452 |     exc_info->exc_traceback = tb;
      |             ^~
efl/eo/efl.eo.c: In function ‘__Pyx__GetException’:
efl/eo/efl.eo.c:7534:28: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7534 |         tmp_type = exc_info->exc_type;
      |                            ^~
efl/eo/efl.eo.c:7536:26: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_traceback’
 7536 |         tmp_tb = exc_info->exc_traceback;
      |                          ^~
efl/eo/efl.eo.c:7537:17: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_type’
 7537 |         exc_info->exc_type = local_type;
      |                 ^~
efl/eo/efl.eo.c:7539:17: error: ‘_PyErr_StackItem’ {aka ‘struct _err_stackitem’} has no member named ‘exc_traceback’
 7539 |         exc_info->exc_traceback = local_tb;
      |                 ^~
efl/eo/efl.eo.c: In function ‘__Pyx_AddTraceback’:
efl/eo/efl.eo.c:464:62: error: invalid use of incomplete typedef ‘PyFrameObject’ {aka ‘struct _frame’}
  464 |   #define __Pyx_PyFrame_SetLineNumber(frame, lineno)  (frame)->f_lineno = (lineno)
      |                                                              ^~
efl/eo/efl.eo.c:8885:5: note: in expansion of macro ‘__Pyx_PyFrame_SetLineNumber’
 8885 |     __Pyx_PyFrame_SetLineNumber(py_frame, py_line);
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
error: command '/usr/lib/ccache/bin/gcc' failed with exit code 1

@lightdot Looks like python 3.11 has dropped some objects used in old implementations, and we might need a new version of Cython to come out and generate correct C++ code for python3.11...

Fails to build with Python 3.11 in a clean chroot, Python 3.10 was fine.

A build dependency of python-setuptools is required.

It builds successfully for me with efl-git, econnman works normally with it

@philb38 Being newer doesn't matter. FX are of a problematic architecture (and evolution with the same problems), that was slower then frequency can make you think. Also it is prone to overheating ans so performance degradation for thermal throttling. Plus many motherboards for that architectures, expecially for first generations, had similar overheating issues on the VRM, and so other performance degradation.

The fact that with a laptop booting into the system and starting firefox made temperatures of 80-90C is indicative.

I use an AMD PhenomII X4, so really older than yours... ;)