asdf-devel April 2018

asdf-devel@common-lisp.net

8 participants
5 discussions

Testing for ASDF 3.3.2 and beyond?
by Faré 27 Apr '18

27 Apr '18

Dear Anton, can you run the below tests, in order or priority? 1- Can you test what is currently in master, a.k.a. 3.3.1.3, as a release candidate for 3.3.2? It has been too long since 3.3.1 was released with several bugs that have impacted Quicklisp users. 2- Can you test what is currently in the syntax-control branch as a release candidate for 3.3.3 or 3.4.0? We want to merge syntax control, but it's a significant enough change that we don't want it at the same time as the bug fixes. Also... 3- Can you test what is currently in the syntax-control branch as a release candidate for 3.3.3 or 3.4.0, but with the following addition just after you load asdf but before you start using it: (defparameter uiop:*shared-readtable* (copy-readtable nil)) ? Indeed, we want to see what breaks if we disable extensions implementation-specific reader extensions. Test most important on CCL. I don't expect much breakage on other implementations, but it may exist, too. 4- While you're at it, can you also run the test, at least on sbcl, with (defparameter uiop:*shared-readtable* uiop:*standard-readtable*)) ? This will detect what breaks when we make the default readtable read-only. The thing is, we really want to have this syntax control, but we also want to preserve backward compatibility, and we can't make asdf stricter until every client is fixed (famous last word; of course we failed at exactly that in 3.3.1 — we could build correctly, but would also spuriously rebuild if secondary systems were misnamed; fixed in 3.3.1.3). https://gitlab.common-lisp.net/asdf/asdf/blob/syntax-control/doc/syntax-con… https://gitlab.common-lisp.net/asdf/asdf/merge_requests/86 http://blog.quicklisp.org/2018/01/build-failures-with-asdf-331.html —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org A friend once asked me if I had ever considered terrorism as a means for political change. I replied that yes, I had considered it... and rejected it. Because it only causes change for the worse. Killing innocent people does not promote a culture of peaceful interaction.

5 26

Problems with DEFSYSTEM-DEPENDS-ON
by Mark Evenson 09 Apr '18

09 Apr '18

The usage of DEFSYSTEM-DEPENDS-ON to specify dependencies that will be satisfied by QL:QUICKLOAD no longer seems to be working in asdf-3.3.1. It used to be the case that to use the [PROVE testing framework][1], it was sufficient to place a … :defsystem-depends-on (:prove-asdf) … clause in the secondary system to be tested, and then upon a QL:QUICKLOAD of this system, the dependency on PROVE was then resolved via a network download from Quicklisp. [1]: https://github.com/fukamachi/prove I believe this was working with asdf-3.2, but testing that assumption is a little hard as asdf-3.3 refuses to degrade itself with a downgrade, and all my systems are running asdf-3.3. Maybe something in Quicklisp changed as well?

5 11

Re: Building from clean on Allegro Windows
by Faré 09 Apr '18

09 Apr '18

I couldn't reproduce with AllegroExpress 10.1 on Linux amd64. So I gave a closer look on the Windows VM, rm'ing all the files in build/results/ before I retried, and looked at the minimal logs for the issue. The warnings were a false lead: Allegro does issue them, but they are actually caught by the build system, so were not the issue. The real issue was that allegro was looking for alisp.exe.dxl instead of alisp.dxl. I thus modified run-tests.sh so it will handle this case with more care. All the tests then passed except test-multiple (which works for me on Linux). Unsurprisingly, I see test-multiple uses ln -s and has an ugly workaround on Windows that doesn't work on sbcl, either. I moved it from using ln -s to using copies, which modified the behavior in ways I admit I don't fully comprehend. I documented the parts I did understand. test-multiple exercises a really dark corner of the design, anyway, one that we're trying to deprecate, badly-named secondary systems. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org You may easily play a joke on a man who likes to argue — agree with him. — Edgar Waston Howe On Sat, Apr 7, 2018 at 3:22 PM, Robert Goldman <rpgoldman(a)sift.net> wrote: > Got the same issue: > > Warning: FIRST-FEATURE is defined more than once as `operator' in file > build\asdf.lisp. > Warning: IMPLEMENTATION-TYPE is defined more than once as `operator' in > file build\asdf.lisp. > Warning: *IMPLEMENTATION-TYPE* is defined more than once as `variable' > in file build\asdf.lisp. > Warning: OPERATING-SYSTEM is defined more than once as `operator' in > file build\asdf.lisp. > Warning: ARCHITECTURE is defined more than once as `operator' in file > build\asdf.lisp. > > I'll see if I can figure out what causes this. EVAL-WHEN is a likely > candidate. > > More as I have news, > r

2 1

Re: Issues with package location information on SBCL
by Eric Timmons 04 Apr '18

04 Apr '18

On Mon, Feb 19, 2018 at 7:03 PM, Eric Timmons <etimmons(a)mit.edu> wrote: > I've also opened the following bug on SBCL to let them know about it: > https://bugs.launchpad.net/sbcl/+bug/1750466. This bug has been fixed upstream and should probably appear in SBCL 1.4.7. Since they got that fixed before ASDF 3.3.2 got out, is it worth reverting commit 21e3a85? That would keep the return of `parse-define-package-form` unchanged and the warnings would only show up in SBCL 1.4.1-1.4.6 inclusive. -Eric

1 0

"deprecated recursive use" warning
by Attila Lendvai 01 Apr '18

01 Apr '18

dear list, shall i be concerned about this? WARNING: Deprecated recursive use of (ASDF/OPERATE:OPERATE 'ASDF/LISP-ACTION:LOAD-OP '("cffi/c2ffi-generator")) while visiting (CFFI/C2FFI::GENERATE-LISP-OP "hu.dwim.zlib" "c2ffi-spec" "zlib.h") - please use proper dependencies instead it happens due to this in cffi/src/c2ffi/asdf.lisp: (defmethod perform ((op generate-lisp-op) (c c2ffi-file)) ... (unless (component-loaded-p :cffi/c2ffi-generator) (load-system :cffi/c2ffi-generator)) ... ) that system only needs to get loaded when the action is executed. or is it safe to ignore that warning long term? -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “If we have the truth, it cannot be harmed by investigation. If we have not the truth, it ought to be harmed.” — J. Reuben Clark (1871–1961)

4 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel April 2018