asdf-devel July 2018

asdf-devel@common-lisp.net

6 participants
8 discussions

Is anyone actually using the deferred warnings code?
by Robert Goldman 05 Aug '18

05 Aug '18

AFAICT, it is disabled by default, and it is not documented in the ASDF manual. So is this code even live, except for in the test scripts? It was pretty painful to get this to work because it relies on unexported (and hence unstable) SBCL internals. My *guess* is that this was originally done as a way to dispense with `WITH-COMPILATION-UNIT` and hence potentially parallelize the compilations. If no one is even using it, I am tempted to move it to be a contrib and drop it from the tests and maintenance as part of core ASDF. Maybe it would be better as a part of a POIU extension to ASDF, and relieve me of dealing with these SBCL compiler internals? Cheers, r

3 3

Another apology...
by Robert Goldman 31 Jul '18

31 Jul '18

I accidentally committed something with a stupid typo. I force-pushed the last push to keep the history clean. Thanks

1 0

More apologies needed
by Robert Goldman 29 Jul '18

29 Jul '18

Sorry *again*. My history fixing was done wrong initially. But 3.2.3.3 should be in place fine now. Best, r

1 0

A little history rewriting...
by Robert Goldman 29 Jul '18

29 Jul '18

Sorry -- I accidentally pushed tag 3.3.3.3 instead of 3.3.2.3. I have fixed that, but it involved deleting the tag from cl.net gitlab after having pushed it. Apologies and thanks to Fare for catching my mistake! R

1 0

Issues with Jenkins and clisp
by Robert Goldman 29 Jul '18

29 Jul '18

For some reason, the ASDF tests are failing on Jenkins on linux with clisp, but *only when run in Jenkins and only for clisp*. At the command line, all the tests pass for me. Under Jenkins, I get this failure on `test-program.script`: ``` ;; Loading file test-program.script ... FOO (UIOP/LISP-BUILD:CURRENT-LISP-FILE-PATHNAME) => #P"test-program.script" ; Registering system hello-world-example 0 errors, 0 warnings ;; Loading file /var/lib/jenkins/workspace/asdf/test/hello-world-example.asd ... ;; Loaded file /var/lib/jenkins/workspace/asdf/test/hello-world-example.asd 0 errors, 0 warnings 0 errors, 0 warnings ; Registering system lisp-invocation ;; Loading file /var/lib/jenkins/workspace/asdf/asdf.asd ... ;; Loaded file /var/lib/jenkins/workspace/asdf/asdf.asd 0 errors, 0 warnings ;; Loading file /var/lib/jenkins/workspace/asdf/build/fasls/clisp-2.49.60+-unix-x64/asdf/build/asdf.fas ... ;; Loaded file /var/lib/jenkins/workspace/asdf/build/fasls/clisp-2.49.60+-unix-x64/asdf/build/asdf.fas 0 errors, 326 warnings ;; Loading file /var/lib/jenkins/workspace/asdf/ext/lisp-invocation/lisp-invocation.asd ... ;; Loaded file /var/lib/jenkins/workspace/asdf/ext/lisp-invocation/lisp-invocation.asd 0 errors, 0 warnings 0 errors, 0 warnings 0 errors, 0 warnings ;; Loading file /var/lib/jenkins/workspace/asdf/ext/lisp-invocation/lisp-invocation.asd ... ;; Loaded file /var/lib/jenkins/workspace/asdf/ext/lisp-invocation/lisp-invocation.asd 0 errors, 0 warnings 0 errors, 0 warnings 0 errors, 0 warnings 0 errors, 0 warnings ;; Loading file /var/lib/jenkins/workspace/asdf/ext/fare-utils/fare-utils.asd ... ;; Loaded file /var/lib/jenkins/workspace/asdf/ext/fare-utils/fare-utils.asd 0 errors, 0 warnings *** - handle_fault error2 ! address = 0x55a16f64c670 not in [0x5575be29b000,0x5575be657030) ! SIGSEGV cannot be cured. Fault address = 0x55a16f64c670. GC count: 65 Space collected by GC: 74922832 Run time: 0 874720 Real time: 1 803489 GC time: 0 179953 Permanently allocated: 165368 bytes. Currently in use: 5850000 bytes. Free space: 1462440 bytes. Segmentation fault (core dumped) Using clisp, test-program.script failed ``` This is with the latest release (but ancient) clisp. It looks like it's not even making it through the preliminary loading process, since we don't see the "test image-op" debugging output. My guess is that this is not a real asdf failure, but instead is clisp being unable to find some piece of tool-age that it needs in order to build a program. But this happened only after (1) load-asdf changed and (2) `source-file-type` was deprecated. Neither of those seems obviously connected to this issue. Any hypotheses or suggestions for debugging?

3 3

POIU is bitrotten
by Faré 26 Jul '18

26 Jul '18

In case anyone cares (I suppose no one does), POIU, the parallel operator on independent units, that parallelizes compilation (but not loading) of ASDF component, with various options regarding determinism or non-determinism, is current bitrotten and not working on ASDF 3.3.2.2, and I disabled its functionality. I don't have the time or interest to fix it (I haven't been using CL at work for five years, and have stopped using it for new personal projects). The other option I know to parallelize a CL build is bazelisp (the Lisp support for bazel.build), which I would bet is also bitrotten, since I haven't touched it in years, either. [An earlier option I worked on, XCVB, has bitrotten long ago.] I am still available for advice in case someone wants to fix things — better ask before the information gets evicted to long-term storage. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Superstition brings bad luck. — Saul Gorn

2 4

A question about the warnings
by Nibby Nebbulous 18 Jul '18

18 Jul '18

I apologize for bringing up this subject, but, is there any chance a patch something like this would be accepted? This is in no way because I disagree with the warning, or have any desire to have multiple systems per "asd". I just want to enjoy the lovely peacefulness of no warnings, without living in my own forked world.

1 0

ASDF recompile all files if ASD file is changed?!
by Chun Tian (binghe) 16 Jul '18

16 Jul '18

Hi ASDF list, I have some huge generated Lisp files which took a lot of time to compile into fasl files. I put the sources into my ASD system definitions with other hand-written Lisp files in parallel (thus no dependencies at all). I found that, whenever I changed the ASD definition, if I load the system by ASDF:LOAD-SYSTEM, all Lisp files will be recompiled, even their source files are not changed at all. Is this a desired feature or possible issue? Do I need to provide sample code to show this “issue”? I’m using quite a recent ASDF (version: 3.3.1.7) Regards, Chun Tian

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel July 2018