On Wed, Oct 03, 2018 at 12:10:49PM +0200, Sébastien Hinderer wrote: > Coming to the directory I was talking about, it is currently called > "target-bindir" and is used to define where the bytecode interpreter, > ocamlrun, will reside on the target system. This is something the > compiler running on the host needs to know because it adds a line like > #!/path/to/ocamlrun/on/target/system > at the beginning of the bytecode executables it produces, so that they > can then be run as regular executable programs on the target. Does all > this make sense? Perhaps autoconf has a different way of handling such > settings? Could this be a subdirectory of one of the standard installation directories? https://www.gnu.org/prep/standards/html_node/Directory-Variables.html For example, your "target-bindir" could be set from libexecdir, and be /usr/local/libexec/ocamalrun by default. _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
