We would appreciate the help of any user who wants to test this version and report any problem encountered (as usual, through the BTS: < http://caml.inria.fr/mantis/main_page.php >).
It will become a full release in one or two weeks unless some serious bug is reported in the meantime.
Damien Doligez [Wednesday 30 August 2006] : > > Hello, > > We have a release candidate for 3.09.3. It is available from the CVS > repository < http://camlcvs.inria.fr/cvsserver-eng.html > under the > tag "ocaml3093rc1".
I get this: ,---- | $ cvs up -r ocaml3093rc1 | cvs [update aborted]: no such tag ocaml3093rc1 `---- -- Olivier
On Wed, 2006-08-30 at 14:18 +0200, Olivier Andrieu wrote: > Damien Doligez [Wednesday 30 August 2006] :
> > Hello,
> > We have a release candidate for 3.09.3. It is available from the CVS > > repository < http://camlcvs.inria.fr/cvsserver-eng.html > under the > > tag "ocaml3093rc1".
> I get this: > ,---- > | $ cvs up -r ocaml3093rc1 > | cvs [update aborted]: no such tag ocaml3093rc1 > `----
skaller [Wednesday 30 August 2006] : > > On Wed, 2006-08-30 at 14:18 +0200, Olivier Andrieu wrote: > > Damien Doligez [Wednesday 30 August 2006] : > > > > > > Hello, > > > > > > We have a release candidate for 3.09.3. It is available from the CVS > > > repository < http://camlcvs.inria.fr/cvsserver-eng.html > under the > > > tag "ocaml3093rc1". > > > > I get this: > > ,---- > > | $ cvs up -r ocaml3093rc1 > > | cvs [update aborted]: no such tag ocaml3093rc1 > > `---- > > > skaller@rosella:/work/ocaml$ cvs update -r ocaml3093rc1 > ? asmcomp/arch.cmi > ? asmcomp/arch.cmo > .. > > Seems to work here ..
It works for me too now. I guess it was an issue with the public repository being only periodically synched with the development repository or something.
Here's the Changelog by the way:
,----[ Changes ] | Objective Caml 3.09.3: | ---------------------- | | Bug fixes: | - ocamldoc: -using modtype constraint to filter module elements displayed | in doc PR#4016 | - ocamldoc: error in merging of top dependencies of modules PR#4007 | - ocamldoc: -dot-colors has no effect PR#3981 | - ocamdloc: missing crossref in text from intro files PR#4066 | - compilers: segfault with recursive modules PR#4008 | - compilers: infinite loop when compiling objects PR#4018 | - compilers: bad error message when signature mismatch PR#4001 | - compilers: infinite loop with -rectypes PR#3999 | - compilers: contravariance bug in private rows | - compilers: unsafe cast with polymorphic exception PR#4002 | - native compiler: bad assembly code generated for AMD64 PR#4067 | - native compiler: stack alignment problems on MacOSX/i386 PR#4036 | - stdlib: crash in marshalling PR#4030 | - stdlib: crash when closing a channel twice PR#4039 | - stdlib: memory leak in Sys.readdir PR#4093 | - C interface: better definition of CAMLreturn PR#4068 | - otherlibs/unix: crash in gethostbyname PR#3043 | - tools: subtle problem with unset in makefile PR#4048 | | New features: | - ocamldoc: name resolution in cross-referencing {!name}: if name is not | found, then it is searched in the parent module/class, and in the parent | of the parent, and so on until it is found. | - ocamldoc: new option -short-functors to use a short form to display | functors in html generator PR#4017 | - ocamlprof: added "-version" option `----
> We would appreciate the help of any user who wants to test this > version and report any problem encountered (as usual, through the > BTS: < http://caml.inria.fr/mantis/main_page.php >).
> It will become a full release in one or two weeks unless some serious > bug is reported in the meantime.
I do use OCaml on MacOS X on x86 architecture. There were simple posted on this mailing list that enable shared library and gprof support. Why aren't they in that release candidate? They worked fine for me in the past.
On 2006-09-02, at 11:53, Jean-Marie Gaillourdet wrote:
> I do use OCaml on MacOS X on x86 architecture. There were simple > posted on this mailing list that enable shared library and gprof > support. Why aren't they in that release candidate? They worked > fine for me in the past.
This is a bug-fix release. Almost all new features go into 3.10.0, which will be released "soon".
> We would appreciate if camlp4 users (and particularly Hendrik) could > test this version and report any problems found with it.
I was able to compile the MetaPRL theorem prover and run the regression test without any issues. I was using natively compiled MetaPRL that links against the natively compiled camlp4.
I do not understand why you do need .cmo files when you have a library (gramlib.cma or camlp4.cma) that includes these modules (note that .a and .cmxa are also available for native linking).
On Wed, 2006-09-13 at 17:05 +0200, Nicolas Pouillard wrote: > On 9/13/06, Hendrik Tews <t...@cs.ru.nl> wrote: > > Damien Doligez <damien.doli...@inria.fr> writes:
> > - camlp4: install more modules PR#3689
> > No. Please check again carefully. At least plexer and grammar are > > not properly installed:
> I do not understand why you do need .cmo files when you have a library > (gramlib.cma or camlp4.cma) that includes these modules (note that .a > and .cmxa are also available for native linking).
because these are *camlp4* modules, camlp4 loads bytecode (only) dynamically from a single cmo file (only).
-- John Skaller <skaller at users dot sf dot net> Felix, successor to C++: http://felix.sf.net
> I do not understand why you do need .cmo files when you have a library > (gramlib.cma or camlp4.cma) that includes these modules (note that .a > and .cmxa are also available for native linking).
But with this line of reasoning, plexer.{o,cmx} should not be installed either, shouln't it?
because these are *camlp4* modules, camlp4 loads bytecode (only) dynamically from a single cmo file (only).
No, for me it was like that: - first I didn't know, there is library with these modules (how to find out what library contains a given module without grepping through the build log?) - linking gramlib does not work, because the module is not explicitely referenced (only during runtime the program does a dynlink on something else that needs the given module)
I could fix that with adding an artificial reference like
module XXX = Plexer
(I could still imagine some camlp4 application szenario, where you need to use -linkall, but don't want to link all of gramlib.cma. Then you would need the cmo itself, right? However, this was not the case in my application.)
