[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re:Re: Maybe a Bug in mdk-1.3.0

From: sqc
Subject: Re:Re: Maybe a Bug in mdk-1.3.0
Date: Mon, 17 Jan 2022 20:42:00 +0800 (CST)

Hi Jose,

Thanks for your quickly response and fixing the bug.

Actually, I installed by source tarball. Now I meet some problem when I build 
it from the 'development source tree'. The error message is below,
test -f mix_scanner.c || /bin/sh ../ylwrap mix_scanner.l .c mix_scanner.c -- 
/bin/sh /root/mdk/missing flex  
lex.yymix_scanner.c is unchanged
gcc -DHAVE_CONFIG_H -I. -I..    -Wall -fno-strict-aliasing 
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include  -DG_DISABLE_DEPRECATED 
-I/usr/local/include -I.. -DG_LOG_DOMAIN=\"libmix\" -g -O2 -MT mix_scanner.o 
-MD -MP -MF .deps/mix_scanner.Tpo -c -o mix_scanner.o mix_scanner.c
gcc: 错误:mix_scanner.c:没有那个文件或目录(file or directory not exist)
gcc: 致命错误:没有输入文件(no input file for gcc).

So, I need more time to overcome this problem. Then I can have a try :-)

Best regards,
Kevin Sun

At 2022-01-17 00:47:19, "Jose Antonio Ortega Ruiz" <jao@gnu.org> wrote:
>On Sun, Jan 16 2022, sqc wrote:
>> Hi,
>> It seems that there is a bug in the MDK 1.3.0. 
>> The command 'pline' cannot be used. When I type 'pline [some number]',
>> the error message is given. It says that this is not a valid command.
>> But I find that there is handler for the command 'pline'. So, I check
>> the source. And I find that the command 'sbt' has not conrresponding
>> enumeration definition in 'mix_vm_command_t'.  By inserting a
>> temperary enumeration for the command 'sbt', the problem can be
>> solved. The command 'pline' can be used.
>Yes, i think you're absolutely right.  I've just pushed a patch to the
>master git branch that, i think, fixes the problem along your
>indications.  Are you able to compile from master to check?
>Many thanks for taking the time to report and debug, and for using mdk:
>it's always nice to know of people finding it useful!
>If a listener nods his head when you're explaining your program, wake
>him up.
>  - Alan Perlis, Epigrams on Programming

reply via email to

[Prev in Thread] Current Thread [Next in Thread]