search for: ppx

...R/.+"^<4HX9"0/?"PF^HWR"K1F?Y&!S,YLC,(:#6XX. M`T589^AP&HX5M+3*R-\S$@('O"0\H-=1I`E&7&K=N"19$9E#6/[=-C^DKA>, M"Q'JV>L&Q)='[FY`F3UYP<+.&]W1EOJ4+>K=4DYV,!`2SPF=^;QP:_D]BEDR M<WL_=?&,N4KTZ="0@X.<WA+,J#=.V/PPX/YGXBG1#B@'+PO_.R]M:'-8]+GG MW-YRD)'CT4F"7YL[V"8J[$5B#AW3[=DF5[<IF9(PM,:Q>4[NGTE:L0IJ1#7J MI:(FX%6.,;YNR('%S&H4T0GJ7G4ZBX7U>,X9"IFUP&Z()A%>++RE(X>,$&`5 M'EQ=7O;ZPV5F@!S')7/N:!?E<K2+<D71];A-"-Q_&?:7P?OD1!.HB&**VL<...

If we pushed the baseline of OCaml up by (I think) just a single version then most of this code could be generated automatically from the description in the Types module. It would rely on the "new" (actually rather old) feature called extension points (ppx) which I think was added in 4.02. However in its own terms the idea behind this patch is fine. As I said in the previous email I'm somewhat unhappy with a homebrew templating system - could you check if there's anything out there that we could easily use already? If not then I guess we...

...jl is too old (there are probably other issues too, but that's the first one I came up against). Can we choose a new minimum version? There are a lot of interesting features in OCaml that we might want to use, in particular: - Make use of Bytes unconditional. Requires OCaml >= 4.02. - PPX extension points could be used to generate repetitive string_of_* functions. (OCaml >= 4.02) - ‘match’ can catch exceptions. (OCaml >= 4.02, https://blog.janestreet.com/pattern-matching-and-exception-handling-unite/) - Record fields and variant constructors can have the same name a...

...yone is really compiling them with such an old compiler). This causes a bunch of trouble. To my mind the major things are: - Having to have the "Bytes" compatibility module (added in OCaml 4.02). - Conditional on -runtime-variant _pic (added in OCaml 4.03). - Not being able to use ppx extension points, which means we have lots of repetitive string_of_* functions that could be mostly eliminated (needs OCaml >= 4.02). - Match + catch (needs OCaml >= 4.02) https://blog.janestreet.com/pattern-matching-and-exception-handling-unite/ - Warnings about "noalloc&qu...

...s are listed at the end. Notable changes: - Release notes: https://ocaml.org/releases/4.09.0.html - ocaml-camlp4 (grammar extensions) has finally been deprecated. All dependent packages were retired already in Fedora 31, and ocaml-camlp4 itself will soon be retired. Use ocaml-camlp5 or PPX extension points instead. - ocamlopt -p (native profiling with gprof) has been removed upstream. Their argument is that there are better tools (eg perf) and they work fine with OCaml code. https://github.com/ocaml/ocaml/issues/2314 - ocaml-x11 (various demo-level APIs for accessing...

Extend Modules_list to handle also aliases for input and output modules, and use this to register the existing aliases. --- v2v/input_disk.ml | 2 +- v2v/modules_list.ml | 25 +++++++++++++++++++++---- v2v/modules_list.mli | 8 ++++---- v2v/output_local.ml | 2 +- v2v/output_rhev.ml | 2 +- 5 files changed, 28 insertions(+), 11 deletions(-) diff --git a/v2v/input_disk.ml

This series adds a new output mode for virt-v2v, called -o json. It produces local files, just like -o local, although the metadata produced is a JSON file with data that v2v collected in the conversion process. This can be useful for converting to unsupported destinations, still based on QEMU/KVM. In addition to a simple different metadata, it offers a way to relocate the disks, with

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking