[asdf-devel] asdf-encodings?
![](https://secure.gravatar.com/avatar/9342d16e648d947803f4af8f1e6a4871.jpg?s=120&d=mm&r=g)
Is this the right place to talk about asdf-encodings? Apologies if this is the wrong place. One minor issue with asdf-encodings and cmucl: It looks like find-implementation-encoding does not expect an error for unknown encodings, so for cmucl, the implementation should be #+cmu (ignore-errors (stream::find-external-format encoding)) Also, once asdf-encodings is loaded, compiles with asdf fail because cl:compile-file is called with :external-format set to the external format object instead of the name. To get the name from the object, use (stream::ef-name obj). I don't know where that should be applied. BTW, make test lisp=cmucl CMUCL=cmulisp passes 41 tests, but there are some warnings like loading level1/file1 Warning: compiling #<STATIC-FILE "test-module-pathnames" "sources/level1" "level2/static.file"> completed without its input file #P"/home/rtoy/src/clnet/asdf/test/sources/level1/level2/static.file" Don't know if that's significant or not. Ray
![](https://secure.gravatar.com/avatar/0345f6261d6ced21145afdec166fd114.jpg?s=120&d=mm&r=g)
On Tue, Jan 15, 2013 at 12:27 PM, Raymond Toy <toy.raymond@gmail.com> wrote:
Is this the right place to talk about asdf-encodings? Apologies if this is the wrong place.
This is the right place indeed.
One minor issue with asdf-encodings and cmucl: It looks like find-implementation-encoding does not expect an error for unknown encodings, so for cmucl, the implementation should be
#+cmu (ignore-errors (stream::find-external-format encoding))
Yes, I discovered as much while running the recently enhanced asdf's test-encodings and put an ignore-errors around the whole thing, for all implementations.
Also, once asdf-encodings is loaded, compiles with asdf fail because cl:compile-file is called with :external-format set to the external format object instead of the name. To get the name from the object, use (stream::ef-name obj). I don't know where that should be applied.
I tried something and it looks like it passes the test-encodings test.
BTW, make test lisp=cmucl CMUCL=cmulisp
passes 41 tests, but there are some warnings like
loading level1/file1 Warning: compiling #<STATIC-FILE "test-module-pathnames" "sources/level1" "level2/static.file"> completed without its input file #P"/home/rtoy/src/clnet/asdf/test/sources/level1/level2/static.file"
There's some magic in some old tests that I haven't tried to figure out - I don't know who set up those directories, but apparently, some static files are expect that were removed or never committed, but that didn't use to cause problems when those files were ignored, which they are not anymore now that timestamps take them into account. I added the files, and it seems to have hushed the tests. Speaking of tests, I just added a 42nd test, but it fails on cmucl: the hello-world-example for producing a standalone program. My dump attempt has these errors, using an image from your distribution on a not-so-fresh ubuntu machine (to be upgraded RSN): [Saving current lisp image as executable into "/home/tunes/cl/asdf/test/hello-world-example": [Writing core objects Read-Only: 27735760 bytes... Static: 4499880 bytes... Dynamic: 8192 bytes... done] Linking executable... [/ita/local/bin/./../lib/cmucl/lib/linker.sh: linking /home/tunes/cl/asdf/test/hello-world-example... /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.3/../../../libdl.so when searching for -ldl /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.3/../../../libdl.a when searching for -ldl /usr/bin/ld: skipping incompatible /usr/lib/libdl.so when searching for -ldl /usr/bin/ld: skipping incompatible /usr/lib/libdl.a when searching for -ldl /usr/bin/ld: cannot find -ldl collect2: ld returned 1 exit status done] —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org "Anything created must necessarily be inferior to the essence of the creator." — Claude Shouse (shouse@macomw.ARPA) "Einstein's mother must have been one heck of a physicist." — Joseph C. Wang (joe@athena.mit.edu)
![](https://secure.gravatar.com/avatar/9342d16e648d947803f4af8f1e6a4871.jpg?s=120&d=mm&r=g)
"Fare" == Far <Far> writes:
Fare> On Tue, Jan 15, 2013 at 12:27 PM, Raymond Toy Fare> <toy.raymond@gmail.com> wrote: >> Is this the right place to talk about asdf-encodings? >> Apologies if this is the wrong place. >> Fare> This is the right place indeed. >> One minor issue with asdf-encodings and cmucl: It looks like >> find-implementation-encoding does not expect an error for >> unknown encodings, so for cmucl, the implementation should be >> >> #+cmu (ignore-errors (stream::find-external-format encoding)) >> Fare> Yes, I discovered as much while running the recently Fare> enhanced asdf's test-encodings and put an ignore-errors Fare> around the whole thing, for all implementations. >> Also, once asdf-encodings is loaded, compiles with asdf fail >> because cl:compile-file is called with :external-format set to >> the external format object instead of the name. To get the >> name from the object, use (stream::ef-name obj). I don't know >> where that should be applied. >> Fare> I tried something and it looks like it passes the Fare> test-encodings test. Cool. I try it out again sometime later. Fare> Speaking of tests, I just added a 42nd test, but it fails on Fare> cmucl: the hello-world-example for producing a standalone Fare> program. Fare> My dump attempt has these errors, using an image from your Fare> distribution on a not-so-fresh ubuntu machine (to be Fare> upgraded RSN): My build machine is an ancient OpenSuSE 11.x box. Your's is way more up-to-date than mine. :-) But based on the warnings, I'm guessing that you don't have the 32-bit development system installed. That's required since cmucl is still a 32-bit app. Ray
participants (2)
-
Faré
-
Raymond Toy