[LispM] ASDF 3.2.1 Anyone?
Steven Nunez
steven.nunez at illation.com.hk
Thu Aug 31 01:37:56 PDT 2017
Dear Fare,
Forgive my ignorance, but how do I print the initargs when the error happens at compile time?
SteveN
From: Faré [mailto:fahree at gmail.com]
Sent: 31 August, 2017 14:31
To: Steven Núñez <steven.nunez at illation.com>
Cc: <lispm at tunes.org> <lispm at tunes.org>
Subject: Re: [LispM] ASDF 3.2.1 Anyone?
Dear Steve,
I can't help you if you fail to act on my suggestions. I'll repeat them.
"1- can you identify what initargs are being passed? Modify the asdf.lisp source code around that error string to also show the initargs and the class of the operation in the error message and/or get a backtrace.
2- which version of the LOOP macro you use depends on which dialect/syntax is active when you load. Are you using the ANSI-Common-Lisp syntax? Are there patches to apply to Genera so its LOOP macro will be fully compliant at long last?"
For 1, PLEASE MODIFY ASDF TO SHOW THE INITARGS IN THE ERROR MESSAGE.
For 2, PLEASE USE WHATEVER INTROSPECTION FUNCTION GENERA HAS to print the current syntax in an EVAL-WHEN, and check whether it is indeed the same when you compile with one error and when you load with another error.
If you fail to act on debugging suggestions, perhaps it's vain trying to make suggestions to you.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
I believe in God, only I spell it Nature. — Frank Lloyd Wright
On Thu, Aug 31, 2017 at 8:21 AM, Steven Nunez <steven.nunez at illation.com.hk <mailto:steven.nunez at illation.com.hk> > wrote:
Still no luck. I thought I’d upgrade Genera before going any further, but that didn’t solve anything (I really didn’t think it would, but wanted to eliminate that possibility).
It looks like the failure is in load-op, being called with an argument of (clos-internals:storage-area 8). At the end of this message there is a detailed stack trace, with all arguments. According to the documentation:
“clos-internals:storage-area, which specifies the area in which to create the instance. The value should be an area number. The default is sys:default-cons-area”
Loading, as opposed to compiling, as I’m doing here, should be with ANSI-COMMON-LISP, since that’s in the attribution line. I’ll experiment with loading next, after a few passes at solving things here. The entire detailed stack trace is:
Regards,
* SteveN
PS The compiler throws up a few warnings that might be of interest, not to this problem, but overall code quality:
From: Faré [mailto:fahree at gmail.com <mailto:fahree at gmail.com> ]
Sent: 27 August, 2017 22:27
To: Steven Núñez <steven.nunez at illation.com <mailto:steven.nunez at illation.com> >
Cc: <lispm at tunes.org <mailto:lispm at tunes.org> > <lispm at tunes.org <mailto:lispm at tunes.org> >
Subject: Re: [LispM] ASDF 3.2.1 Anyone?
I admit I haven't tried Genera since ASDF 3.1.6 or so, so some adverse changes may have been introduced since.
1- can you identify what initargs are being passed? Modify the asdf.lisp source code around that error string to also show the initargs and the class of the operation in the error message and/or get a backtrace.
2- which version of the LOOP macro you use depends on which dialect/syntax is active when you load. Are you using the ANSI-Common-Lisp syntax? Are there patches to apply to Genera so its LOOP macro will be fully compliant at long last?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
An atheist doesn't have to be someone who thinks he has a proof that there
can't be a god. He only has to be someone who believes that the evidence on
the God question is at a similar level to the evidence on the werewolf
question. — John McCarthy
On Sat, Aug 26, 2017 at 12:29 PM, Steven Nunez <steven.nunez at illation.com.hk <mailto:steven.nunez at illation.com.hk> > wrote:
Gents,
I’m trying to get ASDF working on Genera. The ASDF webpage <https://common-lisp.net/project/asdf/> claims that it should ‘just work’, and I see that there was a recent change so the file has a proper attribute line <https://bugs.launchpad.net/asdf/+bug/1517223> , but I’m not getting a clean compile. Below is the result of an attempt to compile from zmacs:
Interestingly, loading gives me a different error:
Does anyone have a version that compiles cleanly so that I can load it from lispm-init.lisp?
Regards,
* Steve
_______________________________________________
LispM mailing list
LispM at tunes.org <mailto:LispM at tunes.org>
http://lists.tunes.org/mailman/listinfo/lispm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </archives/lispm/attachments/20170831/3e1984c8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 49160 bytes
Desc: not available
URL: </archives/lispm/attachments/20170831/3e1984c8/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 64764 bytes
Desc: not available
URL: </archives/lispm/attachments/20170831/3e1984c8/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 34531 bytes
Desc: not available
URL: </archives/lispm/attachments/20170831/3e1984c8/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 7984 bytes
Desc: not available
URL: </archives/lispm/attachments/20170831/3e1984c8/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 22247 bytes
Desc: not available
URL: </archives/lispm/attachments/20170831/3e1984c8/attachment-0009.png>
More information about the LispM
mailing list