Package Details: google-drive-ocamlfuse 0.7.4-1

Git Clone URL: https://aur.archlinux.org/google-drive-ocamlfuse.git (read-only)
Package Base: google-drive-ocamlfuse
Description: FUSE-based file system backed by Google Drive, written in OCaml
Upstream URL: https://astrada.github.io/google-drive-ocamlfuse/
Keywords: drive fuse google ocaml
Licenses: MIT
Submitter: mlq
Maintainer: pricechrispy
Last Packager: pricechrispy
Votes: 53
Popularity: 0.154404
First Submitted: 2013-10-14 21:44
Last Updated: 2019-06-23 01:50

Dependencies (7)

Required by (1)

Sources (1)

Pinned Comments

pricechrispy commented on 2018-01-27 00:47

Another error now exists with the camlidl package on a fresh build system.

In this case, the package is no longer creating a required file called "META". This prevents camlidl from showing up as installed, and prevents the package from building.

If you run "ocamlfind list | grep -i 'camlidl'", you should see the camlidl packages listed.

If not, manually create the META file: /usr/lib/ocaml/camlidl/META

description = "Stub generator"
version = "1.06"
directory = "^"
archive(byte) = "com.cma"
archive(native) = "com.cmxa"

pricechrispy commented on 2017-04-25 17:39

Before you flag this package out-of-date:

According to the official project page: https://astrada.github.io/google-drive-ocamlfuse/
Find latest release versions here: https://launchpad.net/~alessandro-strada/+archive/ubuntu/ppa

The latest releases are not all tagged versions on GitHub.
For the latest development versions on git, try: https://aur.archlinux.org/packages/google-drive-ocamlfuse-git

OLD official project page: http://gdfuse.forge.ocamlcore.org/
OLD release versions here: https://forge.ocamlcore.org/frs/?group_id=305

pricechrispy commented on 2016-11-17 10:46

While upgrading to the newer build, the same build error persists as reported in the comments.

When doing a fresh build, I manually created symlinks as root so that the build process finds them, as similarly suggested in the comments.

# ln -s /usr/lib/ocaml/com.cmxa /usr/lib/ocaml/camlidl/
# ln -s /usr/lib/ocaml/com.a /usr/lib/ocaml/camlidl/

After doing this, the directory '/usr/lib/ocaml/camlidl/' should have the following structure in a fresh environment:

$ ls -l /usr/lib/ocaml/camlidl/
total 4
lrwxrwxrwx 1 root root 20 Nov 17 02:23 com.a -> /usr/lib/ocaml/com.a
lrwxrwxrwx 1 root root 23 Nov 17 02:23 com.cmxa -> /usr/lib/ocaml/com.cmxa
-rw-r--r-- 1 root root 102 Nov 17 01:11 META

As suggested in the comments, this seems to be an issue with the camlidl package.

This should allow the package to build for now, until an automated PKGBUILD solution is found.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

somakd commented on 2019-07-10 18:59

I'm getting an error (using latest pamac on manjaro)

==> Validating source files with sha256sums... v0.7.4.tar.gz ... Passed

==> Removing existing $srcdir/ directory...

==> Extracting sources... -> Extracting v0.7.4.tar.gz with bsdtar

==> Starting build()...

File "none", line 1:

Error: Files /usr/lib/ocaml/cryptokit/cryptokit.cmxa

   and /usr/lib/ocaml/zarith/zarith.cmxa

   make inconsistent assumptions over interface Z

==> ERROR: A failure occurred in build(). Aborting...

jdegreef commented on 2019-06-29 12:15

@nixit : great, it works perfectly :)

I've used this command to completely remove ocaml* :

sudo pacman -Rdd $(pacman -Q | grep ocaml | cut -f 1 -d " ")

dd is used to not check dependencies. Use with caution if you have other programs using ocaml. You'll need to reinstall them as well.

nixit commented on 2019-06-27 22:33

I was able to get this working again by completely removing ocaml* from my system and performing a complete reinstall of google-drive-ocamlfuse, rebuilding the packages in the process.

this is now working like a champ for me. :)

jdegreef commented on 2019-05-27 22:22

Well, I have the feeling ocalm is a big mess. Each time you update google-drive-ocamlfuse it's broken. I've read all your comments but cannot figure out how to install google-drive-ocamlfuse without messing my system which is uptodate. It seems it needs stuff that are not in ARCH or AUR (yet ?). I don't want to add updated libraries that are not stock Arch/Aur and break something else. I think updates of packages should be build-able with what's in Aurch/Aur or wait that all what is necessary is available with yay/pacman/yaourt before being released. Don't take it bad, I like your work... when it works ;) In between I'll switch to rclone :-)

nixit commented on 2019-05-27 18:17

@pricechrispy,

I'm confused on how I apply this to get google-drive-ocamlfuse installed?

pricechrispy commented on 2019-03-17 23:29

I suppose it is possible to provide prebuilt packages on each version bump? There's about 20 in total. Not sure if this is desirable.

willemw commented on 2019-03-10 06:52

Have you tried google-drive-ocamlfuse-opam? It uses the OCaml package manager.

jdegreef commented on 2019-03-09 23:23

I agree with @gudwin this really a p.. in the a.. :-/ Anyway thanks for your work but a solution would be really welcome....

gudwin commented on 2019-03-08 23:10

Every time there is an update in this package, it brings me a strong headache in order to rebuild it through AUR in pamac. This happens because usually there is a new version of ocaml and all the .cmi files for the many sub-packages it depends on became obsolete, but are not automatically reconstructed, giving messages like this:

File "src/utils.ml", line 1: Error: /usr/lib/ocaml/Fuse/Fuse.cmi is not a compiled interface for this version of OCaml. It seems to be for an older version of OCaml.

Then I need to enter into a tedious process of going dependency by dependency and asking it to be rebuild in order to avoid such errors. In some cases, there are dependencies on dependencies that repeats the same problem. Last time it took me more than 4 hours doing it package by package by hand, until the new version is able to be compiled. Isn't there a way of avoiding this obnoxious procedure ?

sucre commented on 2019-01-15 19:25

tambeta updated ocaml-sqlite3 to 4.4.1-1, for now this package can be build again.