Warnings during tests are OK.
These particular warnings are relatively recent (definitely something from the asdf3 days), but are not damning. ASDF 3 has learned to work around a whole lot of weirdness in the way implementations handle pathnames (or fail to handle them, as it all too often happens).
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Your conscience never stops you from doing anything. It just stops you from enjoying it.
On Wed, Oct 23, 2013 at 10:53 PM, Raymond Toy toy.raymond@gmail.com wrote:
"Robert" == Robert Goldman rpgoldman@sift.net writes:
Robert> Dear Lisp hackers, Robert> I am pleased to announce the release of ASDF 2.26. Robert> Since previous release 2.25, the changes are as follows:I assume you really meant 3.0.3 and not 2.26. :-)
I ran the tests and they all passed. However, I noticed there were some warnins such as the one appended below. I don't remember if these happened before or not.
Ray
Testing: test-utilities.script cmulisp -noinit -batch -eval "'(#.(load(string'|script-support.lisp|))#.(asdf-test::load-asdf)#.(asdf-test::frob-packages)#.(asdf-test::with-test()(load(string'|test-utilities.script|))))" ; Loading #P"/Volumes/share2/src/clnet/asdf/test/script-support.lisp". ; Loading #P"/Volumes/share2/src/clnet/asdf/build/fasls/cmucl/asdf.sse2f". Configuring ASDF Enabling debugging Being a bit verbose Comparing directories ASDF-TEST:*TEST-DIRECTORY* and ASDF-TEST::X both evaluate to same path: #P"/Volumes/share2/src/clnet/asdf/test/" Frob packages ; Loading #P"/Volumes/share2/src/clnet/asdf/test/test-utilities.script". Warning: These two expressions yield pathname-equal yet not equal path the first expression (NTH 0 (SPLIT-NATIVE-PATHNAMES-STRING (JOIN-NAMESTRINGS '("foo" "bar")))) yields this: #P"foo" (:HOST "" :DEVICE NIL :DIRECTORY NIL :NAME "foo" :TYPE :UNSPECIFIC :VERSION NIL)
the other expression (NTH 0 '(#P"foo" #P"bar")) yields that:#P"foo" (:HOST "" :DEVICE NIL :DIRECTORY NIL :NAME "foo" :TYPE NIL :VERSION NIL)