PinebookPro Build Errors

[mexsudo]

Build Errors:

I am having a glitch, both of these packages are showing in the add/remove software "updates"

python2-cffi 1.15.0-1
python2-pycparser 2.21-1

I don't know where to start...

I have tried updating seperatly, but still get the same darn errors:
===================
Preparing...
Cloning python2-cffi build files...
Generating python2-cffi information...
Checking python2-cffi dependencies...
Cloning python2-pycparser build files...
Generating python2-pycparser information...
Checking python2-pycparser dependencies...
Synchronizing package databases...
Warning: libtool: local (2.4.6+44+gb9b44533-11) is newer than core (2.4.6+42+gb88cebd5-15)
Warning: xorg-xwayland: local (21.1.2.901-1) is newer than extra (21.1.2-1)
Resolving dependencies...
Checking inter-conflicts...

Building python2-pycparser...
==> Making package: python2-pycparser 2.21-1 (Sun 09 Jan 2022 05:57:31 AM PST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found python2-pycparser-2.21.tar.gz
==> Validating source files with sha512sums...
    python2-pycparser-2.21.tar.gz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting python2-pycparser-2.21.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
running build
running build_py
creating build
creating build/lib
creating build/lib/pycparser
copying pycparser/c_ast.py -> build/lib/pycparser
copying pycparser/_ast_gen.py -> build/lib/pycparser
copying pycparser/__init__.py -> build/lib/pycparser
copying pycparser/ast_transforms.py -> build/lib/pycparser
copying pycparser/c_generator.py -> build/lib/pycparser
copying pycparser/_build_tables.py -> build/lib/pycparser
copying pycparser/c_lexer.py -> build/lib/pycparser
copying pycparser/plyparser.py -> build/lib/pycparser
copying pycparser/c_parser.py -> build/lib/pycparser
creating build/lib/pycparser/ply
copying pycparser/ply/lex.py -> build/lib/pycparser/ply
copying pycparser/ply/__init__.py -> build/lib/pycparser/ply
copying pycparser/ply/yacc.py -> build/lib/pycparser/ply
copying pycparser/ply/ctokens.py -> build/lib/pycparser/ply
copying pycparser/ply/ygen.py -> build/lib/pycparser/ply
copying pycparser/ply/cpp.py -> build/lib/pycparser/ply
copying pycparser/_c_ast.cfg -> build/lib/pycparser
==> Starting check()...
Generating LALR tables
WARNING: 79 shift/reduce conflicts
WARNING: 37 reduce/reduce conflicts
WARNING: reduce/reduce conflict in state 27 resolved using rule (type_specifier -> atomic_specifier)
WARNING: rejected rule (empty -> <empty>) in state 27
WARNING: reduce/reduce conflict in state 87 resolved using rule (type_specifier -> atomic_specifier)
WARNING: rejected rule (empty -> <empty>) in state 87
WARNING: reduce/reduce conflict in state 437 resolved using rule (statement -> pppragma_directive)
WARNING: rejected rule (empty -> <empty>) in state 437
.....F............................................................................................................................
======================================================================
FAIL: test_all_examples (tests.test_examples.TestExamplesSucceed)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/var/tmp/pamac-build-peter/python2-pycparser/src/pycparser-release_v2.21/tests/test_examples.py", line 29, in test_all_examples
    rc, 0, 'example "{}" failed with stdout =\n{}'.format(filename, stdout))
AssertionError: example "using_gcc_E_libc.py" failed with stdout =


----------------------------------------------------------------------
Ran 130 tests in 8.235s

FAILED (failures=1)
==> ERROR: A failure occurred in check().
    Aborting...

[fleamour]

I have exact error with only python2-pycparser 2.20-3 to 2.21-1. I t throws a build error the very same. I was able to install the other package you mention by ignoring pycparser package. I do however have a Lenovo ThinkPad X250.

[fleamour]

The solution for me was delete offending package then reinstall.

[mexsudo]

The solution for me was delete offending package then reinstall.

Thanks, that's good thought.

on my system I have a dozen or so dependencies...
I will give it a shot later.