Re: [Jamin] another 64-bit issue?

[Steve H. <S.W...@ec...>]

On 7 Feb 2008, at 11:37, Emmanuel Saracco wrote:

> Steve Harris a écrit :
>
> Hi Steve,
>
>> On 6 Feb 2008, at 18:23, Udo van den Heuvel wrote:
>>
>>> Emmanuel Saracco wrote:
>>>>> Cannot find plugin 'sc4_1882.so'
>>>>> Required plugin sc4_1882.so missing.
>>>>> Please load the SWH plugins.
>>>>>
>>>>> Yet they are there:
>>>>>
>>>>> [root@newdaw ~]# locate sc4_1882.so
>>>>> /usr/lib64/ladspa/sc4_1882.so
>>>>>
>>>>> Does Jamin look in lib64?
>>>> By default, JAMin look for the LADSPA_PATH env variable. If not
>>>> found it
>>>> default to "/usr/local/lib/ladspa:/usr/lib/ladspa".
>>>>
>>>> So, a "export LADSPA_PATH=/usr/lib64/ladspa" should do the trick.
>>> Thanks for the info.
>>> Would a patch to add the /usr/lib64/ladspa path to the default  
>>> search
>>> path be acceptable?
>>
>> [sorry, I sent this from the wrong address initially]
>>
>> No, they should go in /usr/lib64/ladspa, but it shouldn't be added to
>> the default path.
>>
>> The app needs to know whether it's been compiled with 64bit or 32bit
>> code, because if it tries to load the wrong format it will  
>> segfault, I
>> think.
>>
>> So, probably the default LADSPA_PATH should probably be picked at
>> compile time, between the 64 and 32 paths.
>
> In fact, since my first 64-bit patch, the libdir is set to "/lib" or
> "/lib64", depending on the the system:
>
> http://jamin.cvs.sourceforge.net/jamin/jamin/configure.in?r1=1.232&r2=1.233
> http://jamin.cvs.sourceforge.net/jamin/jamin/controller/Makefile.am?r1=1.5&r2=1.6
>
> Now the second 64-bit patch (not yet commited, but posted on this list
> yesterday) just use the libdir defined at compile time and add it to  
> the
> default LADSPA_PATH.
>
> Can I commit this last one?

Yeah, seems good.

I'm still not quite sure what the right solution is though.

LV2 should do something more sensible, but doesn't yet.

- Steve