@justinkb: Exactly. I got same error here. Recompiling the AUR package solve the problem.
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.002229 |
First Submitted: | 2012-04-29 15:20 (UTC) |
Last Updated: | 2023-01-23 14:25 (UTC) |
Dependencies (13)
- 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)
- git (git-gitAUR, git-glAUR) (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)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 Next › Last »
semeion commented on 2015-10-23 22:20 (UTC) (edited on 2015-10-23 22:20 (UTC) by semeion)
justinkb commented on 2015-10-23 22:14 (UTC) (edited on 2015-10-23 22:15 (UTC) by justinkb)
Maybe do a revbump since boost-libs pkg update from [extra] from a week or two ago means rebuilding this package is necessary
(grive: error while loading shared libraries: libboost_program_options.so.1.58.0: cannot open shared object file: No such file or directory)
edh commented on 2015-06-28 11:39 (UTC)
The concerning bug has been fixed upstream and I can confirm that it is working.
edh commented on 2015-06-26 14:48 (UTC)
There seems to be a problem concerning the build of some test units. I reported the error upstream!
The good news is that it only occurs when the package "cppunit" is installed: Removing the package, removes the error.
This definitely is not a permanent solution but for now "cppunit" is considered a conflicting package.
@jorges Thanks for your comment!
jorges commented on 2015-06-26 13:29 (UTC)
Build failing here, see below for excerpt
Linking CXX executable btest
[ 81%] Built target btest
Scanning dependencies of target unittest
[ 83%] Building CXX object libgrive/CMakeFiles/unittest.dir/test/UnitTest.cc.o
[ 85%] Building CXX object libgrive/CMakeFiles/unittest.dir/test/drive/EntryTest.cc.o
/var/abs/local/yaourt/tmp/yaourt-tmp-jscandal/aur-grive-git/src/grive-git/libgrive/test/drive/EntryTest.cc:24:26: fatal error: drive/Entry.hh: No such file or directory
compilation terminated.
libgrive/CMakeFiles/unittest.dir/build.make:77: recipe for target 'libgrive/CMakeFiles/unittest.dir/test/drive/EntryTest.cc.o' failed
make[2]: *** [libgrive/CMakeFiles/unittest.dir/test/drive/EntryTest.cc.o] Error 1
CMakeFiles/Makefile2:149: recipe for target 'libgrive/CMakeFiles/unittest.dir/all' failed
make[1]: *** [libgrive/CMakeFiles/unittest.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build grive-git.
edh commented on 2015-06-01 13:37 (UTC)
I just obtained maintainership and will update this package from now on.
The PKGBUILD now uses a different source. To be precise it uses a fork of the original grive programm which was also introced in the grive package. This does not only fixes several bugs, e.g. the missing implementation of the new REST API, but moreover promises a much cleaner and better implementation of the new APIs.
tmoore commented on 2015-02-01 22:35 (UTC)
Updated and working
gosella commented on 2014-12-16 16:06 (UTC)
Please, update the patch file "json-c.patch" with this:
http://linkode.org/GolkssnklWcMlrBExxUr17
The first part of the patch is no longer relevant (and is causing trouble appling it, as reported by @frabjous).
Thanks!
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.