Got an error, but I feel this should be solved by version bump ors. So I flagged the package, don if it its the right thing though.
Solution:
https://browse-tutorials.com/snippet/grive-error-while-loading-shared-libraries-libboostprogramoptionsso1620-cannot-open-shared
Search Criteria
Package Details: grive 0.5.3-2
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: | 284 |
| Popularity: | 0.000750 |
| First Submitted: | 2012-04-29 22:26 (UTC) |
| Last Updated: | 2023-01-23 14:24 (UTC) |
Dependencies (12)
- boost-libs (boost-libs-gitAUR)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-c-aresAUR, curl-gitAUR)
- expat (expat-gitAUR)
- gcc-libs (gccrs-libs-gitAUR, gcc11-libsAUR, gcc-libs-gitAUR, 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 (3)
ram4nd commented on 2017-01-16 09:56 (UTC) (edited on 2017-01-16 09:57 (UTC) by ram4nd)
3539037O3Ul2kNk1 commented on 2016-11-01 01:37 (UTC)
Worked like a charm. Thanks again @edh.
edh commented on 2016-10-31 09:25 (UTC)
@s1lentechoes
I increased the pkgrel to force a rebuild.
3539037O3Ul2kNk1 commented on 2016-10-31 02:34 (UTC)
@edh It happened again, but this time with libboost_program_options -
grive: error while loading shared libraries: libboost_program_options.so.1.61.0: cannot open shared object file: No such file or directory
edh commented on 2016-09-12 22:12 (UTC)
@iamroot
Thanks for debugging. However I think this is a bug in grive itself and not directly related to this PKGBUILD. The build script follows the installation instructions provided upstream.
Be sure to file a bug at the project page [1].
[1] https://github.com/vitalif/grive2
iamroot commented on 2016-09-12 16:45 (UTC)
Segmentation fault bug, added the GDB backtrace below, thanks for the help.
10436 segmentation fault (core dumped)
Running with GDB ->>
Starting program: /usr/bin/grive
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7ffff0d9a700 (LWP 16495)]
[Thread 0x7ffff0d9a700 (LWP 16495) exited]
Reading local directories
Reading remote server file list
[New Thread 0x7ffff0d9a700 (LWP 16532)]
[Thread 0x7ffff0d9a700 (LWP 16532) exited]
Thread 1 "grive" received signal SIGSEGV, Segmentation fault.
0x00000000004ab65b in gr::Resource::MD5[abi:cxx11]() const ()
Thanks again!
3539037O3Ul2kNk1 commented on 2016-09-12 03:08 (UTC)
Okay, thanks. Yeah, reinstalling the package fixed it. Many thanks.
edh commented on 2016-09-11 22:32 (UTC)
@s1lentechoes
This isn't really grive's fault but probably due to the boost-lib update. Either way I increased the pkgrel to force a rebuild.
3539037O3Ul2kNk1 commented on 2016-09-11 11:38 (UTC)
Broke after an update yesterday. Error -
grive: error while loading shared libraries: libboost_program_options.so.1.60.0: cannot open shared object file: No such file or directory
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.