HandBrake giving segmentation faults from SBo and Alien's script
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@Alien Bob: I was wondering how your package worked and not home built ones. At first, I concidered that maybe you had some special CFLAGS in your environment, but that seemed far fetched. I read your slackbuild, and could not find a major difference that told me: "Ah, this is where he fixes the issue!" Thanks for your input and insight.
Cheers,
John
EDIT: rereading this now, it sounds like I am asking a question, but it is just me having an "aha" moment about the difference it made (re: resulting in usable binaries) that you compiled with gcc-4.7.
Last edited by j_v; 04-12-2014 at 07:54 PM.
Reason: recapitulate
Are you sure the build used that newer tarball? Handbrake downloads a very specific version of x264 which is hardcoded in the build script. All my SlackBuild script does is download it beforehand, so that you can do an offline build of the package.
Check your build log (you kept a log did you?) and find out if a x264 tarball was downloaded before the compilation started.
Eric
Yes, I am sure the newer tarball was used. I removed the old one, the new one was downloaded, extracted and then used. No, I don't have a log. I am still getting the hang of this stuff so I am kinda disorganized.
Yes, I am sure the newer tarball was used. I removed the old one, the new one was downloaded, extracted and then used. No, I don't have a log. I am still getting the hang of this stuff so I am kinda disorganized.
I applied the diff you posted earlier on (that changes the version and the download URL of the x264 source tarball) and ran a build. This is what I find in the log file:
... meaning your newer x264 source is never used, and the handbrake Makefile still downloads the version it has hardcoded.
It is always a good idea to log your compilation process, or even the output of any long-running process which fills more than one screen.
if feel like testing it, now that I know the cause (thanks Eric!) I created a patch to apply to the Slackbuild on SBo: it updates x264 to the latest snapshot tarball
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.