Re: [asdf-devel] prepare-op

2012-12-18 Thread Christophe Rhodes
Faré fah...@gmail.com writes: I recommend the future use of (:file x86-64-vm :if-feature (:and :sbcl :x86-64)) Thanks very much. Cheers, Christophe ___ asdf-devel mailing list asdf-devel@common-lisp.net

Re: [asdf-devel] prepare-op

2012-12-18 Thread Zach Beane
Faré fah...@gmail.com writes: On Mon, Dec 17, 2012 at 2:19 PM, Christophe Rhodes cs...@cantab.net wrote: Zach Beane x...@xach.com writes: Faré fah...@gmail.com writes: OK, this is now committed as of ASDF 2.26.21 and POIU 1.29.3. It's slightly smaller, it's much cleaner, and it all works.

Re: [asdf-devel] prepare-op

2012-12-18 Thread Faré
On Tue, Dec 18, 2012 at 8:46 AM, Zach Beane x...@xach.com wrote: Faré fah...@gmail.com writes: On Mon, Dec 17, 2012 at 2:19 PM, Christophe Rhodes cs...@cantab.net wrote: Zach Beane x...@xach.com writes: Faré fah...@gmail.com writes: OK, this is now committed as of ASDF 2.26.21 and POIU

Re: [asdf-devel] prepare-op

2012-12-18 Thread Zach Beane
Faré fah...@gmail.com writes: It works for me. I suspect you might not have compiled sb-md5 from clean, and due to that bug I fixed in 2.26.9 which required a substantial refactoring, ASDF can now see that file was not up-to-date, when it couldn't see it earlier. Can you recompile this

Re: [asdf-devel] prepare-op

2012-12-18 Thread Zach Beane
Zach Beane x...@xach.com writes: Faré fah...@gmail.com writes: It works for me. I suspect you might not have compiled sb-md5 from clean, and due to that bug I fixed in 2.26.9 which required a substantial refactoring, ASDF can now see that file was not up-to-date, when it couldn't see it

Re: [asdf-devel] prepare-op

2012-12-18 Thread Faré
It works for me. I suspect you might not have compiled sb-md5 from clean, and due to that bug I fixed in 2.26.9 which required a substantial refactoring, ASDF can now see that file was not up-to-date, when it couldn't see it earlier. Can you recompile this contrib from clean, either in

Re: [asdf-devel] prepare-op

2012-12-18 Thread Zach Beane
Faré fah...@gmail.com writes: sb-md5 hasn't been modified in years, but it depends on sb-rotate-byte which was just tweaked because of :if-component-dep-fails. ASDF used to not propagate timestamps from system to system, or from .asd file to the system internals, but now it does both, and so

Re: [asdf-devel] prepare-op

2012-12-18 Thread Zach Beane
Faré fah...@gmail.com writes: Ok, I updated to the latest SBCL sources, did this: sh clean.sh sh make.sh sudo sh install.sh Then I change to the ASDF directory and do this: sbcl --non-interactive --no-userinit --load asdf.lisp --eval (require :sb-md5) I still get the

Re: [asdf-devel] prepare-op

2012-12-18 Thread Zach Beane
Faré fah...@gmail.com writes: Oh: It work for me in SLIME but I can reproduce the issue with your command-line. I'll investigate some more. My apologies for the frustration. Great, I look forward to the diagnosis and cure! Zach ___ asdf-devel

Re: [asdf-devel] prepare-op

2012-12-18 Thread Faré
OK, I understand the bug that Xach found: There was an ancient bug whereby input-files for a module always returned a singleton list containing the module's component-pathname, its directory. That wasn't an issue then due to the even greater deep design flaw of timestamps not being propagated.

Re: [asdf-devel] prepare-op

2012-12-18 Thread Faré
On Tue, Dec 18, 2012 at 5:01 PM, Faré fah...@gmail.com wrote: OK, I understand the bug that Xach found: There was an ancient bug whereby input-files for a module always returned a singleton list containing the module's component-pathname, its directory. That wasn't an issue then due to the

Re: [asdf-devel] prepare-op

2012-12-17 Thread Zach Beane
Faré fah...@gmail.com writes: OK, this is now committed as of ASDF 2.26.21 and POIU 1.29.3. It's slightly smaller, it's much cleaner, and it all works. I hope I have not broken users — please test. Casualties of the cleanup were :feature and :if-component-dep-fails. They were just horrible

Re: [asdf-devel] prepare-op

2012-12-17 Thread Faré
Casualties of the cleanup were :feature and :if-component-dep-fails. They were just horrible things. FYI, the sb-rotate-byte contrib in SBCL uses :if-component-dep-fails. I've contacted the SBCL maintainers. Hopefully they will revert to #+x86-64 and such until a new asdf is universal. But

Re: [asdf-devel] prepare-op

2012-12-17 Thread Stas Boukarev
Faré fah...@gmail.com writes: Casualties of the cleanup were :feature and :if-component-dep-fails. They were just horrible things. FYI, the sb-rotate-byte contrib in SBCL uses :if-component-dep-fails. I've contacted the SBCL maintainers. Hopefully they will revert to #+x86-64 and such

Re: [asdf-devel] prepare-op

2012-12-17 Thread Christophe Rhodes
Zach Beane x...@xach.com writes: Faré fah...@gmail.com writes: OK, this is now committed as of ASDF 2.26.21 and POIU 1.29.3. It's slightly smaller, it's much cleaner, and it all works. I hope I have not broken users — please test. Casualties of the cleanup were :feature and

Re: [asdf-devel] prepare-op

2012-12-17 Thread Faré
On Mon, Dec 17, 2012 at 2:19 PM, Christophe Rhodes cs...@cantab.net wrote: Zach Beane x...@xach.com writes: Faré fah...@gmail.com writes: OK, this is now committed as of ASDF 2.26.21 and POIU 1.29.3. It's slightly smaller, it's much cleaner, and it all works. I hope I have not broken users

Re: [asdf-devel] prepare-op

2012-12-14 Thread Faré
OK, this is now committed as of ASDF 2.26.21 and POIU 1.29.3. It's slightly smaller, it's much cleaner, and it all works. I hope I have not broken users — please test. Casualties of the cleanup were :feature and :if-component-dep-fails. They were just horrible things. Another, disabled, :feature