Mailing-List: contact dev-help@lucy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucy.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <4F9A92D9.8040609@aevum.de>
Date: Fri, 27 Apr 2012 14:36:41 +0200
From: Nick Wellnhofer <wellnhofer@aevum.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: dev@lucy.apache.org
References: <4F996DAD.2060501@aevum.de>
 <CAAS6=7g6GHy-mZ2ouqE0m2FU9ZQm=-3Eei6V-kO-879jfbf7eA@mail.gmail.com>
 <4F9A8F6B.1050508@aevum.de>
In-Reply-To: <4F9A8F6B.1050508@aevum.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [lucy-dev] Sample extension for Lucy

On 27/04/2012 14:22, Nick Wellnhofer wrote:
>> This leads me to question whether extensions should be linking against
>> the
>> shared objects of their dependencies on *any* platform. Does that
>> create a
>> tight binding that will e.g. break WhitespaceTokenizer when Lucy gets
>> updated?
>> I'm pretty sure we want runtime relocation of upstream symbols.
>
> On Linux I had to link against Lucy.so. Otherwise I get "undefined
> symbol" errors when running the tests.

There seem to be two workarounds on Linux: Link the main executable with 
-rdynamic or pass the RTLD_GLOBAL flag to dl_open. Since our main 
executable is perl, the former won't work. But the latter can be 
achieved by using DynaLoader with dl_load_flags set to 1.

Nick