I specifically don't update cl-ppcre.asd, so that these messages annoy as
many people as possible and they complain to ASDF. cl-ppcre/test works
perfectly fine, nobody calls find-system on it, it's only ever used
via (asdf:test-system :cl-ppcre), which still works.
ASDF is an entrenched monopoly,
On Fri, Jun 22, 2018 at 5:13 PM Robert Goldman wrote:
> I have a library that provides DEF-UNIMPLEMENTED as a macro for defining
> stub functions. When you compile a file with unimplemented functions, you
> get a warning of the type FOO:UNIMPLEMENTED-STUB in my library FOO.
>
> I'd like to put in
The systems working on older asdf versions is wrong?
On Wed, Oct 18, 2017 at 8:48 PM Faré wrote:
> On Wed, Oct 18, 2017 at 12:58 PM, Stas Boukarev
> wrote:
> > ASDF keeps inventing good reasons all the time...
> >
> Indeed , "inventing" in the origin
quite subtle to debug about a year
> >> ago, and it fell out of my working cache.
> >>
> >> Is there anything special you do between A and B except a :depends-on ?
> >>
> >> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> >>
No clear-system in sight, everything is declarative.
On Wed, Oct 18, 2017 at 4:42 PM Faré wrote:
> On Wed, Oct 18, 2017 at 9:25 AM, Chream iz wrote:
> > Hi, I am also getting this error when trying to run (asdf:test-system
> ).
> > It is also not finding the test-files but that might be an
uot; document?
> https://github.com/fare/asdf/blob/master/doc/best_practices.md
>
> —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics•
> http://fare.tunes.org
> Don't forget your daily prayer to Baah-kup,
> the God of data storage and recovery!
>
>
>
> On Wed,
More new warnings from ASDF 3.3, this time I have no idea what it means.
WARNING:
Computing just-done stamp in plan NIL for action
(ASDF/LISP-ACTION:LOAD-OP
"system"), but
dependency (ASDF/FIND-SYSTEM:DEFINE-OP
"system") wasn't done yet!
Th
ave plenty. But maybe that should be done before
introducing new warnings.
On Thu, Oct 12, 2017 at 2:05 PM Faré wrote:
> On Thu, Oct 12, 2017 at 6:00 AM, Stas Boukarev wrote:
> > I get 12 warnings with "System definition file contains definition for
> > system . Please onl
sp version bundled with SBCL to have them disabled by
default.
And if some future version of ASDF stops loading any of the 12 libraries,
then I just won't update SBCL to that ASDF version.
On Thu, Oct 12, 2017 at 5:22 AM Faré wrote:
> On Wed, Oct 11, 2017 at 9:14 PM, Stas Boukarev wrote
3.3.0 issues a barrage of new warnings about something it has decided is
uncouth now.
I really have no wish to stare at these warnings coming from third party
libraries, especially since they're never going to be fixed.
Is the old behavior posing problems? Is the old behavior going away soon?
This
Robert Goldman writes:
> On 3/21/16 Mar 21 -3:01 PM, Jason Miller wrote:
>> Mingw translates command-line arguments that look like a path into
>> windows style pathnames if the DLL is present.
>
> I'm wondering what happens if you have a Lisp running under Mingw.
> Might the environment variables
Stas Boukarev writes:
> Robert Goldman writes:
>
>> On 3/21/16 Mar 21 -9:34 AM, Stas Boukarev wrote:
>>> I never liked the idea of cygwin, mingw (via msys2) seems to be
>>> working pretty well for me.
>>
>> Any chance you could grab a copy of th
Robert Goldman writes:
> On 3/21/16 Mar 21 -9:34 AM, Stas Boukarev wrote:
>> I never liked the idea of cygwin, mingw (via msys2) seems to be
>> working pretty well for me.
>
> Any chance you could grab a copy of the git repo and run the tests on
> Windows?
>
>
I never liked the idea of cygwin, mingw (via msys2) seems to be
working pretty well for me.
On Mon, Mar 21, 2016 at 5:32 PM, Robert Goldman wrote:
> On 3/21/16 Mar 21 -8:59 AM, Stas Boukarev wrote:
>> On Mon, Mar 21, 2016 at 4:16 PM, Robert Goldman wrote:
>>> On 3/20/16 Mar
On Mon, Mar 21, 2016 at 4:16 PM, Robert Goldman wrote:
> On 3/20/16 Mar 20 -7:07 PM, Stas Boukarev wrote:
>
>> Then I guess SBCL holding back on ASDF upgrades is a good strategy after all.
>>
> Actually, no.
>
> The state of affairs on Windows is no worse than befo
On Sun, Mar 20, 2016 at 11:23 PM, Robert Goldman wrote:
> I can set the configuration properly from an environment variable.
>
> But there are a number of tests that then reach out into the environment
> and try to reconfigure the source or otherwise read information.
>
> These are test-program.sc
Brett van de Sande writes:
> Two things:
>
> The links to asdf-devel and asdf-announce on
> http://common-lisp.net/project/asdf/#mailing-lists
> are dead.
That's a feature.
> Also, how do I unsubscribe?
By sending a message to asdf-devel+unsubscr...@common-lisp.net
--
With best regards, Stas.
Faré writes:
> On Tue, Apr 30, 2013 at 10:30 AM, Stas Boukarev wrote:
>>
>> I also have a file /foo, if that m
>
> Yes, that probably matters. I don't remember exactly how things go,
> but I believe that what's going on is that ASDF by default gets
> truen
Faré writes:
> Works for me. Weird. Which version of SBCL are you using?
I also have a file /foo, if that matters.
--
With best regards, Stas.
Faré writes:
> Works for me. Weird. Which version of SBCL are you using?
1.1.6.14-76e4485
--
With best regards, Stas.
Faré writes:
> Dear Lisp hackers,
>
> I'd like to release ASDF 3.0 next week (maybe even later this week).
> Can you test ASDF before I do?
I get asdf-pathname-test.script failure on SBCL:
"
These two expressions yield paths that are not pathname-equal
the first expression (RESOLVE-LOCATION '("/f
Faré writes:
>>>: Dave Cooper
>>> I have a little utility which emits the .asd files for me, with a form like:
>>>
>>> `(asdf:defsystem ,(something-to-make-my-system-name) :description "blah"
>>> … )
>>>
> If you print that form while *package* is bound to something that uses ASDF,
> (such as A
Dave Cooper writes:
> So I am using ASDF 2.31 which puts the symbol "defsystem" into
> asdf/defsystem package instead of plain asdf package (Franz already
> includes ASDF 2.31 in their patches for Allegro CL).
>
> I have a little utility which emits the .asd files for me, with a form like:
>
>
Gary King writes:
> An admittedly quick look at the source didn't ring any bells for me.
(setf asdf:*warnings-file-type* nil)
--
With best regards, Stas.
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://lists.common-lisp.net/cgi-bin/mail
Faré writes:
> Many people have suggested making the ASDF 2.27 release an ASDF 3.0
> release instead.
>
> I was previously hesitant, wanting to signal that I preserve
> compatibility, and not making it a release that doesn't preserve
> version-satisfies, since the major number is different. But I
Faré writes:
> ABCL hackers: is there such a thing as getcwd in ABCL,
> and if so how do I get to it?
(jstatic "getProperty" "java.lang.System" "user.dir")
--
With best regards, Stas.
___
asdf-devel mailing list
asdf-devel@common-lisp.net
http://list
Faré 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 until a
27 matches
Mail list logo
