Hi,<br><br>Continuing from a previous discussion I was having directly with Luigi Panzeri about this issue.&nbsp; I was having problems with unknown foreign type errors.<br><br>I&#39;m running Leopard (10.5.1) on a PowerBook G4 under SBCL 
v.1.0.2<br><br>I&#39;ve quoted his initial response.&nbsp; He suggested I ask here to see if someone else has the solution, though my initial problem was solved by his suggestion.&nbsp; I&#39;ve run into a new problem though.<br><br>
<div class="gmail_quote">On Jan 18, 2008 10:50 AM, Luigi Panzeri &lt;<a href="mailto:matley@muppetslab.org">matley@muppetslab.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
asdf-install should work fine. I have to admit that i have not tested<br>&nbsp;cl-objc on a powerpc with leopard yet, though i don&#39;t think it is<br>related to that. Maybe if you send email to cl-objc mailing list [1]<br>someone else can also help you.
<br><br>At any rate, I think that the problem is due to an older version of<br>cffi you are using. Try to use the darcs repository [2] or a more<br>recent tarball, as in older version ( &lt; April 2007 IIRC) the interface
<br>for defining foreign type is changed.</blockquote><div>&nbsp;</div><div>This was the source of the type error messages, but when I fixed that and tried again, I got these errors from SBCL:<br><br>==== START OF LOG ====<br>
Compiling CLOS bindings for Appkit framework in /usr/local/lib/sbcl/site/cl-objc/src/frameworks/Appkit-CLOS.lisp<br>Control stack guard page temporarily disabled: proceed with caution<br><br>debugger invoked on a SB-KERNEL::CONTROL-STACK-EXHAUSTED:
<br>&nbsp; Control stack exhausted (no more space for function call frames).&nbsp; This is probably due to heavily nested or infinitely recursive function calls, or a tail call that SBCL cannot or has not optimized away.<br><br>Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
<br><br>restarts (invokable by number or by possibly-abbreviated name):<br>&nbsp; 0: [RETRY ] Retry performing #&lt;ASDF:LOAD-OP NIL {11ABD101}&gt; on<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; #&lt;ASDF:CL-SOURCE-FILE &quot;generate-frameworks-bindings&quot; {11AC19A9}&gt;.
<br>&nbsp; 1: [ACCEPT] Continue, treating #&lt;ASDF:LOAD-OP NIL {11ABD101}&gt; on<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; #&lt;ASDF:CL-SOURCE-FILE &quot;generate-frameworks-bindings&quot; {11AC19A9}&gt;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; as having been successful.<br>
&nbsp; 2: [RETRY ] Retry installation<br>&nbsp; 3: [ABORT ] Exit debugger, returning to top level.<br>==== END OF LOG ====<br><br>Retrying does nothing to help with this problem, and even eventually leads to bad memory accesses on the part of SBCL, and an eventual seg fault.
<br><br>Oh yeah, I&#39;m using ASDF-Install to install Cl-ObjC by running the following in SBCL:<br><br>(require &#39;asdf)<br>(require &#39;asdf-install)<br>(asdf-install:install &#39;cl-objc)<br></div></div><br>
Anyone have any idea what might be the problem?<br><br>Thanks,<br>Jeremy Shoemaker<br>