Package: cduce
Version: 0.4.0-4+b1
Severity: important
I do not know exactly if the bug come from cduce or libpcre or
something else but the fact is that you cannot compile something which
needs both pcre.cma and cduce.cma both .
For example :
$ cduce --compile cduceTest.cd
$ ocamlc -c -I /usr/lib/ocaml/3.09.2/cduce -pp "cduce --mlstub" -impl
cduceTest.cdo
$ ocamlc -I /usr/lib/ocaml/3.09.2/cduce/ -I /usr/lib/ocaml/3.09.2/pcre
pcre.cma cduce_lib.cma cduceTest.cmo
Files /usr/lib/ocaml/3.09.2/cduce/cduce_lib.cma(Cduce_lib)
and /usr/lib/ocaml/3.09.2/pcre/pcre.cma(Pcre)
make inconsistent assumptions over interface Pcre
with in cduceTest.cd :
type Xml_int = [ '0'--'9'+ ] ;;
I do not know anything about cduce but it seems there is a problem. Is
cduce in etch compiled with an other version of pcre than the etch one ?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-k7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Versions of packages cduce depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libcomerr2 1.39-1 common error description library
ii libcurl-ocaml-dev 0.2.1-7 ocaml libcurl bindings
ii libcurl3-gnutls 7.15.5-1 Multi-protocol file transfer libra
ii libexpat-ocaml-dev 0.9.1+debian1-1 ocaml expat bindings
ii libexpat1 1.95.8-3.3 XML parsing C library - runtime li
ii libgnutls13 1.4.4-1 the GNU TLS library - runtime libr
ii libidn11 0.6.5-1 GNU libidn library, implementation
ii libkrb53 1.4.4-1 MIT Kerberos runtime libraries
ii libocamlnet-ocaml-dev 1.1-12 OCaml application-level Internet p
ii libpcre3 6.4-2 Perl 5 Compatible Regular Expressi
ii ocaml-nox [ocaml-nox-3.0 3.09.2-6 ML language implementation with a
ii ocaml-ulex 0.8-5 OCaml lexer generator with Unicode
ii zlib1g 1:1.2.3-13 compression library - runtime
cduce recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
