http://bugzilla.rpmfusion.org/show_bug.cgi?id=527
--- Comment #58 from Zarko Pintar <zarko.pintar(a)gmail.com> 2009-05-07 22:20:06 ---
> NO MORE Seg. faults on F10 branch with my machine! (I do not
know why) So,
> please can you check this, too?
>
I still get the segfaults on F-10.
Yes, at home I get segfaults too, but on VBox machine at work do not.
I'll check again tomorrow.
I have answers from upstream too, but author of MLT do not like Fedora to much
:(
Citations:
On Wed, May 6, 2009 at 11:17 PM, Zarko Pintar <zarko.pintar(a)gmail.com> wrote:
1st) You suggested to me to try disable SELinux, but my SELinux is
disabled!
2nd) If I use ffmpeg drom SVN (not from RPM FUsion repo), than I'm getting
Segmentation Faults from that ffmpeg!
Oh well, I do not use Fedora 10 or 11. I have enough to do already.
Are you telling me that you can't find one Fedora user to figure this
out and send a patch to the relevant project? If you can't then that
is an indicator of just how unpopular Fedora is as a distro for MLT
users, which means it really isn't worth my time right now. I have
better things to do, such as...
For this reason I ask you again, can you make some patch for MLT 0.38
for
resolving this build warning:
mlt.i386: W: shared-lib-calls-exit /usr/lib/libmiracle.so.0.3.7
exit(a)GLIBC_2.0
I already repeatedly gave the answer to this. I am not willing to
apply a patch that removes these calls because it will break the
functionality. I have clients that have paid me money that uses this
code, and I am not going to fuck it up for them. However, Fedora is
free to apply their own patch since miracle is not interesting to most
of its users. There is no simple patch to reorganize the repo and
remove miracle from the mlt project. I am already in the process of
reorganizing, but it is far from trivial. I might be able to get this
done this weekend.
So, what are you guys suggest to do now??
--
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.