buildLisp: --help is always parsed and interpreted by SBCL
#136
Opened by sterni at
I tried inserting a --
in the wrapper as a workaround, but that is passed to the executed program and messes up argument parsing. Other options like --script
or --eval
don't seem to be understood though.
$ ./result/bin/🕰️ --help Usage: sbcl [runtime-options] [toplevel-options] [user-options] Common runtime options: --help Print this message and exit. --version Print version information and exit. --core <filename> Use the specified core file instead of the default. --dynamic-space-size <MiB> Size of reserved dynamic space in megabytes. --control-stack-size <MiB> Size of reserved control stack in megabytes. --tls-limit Maximum number of thread-local symbols. Common toplevel options: --sysinit <filename> System-wide init-file to use instead of default. --userinit <filename> Per-user init-file to use instead of default. --no-sysinit Inhibit processing of any system-wide init-file. --no-userinit Inhibit processing of any per-user init-file. --disable-debugger Invoke sb-ext:disable-debugger. --noprint Run a Read-Eval Loop without printing results. --script [<filename>] Skip #! line, disable debugger, avoid verbosity. --quit Exit with code 0 after option processing. --non-interactive Sets both --quit and --disable-debugger. Common toplevel options that are processed in order: --eval <form> Form to eval when processing this option. --load <filename> File to load when processing this option. User options are not processed by SBCL. All runtime options must appear before toplevel options, and all toplevel options must appear before user options. For more information please refer to the SBCL User Manual, which should be installed along with SBCL, and is also available from the website <http://www.sbcl.org/>.
- sterni updated the body of this issue at 2021-08-07T22·20+00
-
sterni at 2021-08-15T11·26+00
- tazjin closed this issue at 2021-08-26T18·47+00