Dear ABCL developers,
I apologize if this is not the right channel for this kind of request, but I'd like to suggest the following change to src/org/armedbear/lisp/Lisp.java (for CFFI to identify the platform properly on MacOSX).
@@ -2378,9 +2378,9 @@ } // Processor architecture if(osArch != null) { - if (osArch.equals("amd64")) + if (osArch.equals("amd64")||osArch.equals("x86_64")) featureList = new Cons(Keyword.X86_64, featureList); - else if (osArch.equals("x86")) + else if (osArch.equals("x86")||osArch.equals("i386")) featureList = new Cons(Keyword.X86, featureList); } Symbol.FEATURES.initializeSpecial(featureList);
Also, there is a problem with contrib/jfli/test/yanking.lisp, there is a referece to abclidea:*lisp-dir* and that package is not part of ABCL. As a workaround I've changed contrib/jfli/jfli.asd to remove the (:module test :components ((:file "yanking")).
Best regards,
Carlos
On Mon, Nov 26, 2012 at 3:11 PM, Mark Evenson evenson@panix.com wrote:
Overall, I think we are more-or-less ready to release the long awaited abcl-1.1.0 with the exception of resolving the outstanding ANSI regression failures.
I have moved all previously outstanding issues to the abcl-1.1.1 milestone, and I have added as three blocker tickets to the abcl-1.1.0 milestone to decide on what to do.
http://trac.common-lisp.net/armedbear/ticket/265 http://trac.common-lisp.net/armedbear/ticket/266 http://trac.common-lisp.net/armedbear/ticket/267
For each of these issues, I have identified the changeset that caused the regression via bisecting the source tree. If the result of the bisection is correct, all three issues should be relatively easy to track down, as "not much happened" in the commits. But maybe something was screwy in my process (I did it "on the road" from an iPad ssh client last week in a non-traditional--for me--working environment).
Additionally, we should probably check the Novemeber Quicklisp test reports to see if anything has been broken. I seem to see a problem with Hunchentoot under SLIME regarding the PATHNAME reader, but this may be something local to me.
I need to finish writing up the CHANGES, and make a quick pass through the manual, updating the grovelled docstring sections.
Hopefully, we can have a quick consultation on #abcl tonight at 2100 CST to see if these plans make sense.
-- "A screaming comes across the sky. It has happened before but there is nothing to compare to it now."
armedbear-devel mailing list armedbear-devel@common-lisp.net http://lists.common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel