Re: [MirageOS-devel] Any way to get caml4p to run on ARM (cubietruck)?

[Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx>]

>> Try to remove it from LIBS in the generated Makefile and remove the 
>> "syntax(camlp4o)" in SYNTAX to see if this helps.
>> If yes, I'm happy to get rid of the automatic inclusion lwt.syntax by the 
>> mirage tool to avoid that.
> 
> This might need a patch on mirage-decks to remove all the syntax extensions. 
> I think that's a good think.

Sorry to spam the list again. This obviously won't be as easy as it could be in 
mirage-decks as we are using the cow syntax extension in various places. So to 
fix you bug, you might want to edit the SYNTAX flag in the Makefile to add 
"<main.*>: -syntax(camlp4o)" (similar to "static*.*" one). This will tell 
ocamlbuild to not use camlp4 on that file.

Hopes this help,
Thomas



> 
> 
> 
>> 
>> Thomas
>> 
>>> 
>>> Command exited with code 2.
>>> Compilation unsuccessful after building 1 target (0 cached) in 00:00:00.
>>> make[1]: *** [main.native] Error 10
>>> make[1]: Leaving directory `/home/mirage/mirage-decks/src'
>>> make: *** [build] Error 2
>>> ~~~
>>> 
>>> I also have a small project of my own that uses `sexp` a bit, it also fails:
>>> 
>>> ~~~
>>> cd src && make build
>>> make[1]: Entering directory `/home/mirage/mirage-kvsrv/src'
>>> ocamlbuild -use-ocamlfind -pkgs 
>>> lwt.syntax,conduit.mirage,core_kernel,mirage-console.unix,mirage-http,mirage-types.lwt,sexplib.syntax,tcpip.stack-socket
>>>  -tags "syntax(camlp4o),annot,bin_annot,strict_sequence,principal" 
>>> -tag-line "<static*.*>: -syntax(camlp4o)" -cflag -g -lflags -g,-linkpkg 
>>> main.native
>>> + ocamlfind ocamldep -package tcpip.stack-socket -package sexplib.syntax 
>>> -package mirage-types.lwt -package mirage-http -package mirage-console.unix 
>>> -package core_kernel -package conduit.mirage -package lwt.syntax -syntax 
>>> camlp4o -modules main.ml > main.ml.depends
>>> Segmentation fault
>>> File "main.ml", line 1:
>>> Error: Error while running external preprocessor
>>> Command line: camlp4 '-I' '/home/mirage/.opam/4.02.1/lib/ocaml/camlp4' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/type_conv' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/ocaml' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/ocaml' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/sexplib' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/sexplib' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/lwt' '-I' 
>>> '/home/mirage/.opam/4.02.1/lib/lwt' '-parser' 'o' '-parser' 'op' '-printer' 
>>> 'p' 'pa_type_conv.cma' 'unix.cma' 'bigarray.cma' 'sexplib.cma' 
>>> 'pa_sexp_conv.cma' 'lwt-syntax-options.cma' 'lwt-syntax.cma'  'main.ml' > 
>>> /tmp/ocamlpp3e0d09
>>> 
>>> Command exited with code 2.
>>> Compilation unsuccessful after building 1 target (0 cached) in 00:00:00.
>>> make[1]: *** [main.native] Error 10
>>> make[1]: Leaving directory `/home/mirage/mirage-kvsrv/src'
>>> make: *** [build] Error 2
>>> ~~~
>>> 
>>> What can I do to improve my luck with building on my cubietruck?
>>> 
>>> /M
>>> 
>>> -- 
>>> Magnus Therning                      OpenPGP: 0xAB4DFBA4 
>>> email: magnus@xxxxxxxxxxxx   jabber: magnus@xxxxxxxxxxxx
>>> twitter: magthe               http://therning.org/magnus
>>> 
>>> "Sendmail" and "make" are two well known programs that are pretty widely
>>> regarded as being debugged into existence. That's why their command
>>> languages are so poorly thought out and difficult to learn.  It's not
>>> just you -- everyone finds them troublesome.
>>>   -- Peter van der Linden, Expert C Programming, p. 220
>>> _______________________________________________
>>> MirageOS-devel mailing list
>>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
>>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
> 


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel