runme.sh fails with missing libraries errors #1
Comments
|
That's the C++ based mapper not linking. Probably the Docker image got
updated or such.
What boost_python3 libraries are available in the image?
…On Tue, Aug 27, 2019, 13:47 Ivan Drobyshevskyi ***@***.***> wrote:
I've tried to execute runme.sh and it fails with the same errors on Ubuntu
16.04 and Ubuntu 18.04 (if host system matters at all).
Note: I supposed that runme.sh is what is supposed to be executed, would
be nice to add it to README if that's the case.
/home/pycat
/home/pycat/.abuild
/home/pycat/.abuild/pycat-5d64fa91.rsa
/home/pycat/.abuild/abuild.conf
/home/pycat/.abuild/pycat-5d64fa91.rsa.pub
/home/pycat/packages
/home/pycat/packages/pycat
/home/pycat/packages/pycat/x86_64
/home/pycat/packages/pycat/x86_64/APKINDEX.tar.gz
/home/pycat/packages/pycat/x86_64/rlwrap-doc-0.43-r0.apk
/home/pycat/packages/pycat/x86_64/rlwrap-0.43-r0.apk
/home/pycat/rlwrap
/home/pycat/rlwrap/APKBUILD
/home/pycat/pycat
(1/1) Installing rlwrap (0.43-r0)
Executing busybox-1.30.1-r2.trigger
OK: 527 MiB in 102 packages
Removing intermediate container 4cd0ab33579e
---> 98bfdc32e770
Step 17/17 : CMD cd pycat/mapper && make test && cd .. && ./start_client.sh
---> Running in 37380cfd1509
Removing intermediate container 37380cfd1509
---> e247208f40f1
Successfully built e247208f40f1
Successfully tagged pycat:latest
g++ -isystem /usr/include/python3.6m -c -std=c++14 -fPIC -Wall -Wextra -g -O0 -fmax-errors=1 -Winvalid-pch -o test_pch.hpp.gch test_pch.hpp
g++ -isystem /usr/include/python3.6m -c -std=c++14 -fPIC -Wall -Wextra -g -O0 -fmax-errors=1 -Winvalid-pch -o test.o test.cpp
g++ -isystem /usr/include/python3.6m -c -std=c++14 -fPIC -Wall -Wextra -g -O0 -fmax-errors=1 -Winvalid-pch -o mapper_pch.hpp.gch mapper_pch.hpp
g++ -isystem /usr/include/python3.6m -c -std=c++14 -fPIC -Wall -Wextra -g -O0 -fmax-errors=1 -Winvalid-pch -o mapper.o mapper.cpp
g++ -shared -o libmapper.so mapper.o
g++ -o unittest test.o -Wl,-rpath=`pwd` -L`pwd` -lmapper -lboost_unit_test_framework -lboost_serialization -lboost_python3 -lpython3.6m
**/usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/../../../../x86_64-alpine-linux-musl/bin/ld: cannot find -lboost_python3
/usr/lib/gcc/x86_64-alpine-linux-musl/8.3.0/../../../../x86_64-alpine-linux-musl/bin/ld: cannot find -lpython3.6m**
collect2: error: ld returned 1 exit status
make: *** [Makefile:35: unittest] Error 1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AAQIQF7YEZKKZ7CXJW52NMLQGUA2JA5CNFSM4IQC3Y4KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHTWYRQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQIQFZSHMWS6RFL4Y376ZDQGUA2JANCNFSM4IQC3Y4A>
.
|
|
|
I guess we'll need to change the makefile to link against -lboost_python37,
then.
…On Tue, Aug 27, 2019 at 2:38 PM Ivan Drobyshevskyi ***@***.***> wrote:
~ $ ls -al /usr/lib/libboost_python*
lrwxrwxrwx 1 root root 27 Aug 27 09:36 /usr/lib/libboost_python27.so -> libboost_python27.so.1.69.0
-rwxr-xr-x 1 root root 267728 May 3 21:13 /usr/lib/libboost_python27.so.1.69.0
lrwxrwxrwx 1 root root 27 Aug 27 09:36 /usr/lib/libboost_python37.so -> libboost_python37.so.1.69.0
-rwxr-xr-x 1 root root 259536 May 3 21:13 /usr/lib/libboost_python37.so.1.69.0
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AAQIQF35Q3WXHYAWJOT27WTQGUG4XA5CNFSM4IQC3Y4KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5HN6MI#issuecomment-525262641>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAQIQFZA7YNG7W2SKGY6FQLQGUG4XANCNFSM4IQC3Y4A>
.
|
Merged
|
@vnd removed the C++ bits. I suppose pathfinding now takes 2µs instead of 2ns. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've tried to execute runme.sh and it fails with the same errors on Ubuntu 16.04 and Ubuntu 18.04 (if host system matters at all).
Note: I supposed that runme.sh is what is supposed to be executed, would be nice to add it to README if that's the case.
The text was updated successfully, but these errors were encountered: