Package Details: python-ocp 7.7.2.1+r4.g544d7fd5-4

Git Clone URL: https://aur.archlinux.org/python-ocp.git (read-only, click to copy)
Package Base: python-ocp
Description: Python wrapper for OCCT generated using pywrap
Upstream URL: https://github.com/CadQuery/OCP
Licenses: Apache-2.0
Conflicts: python-ocp-git
Submitter: greyltc
Maintainer: greyltc
Last Packager: greyltc
Votes: 1
Popularity: 0.000000
First Submitted: 2020-08-22 14:36 (UTC)
Last Updated: 2024-12-28 06:29 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

Auerhuhn commented on 2025-01-02 15:54 (UTC)

@greyltc Would you mind adding the fmt package to depends?
Without fmt, it builds cleanly but fails at runtime.

Auerhuhn commented on 2025-01-02 15:52 (UTC)

@s-ol I got the same error.

Rebuilding the clang15 package with these patches applied fixed it for me.

s-ol commented on 2024-12-27 23:09 (UTC)

Having problems building because of some clang version mismatch:

clang.cindex.LibclangError: /usr/lib/llvm15/lib/libclang.so.15.0.7: undefined symbol: clang_CXXMethod_isDeleted. Please ensure that your python bindings are compatible with your libclang.so version.

greyltc commented on 2024-06-07 16:51 (UTC)

It's probably not stuck, just takes forever to build. Leave it overnight if you think it might be stuck.

chilichiller commented on 2024-05-04 21:18 (UTC) (edited on 2024-05-04 21:32 (UTC) by chilichiller)

I am getting the same problem as Jikstra, the build process is stuck at "Running pywrap", exact same log as Jikstra had (just using Python 3.12). However, there was no issue with the latest fast_float version (6.1.0-2). Can anyone help to fix that?

Jikstra commented on 2024-03-05 16:55 (UTC)

I had to downgrad fast_float to 5.3.0 (sudo paru -U https://archive.archlinux.org/packages/f/fast_float/fast_float-5.3.0-1-any.pkg.tar.zst)

However, it's now stuck at "Running pywrap"

-- Running pywrap
'/usr/bin/python3.11' '-m' 'bindgen' '--njobs' '1' '-l' '/usr/lib/llvm15/lib/libclang.so.15.0.7' '-i' '/usr/lib/llvm15/include/' '-i' '/usr/include/vtk/' '-i' '/usr/lib/clang/16/include' 'all' 'ocp.toml' 'Linux'
^[[A
[W 240305 17:47:53 translation_unit:47] ./opencascade/Standard_WarningsRestore.hxx
[W 240305 17:47:53 translation_unit:48] dummy.cxx:42:28: warning: pragma diagnostic pop could not pop, no matching push [-Wunknown-pragmas]

ptomalak commented on 2024-01-21 09:11 (UTC) (edited on 2024-01-21 09:17 (UTC) by ptomalak)

It was failing for me with:

File "/home/user/builds/python-ocp/src/OCP/pywrap/bindgen/__init__.py", line 48, in read_symbols
sym = pd.read_csv(p,header=None,names=['name'],delim_whitespace=True,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: read_csv() got an unexpected keyword argument 'error_bad_lines'

in the Dumping symbols, then generating bindings... part of the building process just days after (eventually) successfully building it on other device. Same issue with the git version of this package.

A quick hack that fixed the issue for me was modifying PKGBUILD to include:

find ./ -type f -name "*.py" -exec sed -i 's/error_bad_lines=False/on_bad_lines = "skip"/g' {} +

In this part of the build:

build() {
cd OCP
local site_packages=$(python -c "import site; print(site.getsitepackages()[0])")
ln -s "${site_packages}"/clang15 clang
export PYTHONPATH="$(pwd):${PYTHONPATH}"

find ./ -type f -name "*.py" -exec sed -i 's/error_bad_lines=False/on_bad_lines = "skip"/g' {} +

msg2 "Dumping symbols, then generating bindings..."
PATH="/usr/lib/llvm15/bin/:${PATH}" LD_LIBRARY_PATH="/usr/lib/llvm15/lib:${LD_LIBRARY_PATH}" cmake -B new -S .
...

I did not delve deeper into how / why it works, I just applied the first fix given by looking up the error ( https://stackoverflow.com/questions/72210768/read-csv-got-an-unexpected-keyword-argument-on-bad-lines ). I hope someone finds it helpful, or confirms if it is a wider issue or just limited to my setup.

tapia commented on 2023-11-19 21:00 (UTC)

Hi greyltc, it works now! Thanks for fixing the issue ;)

greyltc commented on 2023-11-16 21:25 (UTC)

Should be fixed now tapia. Turns out the official package upgrade of clang/llvm and friends from version 15->16 on 2023-08-29 broke the build. Took me almost forever to figure this out and implement a fix :(

tapia commented on 2023-11-13 21:57 (UTC)

Hi, this is not compiling for me. Is it working for anyone?

1 2 3 4 5 Next › Last »