I just installed ECL from MacPorts, and when I run the test suite I get a failure.
Using ecl -norc Ran 35 tests: 34 passing and 1 failing failing test(s): test-configuration.script
Should I expect this?
best, r
On 9/13/11 Sep 13 -9:08 AM, Robert Goldman wrote:
I just installed ECL from MacPorts, and when I run the test suite I get a failure.
Using ecl -norc Ran 35 tests: 34 passing and 1 failing failing test(s): test-configuration.script
Should I expect this?
Seems like the failure arises because ECL is unhappy with this configuration string:
/foo:/bar::/baz:/quux
in that test.
Error is:
Uneven number of components in source to destination mapping: "/foo:/bar::/baz:/quux"
This is MacPorts ecl 11.1.1_0:
(lisp-implementation-version)
"11.1.1"
HtH, r
On Tue, Sep 13, 2011 at 11:18, Robert Goldman rpgoldman@sift.info wrote:
On 9/13/11 Sep 13 -9:08 AM, Robert Goldman wrote:
I just installed ECL from MacPorts, and when I run the test suite I get a failure.
Using ecl -norc Ran 35 tests: 34 passing and 1 failing failing test(s): test-configuration.script
Should I expect this?
Seems like the failure arises because ECL is unhappy with this configuration string:
/foo:/bar::/baz:/quux
in that test.
Error is:
Uneven number of components in source to destination mapping: "/foo:/bar::/baz:/quux"
This is MacPorts ecl 11.1.1_0:
(lisp-implementation-version)
"11.1.1"
Wow. What's the value of asdf::*inter-directory-separator* ? Of *features* ?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
On 9/13/11 Sep 13 -10:29 AM, Faré wrote:
On Tue, Sep 13, 2011 at 11:18, Robert Goldman rpgoldman@sift.info wrote:
On 9/13/11 Sep 13 -9:08 AM, Robert Goldman wrote:
I just installed ECL from MacPorts, and when I run the test suite I get a failure.
Using ecl -norc Ran 35 tests: 34 passing and 1 failing failing test(s): test-configuration.script
Should I expect this?
Seems like the failure arises because ECL is unhappy with this configuration string:
/foo:/bar::/baz:/quux
in that test.
Error is:
Uneven number of components in source to destination mapping: "/foo:/bar::/baz:/quux"
This is MacPorts ecl 11.1.1_0:
(lisp-implementation-version)
"11.1.1"
Wow. What's the value of asdf::*inter-directory-separator* ? Of *features* ?
asdf::*inter-directory-separator*
#;
(pprint *features*)
(:ASDF2 :ASDF :DARWIN :FORMATTER :LONG-LONG :UINT64-T :UINT32-T :UINT16-T :RELATIVE-PACKAGE-NAMES :LONG-FLOAT :DFFI :CLOS-STREAMS :CMU-FORMAT :ECL-PDE :DLOPEN :CLOS :BOEHM-GC :ANSI-CL :COMMON-LISP :IEEE-FLOATING-POINT :PREFIXED-API :FFI :I686 :COMMON :ECL)
OK, so asdf-unix must be turned on when darwin is present, even though unix is absent. And/or ECL should ensure that unix is present on darwin.
Juanjo, what is the correct behavior wrt *features* on ECL?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
On Tue, Sep 13, 2011 at 11:43, Robert Goldman rpgoldman@sift.info wrote:
On 9/13/11 Sep 13 -10:29 AM, Faré wrote:
On Tue, Sep 13, 2011 at 11:18, Robert Goldman rpgoldman@sift.info wrote:
On 9/13/11 Sep 13 -9:08 AM, Robert Goldman wrote:
I just installed ECL from MacPorts, and when I run the test suite I get a failure.
Using ecl -norc Ran 35 tests: 34 passing and 1 failing failing test(s): test-configuration.script
Should I expect this?
Seems like the failure arises because ECL is unhappy with this configuration string:
/foo:/bar::/baz:/quux
in that test.
Error is:
Uneven number of components in source to destination mapping: "/foo:/bar::/baz:/quux"
This is MacPorts ecl 11.1.1_0:
(lisp-implementation-version)
"11.1.1"
Wow. What's the value of asdf::*inter-directory-separator* ? Of *features* ?
asdf::*inter-directory-separator*
#;
(pprint *features*)
(:ASDF2 :ASDF :DARWIN :FORMATTER :LONG-LONG :UINT64-T :UINT32-T :UINT16-T :RELATIVE-PACKAGE-NAMES :LONG-FLOAT :DFFI :CLOS-STREAMS :CMU-FORMAT :ECL-PDE :DLOPEN :CLOS :BOEHM-GC :ANSI-CL :COMMON-LISP :IEEE-FLOATING-POINT :PREFIXED-API :FFI :I686 :COMMON :ECL)
On Tue, Sep 13, 2011 at 5:47 PM, Faré fahree@gmail.com wrote:
OK, so asdf-unix must be turned on when darwin is present, even though unix is absent. And/or ECL should ensure that unix is present on darwin.
ECL currently trusts the host and uses the C compiler to decide which features it turns on. Apple's compiler does not report "unix" and hence ECL also does not. I really do not know what asdf-unix means here: is it directory convention? POSIX environment? Unix-V?
Juanjo
On Tue, Sep 13, 2011 at 13:06, Juan Jose Garcia-Ripoll juanjose.garciaripoll@googlemail.com wrote:
On Tue, Sep 13, 2011 at 5:47 PM, Faré fahree@gmail.com wrote:
OK, so asdf-unix must be turned on when darwin is present, even though unix is absent. And/or ECL should ensure that unix is present on darwin.
ECL currently trusts the host and uses the C compiler to decide which features it turns on. Apple's compiler does not report "unix" and hence ECL also does not. I really do not know what asdf-unix means here: is it directory convention? POSIX environment? Unix-V?
#+asdf-unix means we have /POSIX/namestrings/ as opposed to c:\Windows\namestrings\ or MacOS 9:namestrings: or Genera:>namestrings> or what else have you. This includes cygwin and MacOS X.
In particular, under a asdf-unix environment, PATH-like variables (notably $CL_SOURCE_REGISTRY and $ASDF_OUTPUT_TRANSLATIONS) use #: as a delimiter, whereas under other environments, they use #; as a delimiter.
Am I correct that I should assume :asdf-unix when :darwin is in the *features* even though :unix isn't?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
On Tue, Sep 13, 2011 at 8:39 PM, Faré fahree@gmail.com wrote:
Am I correct that I should assume :asdf-unix when :darwin is in the *features* even though :unix isn't?
:darwin does imply Darwin operating system which does have '/'-separated pathnames and thus following your definition of :asdf-unix, the latter should be included in *features*.
Juanjo
On Tue, Sep 13, 2011 at 18:41, Juan Jose Garcia-Ripoll juanjose.garciaripoll@googlemail.com wrote:
On Tue, Sep 13, 2011 at 8:39 PM, Faré fahree@gmail.com wrote:
Am I correct that I should assume :asdf-unix when :darwin is in the *features* even though :unix isn't?
:darwin does imply Darwin operating system which does have '/'-separated pathnames and thus following your definition of :asdf-unix, the latter should be included in *features*.
OK. Robert, Juanjo, does the 2.017.5 I just pushed work for you?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
On 9/13/11 Sep 13 -8:23 PM, Faré wrote:
On Tue, Sep 13, 2011 at 18:41, Juan Jose Garcia-Ripoll juanjose.garciaripoll@googlemail.com wrote:
On Tue, Sep 13, 2011 at 8:39 PM, Faré fahree@gmail.com wrote:
Am I correct that I should assume :asdf-unix when :darwin is in the *features* even though :unix isn't?
:darwin does imply Darwin operating system which does have '/'-separated pathnames and thus following your definition of :asdf-unix, the latter should be included in *features*.
OK. Robert, Juanjo, does the 2.017.5 I just pushed work for you?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
Seems to work on all the other Mac OS X implementations I tested last time and additionally on ECL on Mac OS X. Don't have the opportunity to test on Linux right now.
Looks good to me!
Best, r
On Wed, Sep 14, 2011 at 3:23 AM, Faré fahree@gmail.com wrote:
OK. Robert, Juanjo, does the 2.017.5 I just pushed work for you?
I just "git-pull"ed the system and all seems to work with ECL on OS X.
Juanjo
-
Faré -
Juan Jose Garcia-Ripoll -
Robert Goldman