Le 25/06/2012 17:39, Ed Schwartz a écrit :
> 3. As a developer, I should not need to incorporate Debian specific
> hacks into my project, such as using OCAML_COMPAT. If Debian needs to
> change or break the behavior of standard, open source tools, the
> Debian scripts should be changed to opt-in t
Hi Stéphane,
Thank you for your response. I like the idea behind your patch, but
unfortunately the side effects are very serious. Please consider how
this situation affects developers unaffiliated with Debian:
1. As a non-Debian developer, why should I not use -custom? It's not
deprecated, and
Le 23/06/2012 00:04, Ed Schwartz a écrit :
>>> Why do you use -custom if your executable works with plain ocamlrun?
>
> The Makefile that we use (https://bitbucket.org/mmottl/ocaml-makefile)
> uses -custom by default. Several libraries we link to also use
> -custom.
>
>> See /usr/share/doc/ocaml
Hi Stéphane,
On Fri, Jun 22, 2012 at 5:10 PM, Stéphane Glondu wrote:
>> Why do you use -custom if your executable works with plain ocamlrun?
The Makefile that we use (https://bitbucket.org/mmottl/ocaml-makefile)
uses -custom by default. Several libraries we link to also use
-custom.
> See /usr
Le 22/06/2012 22:46, Ed Schwartz a écrit :
> Using debian's ocamlc:
>
> ed@debian:~/ocaml-3.12.1$ ocamlc -custom test.ml -o test.out
> ed@debian:~/ocaml-3.12.1$ ocamlrun test.out
> Fatal error: the file test.out is not a bytecode executable file
Why do you use -custom if your executable works wit
Package: ocaml
Version: 3.12.1-3
Severity: normal
Using debian's ocamlc:
ed@debian:~/ocaml-3.12.1$ ocamlc -custom test.ml -o test.out
ed@debian:~/ocaml-3.12.1$ ocamlrun test.out
Fatal error: the file test.out is not a bytecode executable file
Using the official ocaml 3.12.1 source:
ed@debian:~
6 matches
Mail list logo
