oriansj / mes-m2 Goto Github PK

I know @oriansj probably already knows all this but just documenting it.

From just removing stuff out of mescc.scm to try to make it "run", I've found the following things still need to be added to the slow_lisp branch to make it work:

• Modules support (define-module, use-module, mes-use-module)
• cond-expand support https://www.gnu.org/software/mit-scheme/documentation/mit-scheme-ref/cond_002dexpand-_0028SRFI-0_0029.html
• getenv support
• when (being a scheme n00b I have no idea what it is)

Haven't investigated much further yet but it seems to hang.

I'm trying to compile a hello-world with mes-m2 by running these commands:

$ git clone https://github.com/oriansj/mes-m2
$ cd mes-m2
$ make CFLAGS=-m32 mes-m2
$ (echo '#include <libmes-mini.h>'
   echo 'int main(int argc, char **argv) { return eputs("Hello, World"); }'
  ) >hello.c
$ bin/mes-m2 scripts/mescc.scm hello.c
error: unrecognized switch scripts/mescc.scm
...

I was trying some other command-line flags to mes-m2, but nothing worked.

What is the correct command to run to compile hello-world with mes-m2?

Please note that I'm a newbie to Mes and M2-Planet. I haven't run Guile, Mes or any other Scheme implementation in my life. I have experience with standard Unix tools (e.g. Make and GCC).

I did a bootstrap using stage0-posix and had a few difficulties.

• The readme did not mention the env vars MES_ARENA , MES_MAX_ARENA, MES_STACK. They seemed necessary.

• The correct command for mes-m2 was:

MES_ARENA=20000000
MES_MAX_ARENA=20000000
MES_STACK=6000000
export MES_ARENA  MES_MAX_ARENA MES_STACK
$ ./bin/mes --no-auto-compile -L ../nyacc-1.00.2/module/  -e main scripts/mescc.scm -I include -v -S scaffold/exit-42.c
parsing: input
compiling: input
    :main
dumping: exit-42.s
M1: functions
    :main
M1: globals

(This differs because -L module was removed)

• The correct command for guile was:

guile --no-auto-compile -L ../nyacc-1.00.2/module/ -L module -e main scripts/mescc.scm -I include -v -S scaffold/exit-42.c

(This differs because it explains nyacc must be added to the module path)