Accepted:
libapache2-mod-ocamlnet_3.5.1-1_amd64.deb
to main/o/ocamlnet/libapache2-mod-ocamlnet_3.5.1-1_amd64.deb
libnethttpd-ocaml-dev_3.5.1-1_amd64.deb
to main/o/ocamlnet/libnethttpd-ocaml-dev_3.5.1-1_amd64.deb
libocamlnet-gtk2-ocaml-dev_3.5.1-1_amd64.deb
to main/o/ocamlnet/libocamlnet-gt
ocamlnet_3.5.1-1_amd64.changes uploaded successfully to localhost
along with the files:
ocamlnet_3.5.1-1.dsc
ocamlnet_3.5.1.orig.tar.gz
ocamlnet_3.5.1-1.debian.tar.gz
libocamlnet-ocaml-dev_3.5.1-1_amd64.deb
libocamlnet-ocaml_3.5.1-1_amd64.deb
libocamlnet-ocaml-bin_3.5.1-1_amd64.deb
li
Le 29/02/2012 18:04, Pino Toscano a écrit :
> the asmcomp tests fail to link on hurd-i386, because the "call_gen_code"
> symbol is missing.
> The problem is that in testsuite/tests/asmcomp/i386.S the #define's that
> are enabled for hurd are wrong. Using the linux_elf ones (just also it
> is done i
Package: ocaml
Version: 3.12.2~~dev6+12112-3
Severity: minor
Tags: patch
User: debian-h...@lists.debian.org
Usertags: hurd
Hi,
the asmcomp tests fail to link on hurd-i386, because the "call_gen_code"
symbol is missing.
The problem is that in testsuite/tests/asmcomp/i386.S the #define's that
are e
Le 29/02/2012 11:23, Pierre Boutillier a écrit :
> ssreflect and aactactics are OK
>
> ulex does NOT depend anymore on camlp5 since v1.0:
> CHANGES:
> 1.0
> * Update to the new Camlp4 and to ocamlbuild (release for OCaml 3.10
>only), by Nicolas Pouillard.
Err... we were talking about
ssreflect and aactactics are OK
ulex does NOT depend anymore on camlp5 since v1.0:
CHANGES:
1.0
* Update to the new Camlp4 and to ocamlbuild (release for OCaml
3.10
only), by Nicolas Pouillard.
geneweb has the same uptream author than camlp5 and works in strict.
Le 29 févr. 12
Pierre Boutillier writes:
Why do we keep a camlp5 in transitionnal mode ?
I assumed somebody needs transitional mode. Supporting only
strict mode is of course much simpler.
For packages, Coq and ledit support strict mode. The only remaining
question is about ulex.
How about ss
Le 29/02/2012 10:03, Pierre Boutillier a écrit :
> I'm sorry but I do not see an answer to that question in the thread: Why
> do we keep a camlp5 in transitionnal mode ?
This is a good question that I've been thinking about.
> For packages, Coq and ledit support strict mode. The only remaining
>
Le 29/02/2012 10:01, Hendrik Tews a écrit :
>What about the library?
>
> You mean camlp5.cma and its variants? They differ between strict
> and transitional modes and their name is hardcoded in the
> Makefile as well. There might be some objects which are
> identical, eg. /usr/lib/ocaml/camlp5
Hi,
I'm sorry but I do not see an answer to that question in the thread:
Why do we keep a camlp5 in transitionnal mode ?
For packages, Coq and ledit support strict mode. The only remaining
question is about ulex.
Pierre
Le 28 févr. 12 à 23:16, Hendrik Tews a écrit :
Hi,
I looked at how
Stéphane Glondu writes:
What about the library?
You mean camlp5.cma and its variants? They differ between strict
and transitional modes and their name is hardcoded in the
Makefile as well. There might be some objects which are
identical, eg. /usr/lib/ocaml/camlp5/diff.cmx but finding that
out
Le 28/02/2012 23:16, Hendrik Tews a écrit :
> I looked at how camlp5 is compiled and I believe to build
> transitional _and_ strict camlp5 executables and libraries from
> one source package will require quite a bit of work. The reason
> is that the names of executables and libraries are hardcoded
12 matches
Mail list logo
