asdf-devel

asdf-devel@common-lisp.net

1 participants
1378 discussions

[asdf-devel] using uiop standalone
by Anton Vodonosov 08 Apr '15

08 Apr '15

Hello. If I want to use uiop tools, for example run-program, can I use the newest uiop without upgrading ASDF, or it should be only used with corresponding ASDF version? I mean, uiop is included in Quicklisp, I can add :depends-on uiop, but will it affect the ASDF version shipped with my CL implementation? Is it safe to load new uiop with any ASDF? BTW, is the uiop-3.0.3.tgz included into the recent Quicklisp 2014-02-11 is the latest version of uiop? Best regards, - Anton

2 1

[asdf-devel] Yes proglogue and epilogue is used!
by Jean-Claude Beaudoin 08 Apr '15

08 Apr '15

Hello Faré, Yes the prologue and epilogue is (or will be, in the publicly and officially sanctioned ASDF-way once I send you my small MKCL mods for ASDF 3) used after all. Maybe not really by ECL, although it should, but by MKCL. It is an essential part of the program-op processing. You are right about the fact that prologue and epilogue are not very well designed as they stand in ECL (and how MKCL inherited them from ECL). But they really make sense if they are considered in the context of #'compiler:build-program. I would even say that they are essential in the context of #'compiler:build-program. I am currently putting the finishing touch to ASDF 3.0.3 on MKCL 1.1.7 on Windows (3 more tests to fix). I should be done somewhat shortly and after that I'll sent the ASDF list what I have got, merged with ASDF head. Sorry if I could not reply to your ecls-list messages more promptly but I was out all day participating in a double fencing tournament. I did basically a somewhat marathon-like 8 hours straight of competitive épée, so I hope you will understand if I stand a bit out of phase with my computer keyboard for a few more hours while I try to recover. Cheers, Jean-Claude Beaudoin

2 1

[asdf-devel] Further customization of output translations
by Stelian Ionescu 08 Apr '15

08 Apr '15

How would I go about including the git branch in the output directory name ? -- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib

3 2

[asdf-devel] Quick question about the bundle op
by Robert P. Goldman 08 Apr '15

08 Apr '15

I see that the BUNDLE-PATHNAME-TYPE for :dll is "so" on all unixes. Question: should this be "dylib" on Mac OS X instead? Thanks, r

2 1

[asdf-devel] current failures for CCL Windows and SBCL Windows
by Dave Cooper 08 Apr '15

08 Apr '15

Here are the output text files for these platforms, currently: SBCL: https://www.dropbox.com/s/lky1wlz0o1ku7qt/sbcl.text CCL: https://www.dropbox.com/s/ptoor8nepik85by/ccl.text What else should I be testing for Windows?

1 0

[asdf-devel] 3.0.2.7 follows hot on the heels of 3.0.2.6
by Robert P. Goldman 08 Apr '15

08 Apr '15

Faré points out that /usr/bin/env can only be used on Unix.... Patch pushed!

1 0

[asdf-devel] Are there nightly builds for trunk sources? (was: Re: CCL Windows: output from ccl:fasl-concatenate is "not a FASL file")
by Genworks Support 08 Apr '15

08 Apr '15

So this has been fixed (almost immediately after I opened the Trac ticket http://trac.clozure.com/ccl/ticket/1109!) in the trunk in: http://trac.clozure.com/ccl/changeset/15892 Now I am wondering how often the binaries (e.g. wx86cl.exe) in http://svn.clozure.com/publicsvn/openmcl/trunk/windows/ccl get rebuilt? Is there a nightly build so that I can simply do an svn update on this, or is it time to get set up with gcc on Windows and perform the Windows build of the trunk myself, in order to test this? Regards, Dave On Wed, Sep 4, 2013 at 4:36 PM, Dave Cooper <david.cooper(a)genworks.com>wrote: > > So I'm trying to get the ASDF test suite running on Windows, and tracked > this down as one of the failures for CCL (32-bit and 64-bit). (there were 5 > failures out of 47 tests, I haven't looked at the rest yet). > > This can be replicated as follows (with files from > > https://www.dropbox.com/sh/jc2cqwpkp06dupm/7lgyRUdwZ5/cl/tests/simple > ): > > > [below, substitute ".../'" for your actual path to the test files]: > > > > (lisp-implementation-version) > "Version 1.9-r15765 (WindowsX8664)" > > > (compile-file ".../try1") > > > (compile-file ".../try2") > > > (ccl:fasl-concatenate ".../try.wx64fsl" (list ".../try1.wx64fsl" > ".../try2.wx64fsl")) > > > (load ".../try.wx64fsl") > > ERROR: Not a FASL file. > > > Does anyone recognize what might be going on? > > > -- > My Best, > > Dave Cooper, Genworks Support > david.cooper(a)genworks.com, dave.genworks.com(skype) > USA: 248-327-3253(o), 1-248-330-2979(mobile) > UK: 0191 645 1699 > -- My Best, Dave Cooper, Genworks Support david.cooper(a)genworks.com, dave.genworks.com(skype) USA: 248-327-3253(o), 1-248-330-2979(mobile) UK: 0191 645 1699

1 0

[asdf-devel] Checking system names...... NOT
by Robert P. Goldman 08 Apr '15

08 Apr '15

Faré and James Anderson have convinced me I'm tilting at windmills here. I am in the process of reverting the checks and testing the results to make sure that I haven't messed up in the reversion process. Look for a 3.1.0.76 as soon as I'm sure the tests all pass. Bloodied, but unbowed, R

1 0

Re: [asdf-devel] Possible problem with check-compile-results
by Faré 08 Apr '15

08 Apr '15

You'd have to post the stack trace for us to tell. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org On Sat, Aug 24, 2013 at 5:02 PM, Robert Goldman <rpgoldman(a)sift.net> wrote: > Yes, the underlying problem was a version skew. But I was wondering if this problem tickled a problem in the way that ASDF (UIOP) bundles up errors and re-signals them. > > Best, > r >

1 0

Re: [asdf-devel] Alternate default lisp system location
by Daniel Herring 08 Apr '15

08 Apr '15

On Wed, 12 Mar 2014, Faré wrote: > 1- I think we should proceed and add a default path anyway. > ~/cl/ and/or ~/common-lisp/ sound fine to me, and I've seen no one > complain about that. > You could make it ~/local/common-lisp/ if you're into larger paths. The computer I'm currently on uses ~/lisp for a lot of non-ASDF-related systems, including numerous files that are not source code. On some other systems, I use paths like ~/cl to distinguish from ~/racket and other dialects. I agree with others who dislike this idea. ASDF will inflict significant end-user pain for little benefit if it chooses to do a land grab on an obvious directory name. In my opinion, a lot of the complexity in ASDF, and a lot the motivation for this proposal, stems from ASDF's conflation of the "loader" with the "build system". That's the topic for another post... - Daniel

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

asdf-devel