If it is at all helpful, I've been using GCL 2.7.1 successfully with ASDF after applying the attached patches to ASDF code.
On Tue, May 6, 2025 at 11:16 AM Robert Goldman <rpgold...@sift.info> wrote: > I'm not sure why this would be happening. If you look at run-tests.sh, > https://gitlab.common-lisp.net/asdf/asdf/-/blob/master/test/run-tests.sh?ref_type=heads#L535-537 > , the test script tests for GCL and should short-cut this exact test. > > That error messages comes out of test/script-support.lisp, in > compile-asdf-script. I'd suggest you put some reader conditional around > that call to leave-test to quash failure and see how much further you get. > > Cheers, > R > > On 6 May 2025, at 10:01, Raymond Toy wrote: > > GCL 2.7.1 was just recently released and I decided to see if asdf could be > compiled with this version. I had to make a small change in uiop/os.lisp > to use `system::chdir`, the internal symbol instead of the external > symbol. (Not sure if that's really correct, but it does work from the > repl.) > > This seems to allow asdf.lisp to be compiled. The next step was running > `make l=gcl GCL=<path>/gcl-2.7.1/bin/gcl test`. However this fails with > the message: > > > Testsuite failed: ASDF compiled with unexpected full warnings > > There are a few warnings from the compiler. However, I'd like to see how > far I can get without fixing the compiler warnings. Is that possible? > > I just don't want to spend a lot of time fixing compiler warnings if there > are more serious issues that are exposed by the testsuite. > > > > >
asdf-gcl-patches
Description: Binary data
