Begin forwarded message:

From: Samantha Atkins <sjatkins@mac.com>
Date: March 25, 2007 4:34:05 PM PDT
To: Brian Mastenbrook <brian@mastenbrook.net>
Subject: Re: [Sbcl-help] Apparent trouble with dlopen, OS X 10.4.9, sbcl 1.0.2


On Mar 25, 2007, at 2:14 PM, Brian Mastenbrook wrote:

It's not a matter of recognition. ASDF is passing terminal_glue.c to your C
compiler, and it looks like your C compiler produced a PPC .so.


Hmm.  It doesn't usually.  How is it invoked in this case?  Perhaps some environment variables used by sbcl or uffi are wrong?  Interestingly I seed that HOSTTYPE is set to powerpc on both the macbook, where everything works, and on the Mac Pro where it doesn't.  So that variable can be the problem.  But another might be.

Is there any possibility that you're using a networked file system for your
home directory, and compiled the object on a PPC machine.

It is not a networked file system but I did inherit a fair amount in my home directory from a previously owned G5 (ppc) system.   But the ~/.site and such is fresh.


Or you copied your
home directory from an earlier PPC machine? What happens when you just
remove the .so and let it get recompiled?


Same thing happens.

Also, is there any possibility you have a very old set of Xcode tools
installed?


No.  Fresh Tiger install with full 10.4.9 upgrades.

Thanks for the thoughts.

- samantha




On 3/25/07 3:03 PM, "Samantha Atkins" <sjatkins@mac.com> wrote:

How should this rebuilding be done exactly?  On the macbook the file
was build as an i386 .so automatically.  Even if I rebuild this one
properly by hand aren't I likely to run into similar situations in
the future?  Anyone know why the arch would not be correctly
recognized on a Mac Pro?

- samantha


On Mar 25, 2007, at 7:57 AM, Cyrus Harmon wrote:

Are you saying that opening the ppc library worked fine on the
macbook?

The solution is to rebuild your terminal_glue.so for x86.

Cyrus

On Mar 25, 2007, at 1:46 AM, Samantha Atkins wrote:

One other possibly relevant detail is that I am on a Mac Pro when
this happens.  I tried the exact same thing on my Macbook,  also
under OS X 10.4.9, and it worked fine.  Hmm.

- s

On Mar 25, 2007, at 1:31 AM, Samantha Atkins wrote:

Shoot.  Looked more closely and I see that the .so file is PPC.  I
am on an Intel mac.  Likely the problem?  What fixes it?

[samantha:samantha]$ file /Users/samantha/.sbcl/site/
linedit_0.15.12/terminal_glue.so
/Users/samantha/.sbcl/site/linedit_0.15.12/terminal_glue.so: Mach-O
bundle ppc

- s

On Mar 25, 2007, at 1:24 AM, Samantha Atkins wrote:

I seem to be getting a dlopen error as in the following backtrace:

0] backtrace

0: (SB-SYS:DLOPEN-OR-LOSE
     #S(SB-ALIEN::SHARED-OBJECT
        :FILE "/Users/samantha/.sbcl/site/linedit_0.15.12/
terminal_glue.so"
        :SAP NIL))
1: (LOAD-SHARED-OBJECT
     "/Users/samantha/.sbcl/site/linedit_0.15.12/terminal_glue.so")
2: (NIL #P"/Users/samantha/.sbcl/site/linedit_0.15.12/
terminal_glue.so")
3: ((SB-PCL::FAST-METHOD ASDF:PERFORM
      (ASDF:LOAD-OP LINEDIT-SYSTEM::UFFI-C-SOURCE-FILE))
     #<unused argument>
     #<unused argument>
     #<ASDF:LOAD-OP NIL {11702EC1}>
     #<LINEDIT-SYSTEM::UFFI-C-SOURCE-FILE
"terminal_glue" {11CC2601}>)
4: ((LAMBDA
         (SB-PCL::.PV-CELL. SB-PCL::.NEXT-METHOD-CALL. SB-
PCL::.ARG0.
          SB-PCL::.ARG1.))
     #<unavailable argument>
     #<unavailable argument>
     #<ASDF:LOAD-OP NIL {11702EC1}>
     #<LINEDIT-SYSTEM::UFFI-C-SOURCE-FILE
"terminal_glue" {11CC2601}>)
5: ((LAMBDA ()))
6: (SB-C::%WITH-COMPILATION-UNIT #<CLOSURE (LAMBDA #) {11771B8D}>)
7: (NIL ASDF:LOAD-OP "linedit")
8: ((LABELS ASDF-INSTALL::ONE-ITER) (:LINEDIT))
9: (NIL)
10: (SB-INT:SIMPLE-EVAL-IN-LEXENV
      (ASDF-INSTALL:INSTALL :LINEDIT)
      #<NULL-LEXENV>)
11: (INTERACTIVE-EVAL (ASDF-INSTALL:INSTALL :LINEDIT))
12: (SB-IMPL::REPL-FUN NIL)
13: (SB-IMPL::REPL-FUN NIL)
14: ((LAMBDA ()))
15: ((LAMBDA ()))
16: (SB-IMPL::%WITH-REBOUND-IO-SYNTAX #<CLOSURE (LAMBDA #)
{1169410D}>)
17: (SB-IMPL::TOPLEVEL-REPL NIL)
18: (SB-IMPL::TOPLEVEL-INIT)
19: ((LABELS SB-IMPL::RESTART-LISP))

The file definitely exists and looks OK as far as I know how to
tell.  This install is happy in Linux but breaks on OS X.  Anyone
know what is likely to be going on and how to get past it?

thanks.

- samantha


-------------------------------------------------------------------
--
----
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
share your
opinions on IT & business topics through brief surveys-and earn
cash
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sbcl-help mailing list



---------------------------------------------------------------------
----
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
share your
opinions on IT & business topics through brief surveys-and earn cash
page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sbcl-help mailing list



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sbcl-help mailing list
Sbcl-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-help

-- 
Brian Mastenbrook
brian@mastenbrook.net
http://brian.mastenbrook.net/