[SOLVED] Rebuilding Firefox SlackBuild, problem with -rpath
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.
This works for me with several SlackBuild scripts.
Just add the line with the LDFLAGS, (notice the syntax for rpath).
You really want also to use the "-enable-new-dtags" option!
Yes, that's right. If you do it this way, you can put a script into /etc/profile.d that sets LD_LIBRARY_PATH (some SlackBuilds add that to the package), or you can add /opt/gstreamer1-banshee/usr/lib64 to /etc/ld.so.conf (but it is often considered impolite for packages to do that), or you can create your own wrapper script for Firefox to set LD_LIBRARY_PATH (most packages that expect to live in /opt provide such a script to put into /usr/bin).
*Or*
You can set an rpath, like you already tried. Your build options are almost right, but, let's be honest, these gcc and ld control arguments (and environment variables) are *weird*, and there are several ways to do the same thing. If I've got it right, here are three possibilities:
To explain a bit more: (1) You need to set it as *both* a link path *and* a run path. (Probably). (2) This will work in a simple case, but Firefox is not a simple case, and if plugins etc. etc. don't work properly, it will need something more clever.
ml4711 is right, in general --enable-new-dtags is a good thing. It gets round lots of problems that you haven't had yet
LD_RUN_PATH=xxxx is just a different/easier way of saying -Wl,-rpath,xxxx
What would be the line to use in the SlackBuild if I were to use the GStreamer package which comes with Slackware?
The whole fiddling with -rpath and LD_LIBRARY_PATH is only needed when you have gstreamer installed in a non-standard prefix like I did.
Building Firefox against Slackwares gstreamer 0.10.x is much easier, but Slackware only comes with gst-plugins-good.
You need to build gst-plugins-ugly from slackbuilds.org for MP3 support and gst-ffmpeg + ffmpeg for HTML5 video support.
After that, you can add "--enable-gstreamer" to the options in the firefox Slackbuild to build it with gstreamer-0.10 support.
Considering that gstreamer 0.10.x is end-of-life, I would strongly advise building Firefox against the newest branch. You can find SlackBuilds and packages for Slackware64 -current in my signature.
The whole fiddling with -rpath and LD_LIBRARY_PATH is only needed when you have gstreamer installed in a non-standard prefix like I did.
Building Firefox against Slackwares gstreamer 0.10.x is much easier, but Slackware only comes with gst-plugins-good.
You need to build gst-plugins-ugly from slackbuilds.org for MP3 support and gst-ffmpeg + ffmpeg for HTML5 video support.
After that, you can add "--enable-gstreamer" to the options in the firefox Slackbuild to build it with gstreamer-0.10 support.
Considering that gstreamer 0.10.x is end-of-life, I would strongly advise building Firefox against the newest branch. You can find SlackBuilds and packages for Slackware64 -current in my signature.
Thanks much for the help. It is greatly appreciated.
I wonder why Pat hasn't upgraded gstreamer from the 0.x.x branch, given that it is end-of-life.
Just curious.
Does the newest branch of gstreamer offer any compelling features to warrant an upgrade? Because otherwise, I'm not inclined to modify what already works, lest I break it in the process.
Does the newest branch of gstreamer offer any compelling features to warrant an upgrade? Because otherwise, I'm not inclined to modify what already works, lest I break it in the process.
That's exactly why I installed gstreamer 1.x into /opt, so I can keep all official packages without breaking anything.
I don't know of any big changes. I think they made a lot of improvements using hardware decoding with libvdpau, but Firefox doesn't use these features yet. On Banshee I made a backport of GST1 because it is much more stable. Didn't experience any crashes anymore, seeking in files works every time etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.