Package Details: ocaml-zarith 1.8-2

Git Clone URL: https://aur.archlinux.org/ocaml-zarith.git (read-only)
Package Base: ocaml-zarith
Description: Implements arithmetic and logical operations over arbitrary-precision integers and rational numbers
Upstream URL: https://github.com/ocaml/Zarith
Licenses: GPL2
Provides: zarith
Submitter: oriba
Maintainer: oriba
Last Packager: oriba
Votes: 30
Popularity: 0.076336
First Submitted: 2018-04-30 21:40
Last Updated: 2019-05-26 13:55

Dependencies (3)

Required by (11)

Sources (1)

Latest Comments

1 2 3 Next › Last »

oriba commented on 2019-05-26 13:56

@Samsagax: thanks for your exploration of the problem; I changed the PKGBUILD accordingly.

gee commented on 2019-05-25 23:50

Yup -j1 worked thanks!

Samsagax commented on 2019-05-25 20:34

@oriba, I had the same issue as @gee described. The solution I found was to use "-j1" flag in the make call on build() function. Seems like the Makefile doesn't handle multiple threads well. Maybe a wrongly defined Makefile.am somewhere.

oriba commented on 2019-05-25 11:39

@gee: I tried to reproduce your problem (removed all pkg/src files which I forgot to do, when changing the PKGBUILD). But with a clean directory, containing the PKGBUILD and no previously compiled files, the package could be built. Possibly you may also clean up your dirctory, starting only with the PKGBUILD. IMO it should work.

gee commented on 2019-05-25 09:51

Since the update the build fails for me:

make: No rule to make target 'z.cmti', needed by 'all'. Stop. make: Waiting for unfinished jobs...

I don't know anything about caml so not sure how to fix it.

Kunda commented on 2018-05-23 13:30

@hriad thanks, your solution worked.

hriad commented on 2018-05-15 08:13

Edit: If you have the same issue, simply do:

pacman -Rdd zarith

Then build again.

error: failed to commit transaction (conflicting files)

ocaml-zarith: /usr/lib/ocaml/zarith/META exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/big_int_Z.cmi exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/big_int_Z.cmx exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/big_int_Z.mli exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/dllzarith.so exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/libzarith.a exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/q.cmi exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/q.cmx exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/q.mli exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/z.cmi exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/z.cmx exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/z.mli exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/zarith.a exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/zarith.cma exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/zarith.cmxa exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/zarith.cmxs exists in filesystem

ocaml-zarith: /usr/lib/ocaml/zarith/zarith.h exists in filesystem

Errors occurred, no packages were upgraded.

oriba commented on 2018-04-30 21:50

@emersion: 'ocaml-zarith' created, merge-request-into ocaml-zarith sent. in zarith the request is mentioned, in ocaml-zarith not, even though I got email from AUR about that. Any ideas how to preoceed from now on?

emersion commented on 2018-04-16 12:59

It seems dllzarith.so is not placed at the correct location:

Fatal error: cannot load shared library dllzarith Reason: dllzarith.so: cannot open shared object file: No such file or directory

I had to run export CAML_LD_LIBRARY_PATH=/usr/lib/ocaml/zarith to be able to execute my program. Maybe dllzarith.so should be installed in /usr/lib directly?

emersion commented on 2018-04-16 10:59

You can submit a new package with the new name, click "Submit Request" on the old one (link on the right), and select "Merge". You can add provides=('zarith') to the new package to prevent other packages from being broken. You can probably keep the whole Git history of the package by just adding and pushing to the new remote (with a commit updating the package name).