search

mkeeter / antimony

CAD from a parallel universe
2.09k stars 159 forks source link

libboost_python36.so.1.67.0: cannot open shared object file #210

Closed Pupo1 closed 4 years ago

Pupo1 commented 4 years ago

Hello,

on Debian 10 I get

antimony: error while loading shared libraries: libboost_python36.so.1.67.0: cannot open shared object file: No such file or directory

Linux 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux

regards, Pupo

mkeeter commented 4 years ago

What bindings to boost::python3 have you installed?

Last time I checked, they were part of libboost-all-dev, but that may not be true anymore – if that's not the case, please open a PR against BUILDING.md.

Pupo1 commented 4 years ago

Sorry, I have no idea how I check this. What command should I use to check the python3 binding?

mkeeter commented 4 years ago

I can't debug your specific Linux system, but try looking around in /usr/lib, /usr/local/lib, etc, for something that looks like libboost_python.*.

Pupo1 commented 4 years ago

Thank you for the hint. What do you mean with PR, a pull request? I installed libboost-all-dev, and find the following files looking similar to what you said: ./lib/x86_64-linux-gnu/libboost_python3-py37.so ./lib/x86_64-linux-gnu/libboost_mpi_python37.so.1.67.0 ./lib/x86_64-linux-gnu/libboost_mpi_python3-py37.a ./lib/x86_64-linux-gnu/libboost_python37.a ./lib/x86_64-linux-gnu/libboost_mpi_python3-py37.so ./lib/x86_64-linux-gnu/libboost_python37.so.1.67.0 ./lib/x86_64-linux-gnu/libboost_python3-py37.a

I don't know how to write a pull request, because I never did it... :-(

Best regards, Bernd

On Fr, 17. Jan 05:27, Matt Keeter wrote:

What bindings to boost::python3 have you installed?

Last time I checked, they were part of libboost-all-dev, but that may not be true anymore – if that's not the case, please open a PR against [1]BUILDING.md.

— You are receiving this because you authored the thread. Reply to this email directly, [2]view it on GitHub, or [3]unsubscribe.

References

Visible links

  1. https://github.com/mkeeter/antimony/blob/develop/BUILDING.md
  2. https://github.com/mkeeter/antimony/issues/210?email_source=notifications&email_token=ABP4G62VISWAEIJKYOO2K23Q6GW3DA5CNFSM4KHYTCHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJHVQCQ#issuecomment-575625226
  3. https://github.com/notifications/unsubscribe-auth/ABP4G63H4DLU35L4SC5J44DQ6GW3DANCNFSM4KHYTCHA /home/pulmo/.elinks//elinks.conf:3: unknown command 
orthzar commented 4 years ago

Bernd,

I had the exact same issue on Debian 11 (Bullseye). However, Antimony is now working for me after a recent update.

From the Debian patches list, 0.9.3-1.1 resolves the issue. Debian 11 and Sid have that patch, but Debian 10 (Buster) does not.

Your options are:

Regards, orthzar

P.S. If Tiago sees this: thanks! I can now proceed with a project that I've been putting off.

mkeeter commented 4 years ago

Great, I'm going to close this issue as it's been resolved in newer versions of Debian.

Pupo1 commented 4 years ago

I still wanted to say thank you. to orthzar. I will just upgrade to Debian 11.

ceremcem commented 3 years ago

Anyone has a ready-to-apply solution for Debian Buster? Can we download current package and apply that patch manually, and then apt install antimony-patched.deb?

ceremcem commented 3 years ago

FYI: Upgrading to Debian 10 was not an option to me. I followed the following path instead:

  1. Create an LXC container:

    $ sudo lxc-create -n antimony -t debian -B btrfs -- -r bullseye --packages xbase-clients nano sudo $ sudo lxc-attach -n antimony antimony:~# adduser myuser

  2. Install Antimony via package manager:

    antimony:~# apt-get install antimony

  3. Run Antimony over ssh:

    ssh -X myuser@ip-of-lxc-container antimony

nerdCopter commented 3 years ago

if only Antimony came in .AppImage :thinking: ... same boat, Debian 10 Stable + buster-backports, still an issue.