You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run the build.sh, the steps for build1 seem to run into an uncontrolled loop where it gives the same two prompts over and over. When I run build.sh | head -20 to see how it starts, it does stop the assembler, but gives errors about missing files.
This may actually be a kernalemu bug.
Here's the first 20 lines of output:
splatty:cbmsrc nickb$ ./build.sh | head -20
CBM RESIDENT ASSEMBLER V080282
(C) 1982 BY COMMODORE BUSINESS MACHINES
OBJECT FILE (CR OR D:NAME):
CBM RESIDENT ASSEMBLER V080282
(C) 1982 BY COMMODORE BUSINESS MACHINES
OBJECT FILE (CR OR D:NAME):
HARD COPY (CR/Y OR N)?
CROSS REFERENCE (CR/NO OR Y)?
SOURCE FILE NAME?
CROSS REFERENCE (CR/NO OR Y)?
SOURCE FILE NAME?
CROSS REFERENCE (CR/NO OR Y)?
SOURCE FILE NAME?
CROSS REFERENCE (CR/NO OR Y)?
SOURCE FILE NAME?
./build.sh: line 37: _tmp_obj: No such file or directory
mv: rename printer4.txt to ../MONITOR_AIM65.lst: No such file or directory
Results of uname -a: Darwin splatty.local 18.7.0 Darwin Kernel Version 18.7.0: Mon May 3 20:41:19 PDT 2021; root:xnu-4903.278.68~1/RELEASE_X86_64 x86_64
The text was updated successfully, but these errors were encountered:
This is because the echo command does not handle the backslash sequences. I had this very same issue.
It can be fixed by adding the "-e" option to the echo commands. It is included in commit 281ea10, which is part of PR #5.
When I run the
build.sh
, the steps forbuild1
seem to run into an uncontrolled loop where it gives the same two prompts over and over. When I runbuild.sh | head -20
to see how it starts, it does stop the assembler, but gives errors about missing files.This may actually be a
kernalemu
bug.Here's the first 20 lines of output:
Results of
uname -a
:Darwin splatty.local 18.7.0 Darwin Kernel Version 18.7.0: Mon May 3 20:41:19 PDT 2021; root:xnu-4903.278.68~1/RELEASE_X86_64 x86_64
The text was updated successfully, but these errors were encountered: