Processing commands for cont...@bugs.debian.org:
> tags 467563 + wontfix
Bug #467563 [camlp5] Strict and transitional
Added tag(s) wontfix.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
467563: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467563
Debian Bug T
Stéphane Glondu writes:
I've pushed an updated camlp5 (6.04) package to the team's git, that
defaults to strict. I've also pushed a fix for ulex0.8, so that both
strict and transitional are supported. Matita then builds with no
changes in strict mode.
But then we don't need tran
Le 01/03/2012 15:50, Hendrik Tews a écrit :
>> ledit, geneweb and coq build without problems with strict camlp5.
>
>Did you test with the latest version (6.04)? Thanks a lot for your great
>work.
>
> No, I used the current camlp5 package (6.02.3-1), changed it to
> strict mode, instal
Concerning ulex0.8/matita, a perhaps saner alternative is to make matita
work with latest ulex and get rid of ulex0.8. I guess this means porting
it to camlp4... I've got no idea how much work is that, though.
I would leave this task to the matita authors. Is one of them
still on debian-
Le 01/03/2012 13:51, Hendrik Tews a écrit :
>There are other reverse build-dependencies: matita, ssreflect,
>geneweb... and maybe others (transitively). Someone has to test.
>
> ulex0.8 does not build with a strict camlp5:
>
> ocamlc -a -o pa_ulex.cma -pp 'camlp5o pa_extend.cmo q_MLas
Stéphane Glondu writes:
There are other reverse build-dependencies: matita, ssreflect,
geneweb... and maybe others (transitively). Someone has to test.
ulex0.8 does not build with a strict camlp5:
ocamlc -a -o pa_ulex.cma -pp 'camlp5o pa_extend.cmo q_MLast.cmo' -I +camlp5
cset.ml ule
I wrote:
is that the names of executables and libraries are hardcoded in
the makefiles and that these names are identical for strict and
transitional mode.
I told Daniel de Rauglaudre about the problem of compiling strict
and transitional camlp5 in one go. His answer is the new release
6
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
Hi,
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 in
the makefiles and that these names are ident
Le 28/02/2012 09:21, Hendrik Tews a écrit :
> I just noticed that camlp5 from Debian cannot compile hol-light,
> because the latter requires a strict camlp5 (with configure -strict).
> Has it ever be considered adding a Debian package for a strict
> camlp5?
See http://bugs.debian.org/cgi-bin/bugr
Hi,
I just noticed that camlp5 from Debian cannot compile hol-light,
because the latter requires a strict camlp5 (with configure -strict).
Has it ever be considered adding a Debian package for a strict
camlp5?
Bye,
Hendrik
--
To UNSUBSCRIBE, email to debian-ocaml-maint-requ...@lists.de
18 matches
Mail list logo
