with a freshly installed grive-git I am getting: grive: error while loading shared libraries: libboost_filesystem.so.1.71.0: cannot open shared object file: No such file or directory
Search Criteria
Package Details: grive-git 557.648ff8e-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/grive-git.git (read-only, click to copy) |
|---|---|
| Package Base: | grive-git |
| Description: | An open source Linux client for Google Drive with support for the new Drive REST API and partial sync |
| Upstream URL: | https://github.com/vitalif/grive2 |
| Keywords: | drive git Google share sync |
| Licenses: | GPL2 |
| Conflicts: | grive |
| Provides: | grive |
| Submitter: | ilpianista |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 78 |
| Popularity: | 0.000000 |
| First Submitted: | 2012-04-29 15:20 (UTC) |
| Last Updated: | 2023-01-23 14:25 (UTC) |
Dependencies (13)
- boost-libs
- curl (curl-gitAUR, curl-c-aresAUR)
- expat (expat-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- json-c (json-c-gitAUR)
- libgcrypt
- yajl (yajl-gitAUR)
- boost (boost-gitAUR) (make)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- binutils (optional) – backtrace and libiberty
- cppunit (optional) – unit tests
- inotify-tools (inotify-tools-gitAUR) (optional) – scheduled syncs and syncs on file change events
Required by (0)
Sources (1)
tjc commented on 2020-02-03 22:31 (UTC)
edh commented on 2020-01-29 19:59 (UTC)
@vlas
Sure, that is why I implicitly recommended you to check how to get to the error in a reproducable way or depending on preliminary tests on your side, file a bug report. It is not required to understand every last bit of C++ code in grive to do either of this. To start with, I would check that you boost package is up-to-date and make sure that the error also occurs if you manually try to build grive.
P.s. please be a little bit more considered of what to expect from the comment section of a package. This is not a helpdesk after all.
vlas commented on 2020-01-29 19:45 (UTC)
@edh, I'm sorry, but I'm not a coder and I have no idea what caused this error. I expect getting advice here.
edh commented on 2020-01-29 19:07 (UTC)
@vlas I can not reproduce your error. Please file a bug upstream if you think that it is actually due to something in the code of grive.
vlas commented on 2020-01-29 16:08 (UTC)
501.a3cce71-1 build error: https://pastebin.com/raw/zfeE88Rt
vlas commented on 2019-10-20 22:08 (UTC) (edited on 2019-10-20 22:12 (UTC) by vlas)
@dikei: It works, thanks! Just changed cmake -DCMAKE_BUILD_TYPE=Release \ to cmake -DBoost_DIR=/usr/lib/cmake/Boost-1.71.0 \
Mad. I never would have thought of it. Am I the only one with this problem?..
dikei commented on 2019-10-19 08:21 (UTC) (edited on 2020-03-22 08:47 (UTC) by dikei)
@vlas: Seem like a new bug in Boost-1.71 https://gitlab.kitware.com/cmake/cmake/issues/19841
Workaround by manually setting -DBoost_DIR=/usr/lib/cmake/Boost-<boost_version>/ in the PKGBUILD file
vlas commented on 2019-10-08 19:20 (UTC) (edited on 2019-10-08 19:21 (UTC) by vlas)
493.f039e38-2 build error: https://pastebin.com/V0yrr9uY
the_isz commented on 2019-03-03 16:51 (UTC)
@edh: Sorry, somehow I completely missed your response D:
You are correct, it is an optional dependency because you only need it if you want to use "grive-changes" to automatically upload changes to your google drive folder.
Tharbad commented on 2019-02-02 11:55 (UTC)
What happened to grive-tools package?
Pinned Comments
edh commented on 2022-09-20 20:45 (UTC)
This package has a bad record of not building. However, I am reluctant to patch a git-package because any changes would most likely break with any new upstream commit. Please try to get the build fixed upstream or switch to the grive package.