Search Criteria
Package Details: cppo 1.6.9-2
Package Actions
| Git Clone URL: | https://aur.archlinux.org/cppo.git (read-only, click to copy) |
|---|---|
| Package Base: | cppo |
| Description: | C-style preprocessor for OCaml |
| Upstream URL: | https://github.com/ocaml-community/cppo |
| Keywords: | ocaml |
| Licenses: | BSD |
| Submitter: | J5lx |
| Maintainer: | hv15 |
| Last Packager: | hv15 |
| Votes: | 6 |
| Popularity: | 0.002900 |
| First Submitted: | 2019-09-04 10:17 (UTC) |
| Last Updated: | 2022-05-21 10:03 (UTC) |
Dependencies (4)
- glibc (glibc-gitAUR, glibc-linux4AUR, glibc-eacAUR)
- dune (make)
- ocamlbuild (make)
- ocamlbuild (optional) – ocamlbuild plugin
Required by (12)
- gapi-ocaml
- ocaml-cil-git (make)
- ocaml-extlib (make)
- ocaml-lwt (make)
- ocaml-mdx (make)
- ocaml-ocplib-endian (make)
- ocaml-ppx_deriving (make)
- ocaml-ppx_deriving-git (make)
- ocaml-ppx_tools (make)
- ocaml-utop
- ocaml-yojson (make)
- ocaml-yojson-git (make)
Latest Comments
« First ‹ Previous 1 2
J5lx commented on 2019-12-04 18:15 (UTC)
I’m extremely sorry about the lack of communication, I totally let your comments get buried beneath other stuff.
The problem is most likely that you have OCaml software installed locally through opam. Please check if the directory ~/.opam exists on your system – if it does, rename or remove it and retry building the package.
Alternatively, try building in a clean chroot like algorythmis has done. In my experience this avoids many build failures that can be caused by conflicting system configuration, especially for OCaml packages. The error posted by algorythmis (“target not found: cppo”) only means that this package is not part of any of the binary repos (core, extra, community etc.), the actual build should work just fine right now.
Lastly, if I (or another maintainer) fail to respond to comments, try sending an email (the address can usually be found in the PKGBUILD or on the profile page) instead of flagging the package out-of-date. Personally I have my mail filtering rules set up in a way that gives “hand-crafted” emails higher visibility than any notifications, so when I’m busy I’m much more likely to see those.
Again, I’m super sorry that I didn’t respond earlier, I really messed up there!
algorythmis commented on 2019-10-30 18:34 (UTC) (edited on 2019-10-30 18:51 (UTC) by algorythmis)
Same error than @skalkoto @Mr.E @Tyilo @alfa8my
Either inserting
mkdir "${srcdir}/usr/doc"before themvcommand, or removing the latter make the build work, but then thecppocommand doesn't seem to exist.Attempting to build in a clean chroot with extra-x86_64-build instead returns this:
skalkoto commented on 2019-10-05 18:20 (UTC) (edited on 2019-10-05 18:38 (UTC) by skalkoto)
I get the same error:
Mr.E commented on 2019-10-03 20:10 (UTC)
I'm having the same problem. This is the error message I get when trying to compile it using
makepkg -siJ5lx commented on 2019-09-12 15:16 (UTC)
@milk The problem is that you have a per-user copy of ocamlbuild installed on your system which shadows the system-wide version. Please build this package in a clean chroot, or at least remove/rename ~/.opam when building this package. In general, not building packages in a clean chroot on a system which also has stuff installed through opam is practically a recipe for problems.
@Tyilo I can only repeat what I told alfa8my: Since I can’t reproduce your issue myself, I need more information to help you. For starters, the complete build output would be very useful. Alternatively, try building the package in a clean chroot (there is a reason I keep saying this – it really does help in many cases).
Tyilo commented on 2019-09-12 14:50 (UTC)
I have the same problem as @alfa8my
milkii commented on 2019-09-10 15:28 (UTC)
Getting this atm:
J5lx commented on 2019-09-10 02:36 (UTC)
I can’t reproduce that, the package compiles just fine for me. Can you provide a bit more context? Sometimes local configuration can interfere with the build, in that case building in a clean chroot usually helps.
alfa8my commented on 2019-09-10 01:14 (UTC)
It does not compile, because it cannot evaluate "…/cppo/pkg/cppo/usr/doc"; says there is no such file.
« First ‹ Previous 1 2