I'm attempting to use grive2 and I am getting some sort of boost error so I am wondering if grive2 suffers from the same thing others here are complaining about. I'm running boost 1.57.0-2, what do I have to do to get grive working?
Search Criteria
Package Details: grive 0.5.3-3
Package Actions
| Git Clone URL: | https://aur.archlinux.org/grive.git (read-only, click to copy) |
|---|---|
| Package Base: | grive |
| 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 Google grive2 sync vitalif |
| Licenses: | GPL2 |
| Submitter: | mrbit |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 282 |
| Popularity: | 0.120546 |
| First Submitted: | 2012-04-29 22:26 (UTC) |
| Last Updated: | 2024-09-14 09:14 (UTC) |
Dependencies (12)
- boost-libs
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- expat (expat-gitAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-snapshotAUR)
- json-c (json-c-gitAUR)
- libgcrypt
- yajl (yajl-gitAUR)
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR) (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 (4)
ubuntuaddicted commented on 2014-12-08 04:59 (UTC)
semeion commented on 2014-11-26 20:52 (UTC)
Thanks for this package!
nullptr_t commented on 2014-11-11 01:48 (UTC)
Since boost 1.57.0, there seems to be no nessecarity to link the libs anymore (see below)
$ /u/lib> ls -l /usr/lib/libboost_filesystem.so
…system.so …system.so.1.56 …system.so.1.57.0
$ /u/lib> ls -l /usr/lib/libboost_filesystem.so.1.56
lrwxrwxrwx 1 root root 31 Sep 9 21:32 /usr/lib/libboost_filesystem.so.1.56 -> /usr/lib/libboost_filesystem.so*
$ /u/lib> ls -l /usr/lib/libboost_filesystem.so.1.57.0
-rwxr-xr-x 1 root root 101568 Nov 6 08:46 /usr/lib/libboost_filesystem.so.1.57.0*
$ /u/lib> ls -l /usr/lib/libbost_program_options.so.1.56.0
lrwxrwxrwx 1 root root 36 Sep 9 21:32 /usr/lib/libbost_program_options.so.1.56.0 -> /usr/lib/libboost_program_options.so*
Please remove/uncomment the corresponding line
ln -sf "/usr/lib/libboost_program_options.so" "${pkgdir}/usr/lib/libbost_program_options.so.1.57.0" || return 1
in your PKGBUILD to prevent file conflicts during upgrading via pacman. The following line can stay ;)
monojp commented on 2014-11-10 15:30 (UTC)
boost has been updated and the lib needs to be changed once again
markusk commented on 2014-10-15 20:22 (UTC)
"Boost" problem : you have to recompile all aur pakages that depend on boost
mrbit commented on 2014-10-11 15:08 (UTC)
Hi, yedibela
why to downgrade boost to 1.55?
yedibela commented on 2014-10-11 14:18 (UTC)
hi, can someone give me helping hand in order to make grive run again. Do i need to downgrade my boost to 1.55?
monojp commented on 2014-09-12 11:40 (UTC)
hi, the 3 i686 sed fixes (casting to boost::uint64_t in State.cc) also apply for the armv6h architecture (archlinuxarm on raspberry pi)
mrbit commented on 2014-09-09 16:12 (UTC)
Thanks, whahn1983, updated link for boost 1.56
whahn1983 commented on 2014-09-09 15:44 (UTC)
grive: error while loading shared libraries: libboost_program_options.so.1.55.0: cannot open shared object file: No such file or directory
Looks like boost was updated to 1.56 a few days ago.
Pinned Comments
edh commented on 2023-10-11 23:00 (UTC)
If you encounter errors similar to
error [...] loading shared libraries, you most likely need to rebuilt the grive package. Usually no further action is needed except for forcing a rebuilt.The error is due to grive having been built against an older version of the library mentioned in the error message. The library has likely since been updated by
pacmanand grive need to be made aware of this by rebuilding it.