asdf-devel May 2018

asdf-devel@common-lisp.net

5 participants
6 discussions

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

06 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

New candidate patch for DEFERRED-WARNINGS on SBCL
by Robert Goldman 31 May '18

31 May '18

Many thanks to Attila and Fare for suggesting ways to rewrite my original patch. New version now available in the repo. Note: has not been tested on *old* SBCL yet: I will do that later today when I get to the office. Best, r

1 0

Fixing deferred warnings on SBCL 1.4.7+
by Robert Goldman 30 May '18

30 May '18

OK, I have pushed a better solution to gitlab on cl.net, as merge request 95. The history of this branch is a little messy, so I will squash-merge it later. But I would definitely appreciate other eyes on. I had hoped to localize the fix, but it was too hard for me -- getting it right involved excruciatingly complex dealing with evaluation at read, compile, and load times, and the difference between loading ASDF as a big single file and as an ASDF system itself. I'll plan to merge this into master at the end of the week unless I hear some screams before then. P.S. I created a milestone for a bug fix release, but mis-named it, and I don't seem to be able to edit it. 😜 Cheers, r

1 0

Deferred warnings broken on SBCL 1.4.7
by Eric Timmons 30 May '18

30 May '18

Looks like SBCL 1.4.7 changed the slots of sb-c::compiler-error-context (in particular enclosing-source -> %enclosing-source, source -> %source, and original-source was removed). As a result, deferred warnings are broken. Attached is the output of `./run-tests.sh sbcl test-deferred-warnings.script` -Eric

3 8

Re: asdf-announce post from nimiux@gentoo.org requires approval
by Faré 05 May '18

05 May '18

Chema Alonso asked: > Where can I download the 3.3.2 tarball? > > Normally I get it from here: > > https://common-lisp.net/project/asdf/archives/ > > But I can't find it right now. > > Thanks. > I took the liberty of running "make archive publish-archive" from the release branch. The tarballs should now all be present. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org The hacker: someone who figured things out and made something cool happen. — Alan Schmitt

1 0

ASDF 3.3.2 Released
by Robert Goldman 04 May '18

04 May '18

Today we release ASDF 3.3.2, the second bugfix release for the 3.3 release series. Of primary interest in this release are 1. Multiple fixes in handling misnamed (or "legacy-named," if you prefer) secondary systems ("foo-test" instead of "foo/test"). Thanks to Eric Timmons, there is also a similar fix for package-inferred-systems. 2. Fix an annoying warning message for compute-action-stamp. 3. Add support for the Mezzano implementation (thanks to E. Housel, H. Harrington). 4. Miscellaneous minor fixes and documentation tweaks. We urge implementations that are currently bundling previous versions of ASDF -- and especially those bundling 3.3.0 or 3.3.1 -- to upgrade to 3.3.2 at their earliest convenience. Immense thanks, as always, to Fare Rideau. Also thanks to the many bug reporters and patch submitters (see the Changelog), and to Anton Vodonosov and Dave Cooper for help with testing. Here is the changelog entry for 3.3.2: cl-asdf (2:3.3.2-1) unstable; urgency=low Bug fix release: * Dependency tracking: fix bugs in handling misnamed secondary systems. We now distinguish between "syntactic" and "semantic" primariness, properly warn in case a secondary system is misnamed, yet properly recompile or avoid spurious recompilation depending on whether there or not is a conflict or redefinition. Similarly handle package-inferred-system (thanks to Eric Timmons). Better warning in a fishy case of compute-action-stamp. * UIOP: Add package location information to define-package on SBCL. * Upgrade: fix issue with asdf/bundle. * Portability: add support for Mezzano (thanks to E. Housel, H. Harrington) * Documentation: add discussion of best practices. * Package-inferred system: Improve source file handling. * Test and documentation improvements. -- Francois-Rene Rideau <fare(a)tunes.org> Thu, 03 May 2018 22:46:19 -0400

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel May 2018