Package Details: google-drive-ocamlfuse 0.7.1-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.899879
First Submitted: 2013-10-14 21:44
Last Updated: 2019-03-04 06:36

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 »

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.

woodyl commented on 2018-12-22 22:03

I'm having the same problem as @DroidFreak32 and @sfranchi. I can't build this package because it depends on ocaml-sqlite3. I see that ocaml-sqlite3 is now out of date and the maintainer comments that he doesn't have time to fix it and it's now orphaned. Does anybody have a suggestion for a a work-around?

sfranchi commented on 2018-12-20 14:03

I'm having the same problem as @DroidFreak32, package does not build because (I think) of older versions of ocaml packages.

DroidFreak32 commented on 2018-12-12 10:14

Im having errors compiling this:

==> Starting build()...
    ocamlopt src/.google_drive_ocamlfuse.objs/dbCache.{cmx,o} (exit 2)
(cd _build/default && /usr/sbin/ocamlopt.opt -w -40 -w -3-27-32-58 -g -I src/.google_drive_ocamlfuse.objs -I src/.google_drive_ocamlfuse.objs/.private -I /usr/lib/ocaml/Fuse -I /usr/lib/ocaml/biniou -I /usr/lib/ocaml/bytes -I /usr/lib/ocaml/cryptokit -I /usr/lib/ocaml/curl -I /usr/lib/ocaml/easy-format -I /usr/lib/ocaml/extlib -I /usr/lib/ocaml/gapi-ocaml -I /usr/lib/ocaml/netstring -I /usr/lib/ocaml/netsys -I /usr/lib/ocaml/sqlite3 -I /usr/lib/ocaml/threads -I /usr/lib/ocaml/yojson -I /usr/lib/ocaml/zarith -intf-suffix .ml -no-alias-deps -o src/.google_drive_ocamlfuse.objs/dbCache.cmx -c -impl src/dbCache.ml)
File "src/dbCache.ml", line 1:
Error: /usr/lib/ocaml/sqlite3/sqlite3.cmi
is not a compiled interface for this version of OCaml.
It seems to be for an older version of OCaml.
==> ERROR: A failure occurred in build().
    Aborting...
Error making: google-drive-ocamlfuse

ValHue commented on 2018-09-24 16:45

Error: Library "zarith" not found.

-> required by library "cryptokit" in /usr/lib/ocaml/cryptokit

Hint: try: dune external-lib-deps --missing @install

sfranchi commented on 2018-09-05 14:45

Just in case someone is encountering the same problem I had with building the ocamlnet dependency (see my previous comment): it turned out that building most of its dependencies individually (ocaml base, ocam-pcre, etc.) before trying to build ocamlnet solved the problem for me.