Xen built with ocaml 4.06 gives errors such as
Error: This expression has type bytes but an expression was
expected of type string
as Byte and safe-strings which were introduced in 4.02 are the
default in 4.06.
This patch which is partly by Richard W.M. Jones of Red Hat
from https://bugzil
On Tue, Jan 30, 2018 at 10:55:47PM +, Michael Young wrote:
> Xen built with ocaml 4.06 gives errors such as
> Error: This expression has type bytes but an expression was
> expected of type string
> as Byte and safe-strings which were introduced in 4.02 are the
> default in 4.06.
> This pa
On Tue, 6 Feb 2018, Wei Liu wrote:
On Tue, Jan 30, 2018 at 10:55:47PM +, Michael Young wrote:
Xen built with ocaml 4.06 gives errors such as
Error: This expression has type bytes but an expression was
expected of type string
as Byte and safe-strings which were introduced in 4.02 are
On Tue, Feb 06, 2018 at 09:56:14PM +, Michael Young wrote:
> On Tue, 6 Feb 2018, Wei Liu wrote:
>
> > On Tue, Jan 30, 2018 at 10:55:47PM +, Michael Young wrote:
> > > Xen built with ocaml 4.06 gives errors such as
> > > Error: This expression has type bytes but an expression was
> > > ex
On Tue, 2018-01-30 at 22:55 +, Michael Young wrote:
> Xen built with ocaml 4.06 gives errors such as
> Error: This expression has type bytes but an expression was
> expected of type string
> as Byte and safe-strings which were introduced in 4.02 are the
> default in 4.06.
> This patch whi
On Thu, Feb 08, 2018 at 06:49:58PM +0100, Dario Faggioli wrote:
> On Tue, 2018-01-30 at 22:55 +, Michael Young wrote:
> > Xen built with ocaml 4.06 gives errors such as
> > Error: This expression has type bytes but an expression was
> > expected of type string
> > as Byte and safe-strings w
On Thu, Feb 08, 2018 at 06:03:48PM +, Wei Liu wrote:
> On Thu, Feb 08, 2018 at 06:49:58PM +0100, Dario Faggioli wrote:
> > On Tue, 2018-01-30 at 22:55 +, Michael Young wrote:
> > > Xen built with ocaml 4.06 gives errors such as
> > > Error: This expression has type bytes but an expression w
> On 8. Feb 2018, at 18:24, Wei Liu wrote:
>
> Christian, do you have any idea when you can look into fixing the
> safe-string patch?
Sorry, I can’t make a promise because of my other obligations. I do wonder,
though: this patch did not come out of nowhere but supposedly was working -
what i
On Fri, 2018-02-09 at 09:20 +, Christian Lindig wrote:
> > On 8. Feb 2018, at 18:24, Wei Liu wrote:
> >
> > Christian, do you have any idea when you can look into fixing the
> > safe-string patch?
>
> Sorry, I can’t make a promise because of my other obligations. I do
> wonder, though: this
On Fri, Feb 09, 2018 at 09:20:33AM +, Christian Lindig wrote:
>
>
> > On 8. Feb 2018, at 18:24, Wei Liu wrote:
> >
> > Christian, do you have any idea when you can look into fixing the
> > safe-string patch?
>
> Sorry, I can’t make a promise because of my other obligations. I do wonder,
>
On Fri, 9 Feb 2018, Christian Lindig wrote:
Sorry, I can’t make a promise because of my other obligations. I do
wonder, though: this patch did not come out of nowhere but supposedly
was working - what is different here?
The patch was from Fedora and is broken there too! It fixes the build
is
On Mon, 12 Feb 2018, Wei Liu wrote:
On Fri, Feb 09, 2018 at 09:20:33AM +, Christian Lindig wrote:
On 8. Feb 2018, at 18:24, Wei Liu wrote:
Christian, do you have any idea when you can look into fixing the
safe-string patch?
Sorry, I can’t make a promise because of my other obligation
> On 9. Mar 2018, at 22:57, Michael Young wrote:
>
> I have had a go at fixing the patch and my revised attempt is attached. I
> suspect it could be tidied up, but it works for me.
Thank you for giving this another go. What is the key difference to the
previous patch which compiled but lead
On Fri, 9 Mar 2018, Christian Lindig wrote:
On 9. Mar 2018, at 22:57, Michael Young wrote:
I have had a go at fixing the patch and my revised attempt is attached. I
suspect it could be tidied up, but it works for me.
Thank you for giving this another go. What is the key difference to the
The problem with the old patch is illustrated by the following section
from the old patch for tools/ocaml/xenstored/utils.ml
@@ -85,7 +85,7 @@ let create_unix_socket name =
let read_file_single_integer filename =
let fd = Unix.openfile filename [ Unix.O_RDONLY ] 0o640 in
let buf
On Mon, 12 Mar 2018, Christian Lindig wrote:
The problem with the old patch is illustrated by the following section
from the old patch for tools/ocaml/xenstored/utils.ml
@@ -85,7 +85,7 @@ let create_unix_socket name =
let read_file_single_integer filename =
let fd = Unix.openfile f
On 12/03/18 19:35, Michael Young wrote:
Here is version 4 of the patch where I have replaced the uses of s with b
where the patch changes it from string to bytes. I have also removed the
two trailing spaces and changed stmp back to s.
Michael Young
0001-make-xen-ocaml-safe-strings-compliant
On Tue, Mar 13, 2018 at 09:29:49AM +, Christian Lindig wrote:
> On 12/03/18 19:35, Michael Young wrote:
>
> > Here is version 4 of the patch where I have replaced the uses of s with b
> > where the patch changes it from string to bytes. I have also removed the
> > two trailing spaces and chang
18 matches
Mail list logo
