http://bugzilla.rpmfusion.org/show_bug.cgi?id=527
--- Comment #34 from Orcan Ogetbil <oget.fedora(a)gmail.com> 2009-04-17 17:09:30 ---
(In reply to comment #31)
>
> and what will set the LADSPA_PATH during runtime? No, just patch (or sed) it
> up, and there won't be no worries.
My mistake...
but if I put in spec some like this:
%post
/sbin/ldconfig
export LADSPA_PATH=%{_libdir}/ladspa
Then, will yum after installing package execute this export line and setup
LADSPA_PATH to correct value?
But if you want patch, I'll make a patch, but before them I must know how to
solve this multilib path (Currently I do not have enough knowledge about
multilibs :( ) (Nobody is perfect :) )
It's okay, you learn with experience. It will be enough to change the line
ladspa_path = g_strdup ("/usr/local/lib/ladspa:/usr/lib/ladspa");
in src/modules/jackrack/plugin_mgr.c to
ladspa_path = g_strdup
("/usr/local/lib/ladspa:/usr/lib/ladspa:/usr/local/lib64/ladspa:/usr/lib64/ladspa");
You can then send this patch upstream.
>
> Please describe me the steps to get this rpmlint warning, with that line
> removed.
>
After building package with mock and checked packages under mocsk's result dirs
with rpmlint, and without execstack line, I'm getting this warning in i386
package:
mlt.i586: W: executable-stack /usr/lib/mlt/libmltgtk2.so
I confirm this to happen only in i386 package. x86_64 doesn't have the problem.
You can use the attached patch to solve the issue permanently. You can send
this upstream too.
Other then these, I found that the installed package gives the rpmlint
mlt.x86_64: W: unused-direct-shlib-dependency /usr/lib64/libmlt.so.0.3.8
/lib64/libm.so.6
which can easily be fixed too. Check the LDFLAGS.
--
Configure bugmail:
http://bugzilla.rpmfusion.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.