OCaml »binaries« don't like being stripped… If you however decide stripping them (what can happen with the appropriate build-options), you end up with something like #v+ aw@rerun:~> wyrd No bytecode file specified. aw@rerun:~> #v- probably missing important appointments and no-one to blame. Reproducible: Always Steps to Reproduce: 1. type ›echo "*/* BUILD_OPTIONS: strip" > /etc/paludis/use.conf‹ or similar 2. run ›paludis -i app-misc/wyrd‹ or so 3. run ›wyrd‹ and stand back (beware: strange things™ will happen) Actual Results: »Oh, my calendar app just vanished to some kind of OCaml interpreter…« Expected Results: A shiny and lightweight calendar app. A »RESTRICT="strip"« in the ebuild should fix this issue.
(In reply to comment #0) > OCaml »binaries« don't like being stripped… Is this something the ml team can confirm? > #v+ > aw@rerun:~> wyrd > No bytecode file specified. > aw@rerun:~> > #v- My wyrd works. Which ocaml version do you use? > A »RESTRICT="strip"« in the ebuild should fix this issue. Should? Did you test it?
(In reply to comment #1) > (In reply to comment #0) > > OCaml »binaries« don't like being stripped… > > Is this something the ml team can confirm? yes; ocamlc -custom built binaries (usually when native code support is disabled) do not like being stripped see: alexis@portable /tmp $ ocamlc -custom foo.ml alexis@portable /tmp $ ./a.out hello world alexis@portable /tmp $ strip a.out alexis@portable /tmp $ ./a.out No bytecode file specified. I recommend using STRIP_MASK though and not using the (obviously) suboptimal RESTRICT=strip; grep STRIP_MASK in dev-ml cat. for examples.
So i've added STRIP_MASK="/usr/bin/wyrd". Thanks.
