Search Criteria
Package Details: ocaml-ppx_here 1:0.17.0-3
Package Actions
| Git Clone URL: | https://aur.archlinux.org/ocaml-ppx_here.git (read-only, click to copy) |
|---|---|
| Package Base: | ocaml-ppx_here |
| Description: | Expands [%here] into its location |
| Upstream URL: | https://github.com/janestreet/ppx_here |
| Keywords: | library line number ocaml position replace rewrite rewriter source value |
| Licenses: | MIT |
| Submitter: | J5lx |
| Maintainer: | None |
| Last Packager: | dpeukert |
| Votes: | 1 |
| Popularity: | 0.000000 |
| First Submitted: | 2016-02-06 02:10 (UTC) |
| Last Updated: | 2025-01-22 08:14 (UTC) |
Dependencies (5)
- ocaml (ocaml-gitAUR)
- ocaml-base (ocaml-base-gitAUR)
- ocaml-ppxlibAUR
- zstd (zstd-gitAUR, zstd-staticAUR)
- dune (make)
Latest Comments
dpeukert commented on 2024-05-21 09:18 (UTC)
@frankenstein20: This is caused by a gcc update. Until the rebuild in the main repos is complete (see here for progress), you can rebuild and install ocaml-base manually.
frankenstein20 commented on 2024-05-17 17:41 (UTC)
Do you know how to fix this
Thank you
dpeukert commented on 2023-10-10 10:55 (UTC)
@dreieck: Hi, yes, that's the minimum version of ocaml-base required by upstream and sadly the version of ocaml-base in the repos has been out-of-date for quite some time. Just updating to the new version in the ocaml-base PKGBUILD from the repos works.
dreieck commented on 2023-10-10 10:41 (UTC)
Does it really need
ocaml-base>=0.16.0?ocaml-basein the Arch repository is currently at version 0.15.1.Regards!
dpeukert commented on 2022-08-11 08:54 (UTC)
After the 4.14.0 rebuild, this package now builds again.
dpeukert commented on 2022-07-16 21:22 (UTC)
@VannTen: Sorry about the delay, this seems to be caused by ocaml-base in the main repos not being rebuilt. I've filed a bug (https://bugs.archlinux.org/task/75349), but in the meantime, you can rebuild ocaml-base manually and this package should build afterwards.
VannTen commented on 2022-06-28 15:28 (UTC)
the build seem to be broken (in a clean chroot anyway)
Not sure if it's an upstream issue ?