<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">On 15 Dec 2022, at 14:48, Robert Dodier wrote:</p>
</div><div class="plaintext" style="white-space: normal;"><blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><p dir="auto">Robert, thanks for your reply. I have made some progress.</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;"><blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #BBBBBB; color: #BBBBBB;"><p dir="auto">Just performed compiling #<INSTRUMENTED-CL-SOURCE-FILE
<br>
"test-serial-system" "package"> but failed to mark it done</p>
</blockquote></blockquote><blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;"><p dir="auto">It would help to get a backtrace here. I can't tell from this if the error is happening in ASDF or in ASDF-DEPENDENCY-GROVEL (which probably isn't maintained).</p>
</blockquote><p dir="auto">The "failed to mark it done" is coming from ASDF. The ASDF version
<br>
(bundled with SBCL) is, I think, 3.2.something. I tried it with
<br>
Clozure CL, which has (on my system at least) ASDF 3.1.something, and
<br>
the same operation succeeds. I guess I'm not too worried about it,
<br>
since I now have a workaround, but I'm curious to know what's going on
<br>
here.</p>
</blockquote></div>
<div class="markdown" style="white-space: normal;">
<p dir="auto">FWIW, <em>both</em> of these are obsolete. The current release is 3.3.6 which you can get from the ASDF home page (at common-lisp.net)</p>
<p dir="auto">I don't see any reason that 3.3.6 would fix the problem you see, but we can't debug old versions of ASDF.</p>
<p dir="auto">It should be easy to install the new version of ASDF on any lisp if you grab the monolithic file and load it in your lisp .rc file</p>
</div><div class="plaintext" style="white-space: normal;"><blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;"><p dir="auto">Also whose run-tests.sh are these? ASDF's tests or ASDF-dependency-grovel's?</p>
</blockquote><p dir="auto">For the record, it's the run-tests.sh of asdf-dependency-grovel.</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;"><p dir="auto">Again, it would help to have a backtrace from this circular dependency to help us get started (if you can share it -- I suppose your system could be private/proprietary).</p>
</blockquote><p dir="auto">About the circular dependency, it's in Maxima's ASDF file. After
<br>
puzzling over a backtrace (thanks for the hint) I figured out it's
<br>
because :serial t is specified, and a module depends on something
<br>
later in the .asd. I moved the offending module and that resolved the
<br>
dependency error. Hurray!</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; border-left-color: #999999; color: #999999;"><p dir="auto">I wonder if we should adopt asdf-dependency-grovel into the ASDF group on cl.net's GitLab? There's no guarantee that would result in active maintenance, though -- it should be obvious that I don't have a lot of cycles to spare...</p>
</blockquote><p dir="auto">Well, I think that sounds like a good idea. I know developing new code
<br>
is unlikely but it would be great to at least make any updates
<br>
necessary to keep up with new ASDF versions.</p>
<p dir="auto">asdf-dependency-grovel seems like a really great idea -- I am hoping
<br>
to use it to analyze dependencies in Maxima, which, as you may know,
<br>
is an ancient and pretty large system ... If asdf-dependency-grovel
<br>
didn't exist, I would have to reinvent some wheels.</p>
</blockquote></div>
<div class="markdown" style="white-space: normal;">
<p dir="auto">Forking it into ASDF would make sense because then at least we could set up GitLab CI and identify when it does or does not work with the most up-to-date ASDF.</p>
<p dir="auto">If you think this is a good idea, and would be willing to set up a fork of asdf-dependency-grovel, please contact off-list with your cl.net account (they are easy to get if you don't have one), and I can add you to the group. Then you would be able to fork A-D-G into the ASDF group. From there I could set up the GitLab CI to run the tests automagically.</p>
</div>
</div>
</body>
</html>