A bug(?) around phantoms in 3.11.0 b1 (Re: [Caml-list] OCaml version 3.11.0+beta1)

2008-10-21 Thread Jun Furuse
Hi, I found a strange bug in 3.11.0 beta 1. The following typical example of phantom types does not compile any more. (It is compilable in 3.10.2, but not in release311): module M : sig type +'a t constraint 'a = [ `checked | `unchecked ] val check : _ t - [ `checked ] t end = struct type

RE: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread David Allsopp
The Win64 port is listed as requiring Windows XP 64 or Server 64 - is 64 bit Windows Vista not included in the list because it's not supported or because it's not been tested with it? David -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Damien Doligez

RE: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread David Allsopp
Apologies if I missed them, but are there any installation instructions for flexdll for Win32 building OCaml 3.11? I copied flexdll.h, flexdll_initer_mingw.o, flexdll_mingw.o and flexlink.exe to my (empty) OCaml bin directory (C:\Dev\OCaml\bin which is in PATH) before starting to build which

RE: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread David Allsopp
I'm slowly testing my stuff on WinXP SP2 and will do Windows Vista SP1 (both MinGW build). Very much looking forward to adding plug-in support back into two products now that native Dynlink is available so many thanks to the OCaml team for the work on this release! Both the MSVC and MinGW ports

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread Alain Frisch
David Allsopp wrote: The install target of flexdll's Makefile suggests copying: flexdll_initer.c, flexdll.c Surely these aren't needed once it's compiled? Indeed. However, some people might want to recompile them (e.g. to keep debug symbols, or to use a specific version of their C

Re : [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread Adrien
2008/10/16, Alain Frisch [EMAIL PROTECTED]: David Allsopp wrote: There seems to be an interesting chicken-and-egg source dependency between flexdll and OCaml 3.11 - you can't build OCaml 3.11 from source or use it afterwards without flexdll and you can't build flexdll from source without

Re: Re : [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread Alain Frisch
Adrien wrote: How often should we expect new releases of flexlink ? Basically, the question is : will it have to be updated from time to time or can we just drop it somewhere and forget everything about it ? There will be new releases when bugs are found and fixed. It's hard to predict. I

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread Andres Varon
On Oct 16, 2008, at 5:58 AM, David Allsopp wrote: Both the MSVC and MinGW ports seem to have an error in the Makefile - they're linking against tk83.dll and tcl83.dll - the OCaml 3.10.2 line to link against tk84.lib and tcl84.lib is commented out. Changing the Makefile to link against

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread Andres Varon
On Oct 16, 2008, at 12:22 PM, Andres Varon wrote: On Oct 16, 2008, at 5:58 AM, David Allsopp wrote: Both the MSVC and MinGW ports seem to have an error in the Makefile - they're linking against tk83.dll and tcl83.dll - the OCaml 3.10.2 line to link against tk84.lib and tcl84.lib is

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-16 Thread Andres Varon
On Oct 16, 2008, at 12:31 PM, Andres Varon wrote: Changing the Makefile to link against tk84.dll and tcl84.dll seems to fix the problem. Did you manage to do it with *.dll or *.lib? I don't have those dll's and have been unable to compile the MinGW port with a setup that succeeded

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Andres Varon
On Oct 15, 2008, at 9:40 AM, Damien Doligez wrote: Dear OCaml Users, We are pleased to celebrate the birthday of Friedrich Nietzsche by releasing OCaml version 3.11.0+beta1. We need YOU to test it thoroughly and report any problems you might have. Does your favorite software work with it?

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Alain Frisch
Andres Varon wrote: Thanks for the good work. I would like to know exactly what architectures support the native Dynlink? I did not see this information in the release notes. The native Dynlink is known to work under Linux x86, Linux AMD64, Win32 (mingw/msvc ports). It has been lightly

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Andres Varon
On Oct 15, 2008, at 11:04 AM, Alain Frisch wrote: Andres Varon wrote: Thanks for the good work. I would like to know exactly what architectures support the native Dynlink? I did not see this information in the release notes. The native Dynlink is known to work under Linux x86, Linux

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Andres Varon
On Oct 15, 2008, at 11:22 AM, Daniel Bünzli wrote: The native Dynlink is known to work under Linux x86, Linux AMD64, Win32 (mingw/msvc ports). It has been lightly tested under Win64, some flavors of BSDs and also the Cygwin port. And on macosx ? It seems here on 10.5.5 that only

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Stefano Zacchiroli
On Wed, Oct 15, 2008 at 05:04:46PM +0200, Alain Frisch wrote: Andres Varon wrote: Thanks for the good work. I would like to know exactly what architectures support the native Dynlink? I did not see this information in the release notes. The native Dynlink is known to work under Linux x86,

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Jaap Boender
On Wednesday 15 October 2008 15:40:01 Damien Doligez wrote: We are pleased to celebrate the birthday of Friedrich Nietzsche by releasing OCaml version 3.11.0+beta1. We need YOU to test it thoroughly and report any problems you might have. Does your favorite software work with it? For ease

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Alain Frisch
Daniel Bünzli wrote: And on macosx ? It seems here on 10.5.5 that only dynlink.cma and dynlink.cmi for bytecode get installed. So I guess there's no support. What about the future ? Native dynlink used to work on Mac OS X 10.5 (x86 only). The new linker in 10.5 does not support linking

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Alain Frisch
Andres Varon wrote: One more question: is it always compiled? or is dynlink.cmxa simply not available in some architectures? if yes, what are those? As far as I can tell, dynlink.cmxa is always compiled. You will get error when ocamlopt -shared on those architecture where natdynlink is not

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Andres Varon
On Oct 15, 2008, at 11:37 AM, Alain Frisch wrote: Andres Varon wrote: One more question: is it always compiled? or is dynlink.cmxa simply not available in some architectures? if yes, what are those? As far as I can tell, dynlink.cmxa is always compiled. You will get error when ocamlopt

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Alain Frisch
Andres Varon wrote: OK. Would you recommend that configure scripts use this test to verify if the functionality is supported? Yes. -- Alain ___ Caml-list mailing list. Subscription management:

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Andres Varon
On Oct 15, 2008, at 11:32 AM, Alain Frisch wrote: Daniel Bünzli wrote: And on macosx ? It seems here on 10.5.5 that only dynlink.cma and dynlink.cmi for bytecode get installed. So I guess there's no support. What about the future ? Native dynlink used to work on Mac OS X 10.5 (x86

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Xavier Leroy
Native dynlink used to work on Mac OS X 10.5 (x86 only). The new linker in 10.5 does not support linking shared libraries with non-PIC code. It is still possible to use the old linker, called ld_classic, but some libraries (like X11) does not work, so this has been disabled in the configure

Re: [Caml-list] OCaml version 3.11.0+beta1

2008-10-15 Thread Richard Jones
On Wed, Oct 15, 2008 at 03:40:01PM +0200, Damien Doligez wrote: We are pleased to celebrate the birthday of Friedrich Nietzsche by releasing OCaml version 3.11.0+beta1. We need YOU to test it thoroughly and report any problems you might have. Does your favorite software work with it?