[Openmcl-devel] An unfortunate interaction between CFFI and open-shared-library

[Ron Garret]

On Sep 19, 2010, at 1:36 PM, Raffael Cavallaro wrote:

> 
> On Sep 19, 2010, at 4:31 PM, Ron Garret wrote:
> 
>> So... is there a reason that open-shared-library is dispatching to the initial thread?  If there isn't, it really shouldn't.  And if there is, well, then Houston, we have a problem.
> 
> On Sep 10, 2010, at 11:41 PM, Gary Byers wrote:
> 
>> some OSX shared libraries can only be opened on the
>> initial thread, some lisp libraries seem to be unaware of this, and that
>> change was supposed to at least allow users of those lisp libraries to get
>> to the point where they realized that lots of other things would need to
>> change.
> 

Ah.  Hm.

A little more context:

> I don't know of any recent change in CCL that'd affect this.  The thing
> that comes closest is a change to force OPEN-SHARED-LIBRARY to call dlopen()
> on the initial thread; some OSX shared libraries can only be opened on the
> initial thread, some lisp libraries seem to be unaware of this, and that
> change was supposed to at least allow users of those lisp libraries to get
> to the point where they realized that lots of other things would need to
> change.  Whether that workaround's a good idea or not, it's not clear to
> me that it could affect whether or not a library's found or loaded correctly.

I guess it's clearer now.  :-)

I opened a ticket.  #742.

rg