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.
If not told otherwise, in this case the linker looks for libraries first in /usr/lib (standard location). But those you wanted it to link to are in /usr/lib64, so you need to told that setting LDFLAGS to -L/usr/lib64 (as you run a 64-bit kernel LIBDIRSUFFIX is set to 64 by the SlackBuild) otherwise it picks the "bad" (32-bit) libraries.
Last edited by Didier Spaier; 07-15-2015 at 05:23 PM.
Phew man, that was a tough one.
I successfully managed to compile webkitgtk and Midori browser afterwards.
It took 2 days for me to figure out and compile (there were additional problems with pkgconfig).
Thanks everyone for your answers!
-Youmu
i'm unsure why your concerned where gcc finds what it will use - that's automatic - your talking about whether gcc cannot compile a _64 binary correctly (if gcc is intermittently using wrong libexec though you gave _64 as target)
perhaps waf, the python "build tool" that midori (which claims multi plat compat and such) is using a hardcoded path and telling which libexec to use. some Makefiles try to specify things they should leave gcc to decide, like "where is crtbegin" and when to use "collect2".
i'm looking into waf today wondering if the following in the waf python script is a trojan horse - to ask anyone if they can figure out what the blob is...
#==>
#BZh91AY&SY+Þ$^\^BÚ^P^?ÿÿ±^@Ø^?ÿÿÿÿÿÿÿÿÿÿÿ.@^B!^F^A$0Â.½^@..^L^HaØ<û×¾÷^P^@^@^@^
(continues for some time - is obviously an obscured ?binary?)
#<==
i'm looking at LFS seeing libsoup is a gnome depends and midori requires a huge number of other gnome depends - the whole gnome networking stack and also all gnome HTML support libs
(in other words - it requires epiphany to run, and has same depends. i can only assume then it is a different "main frame window" is all ?)
i'm also prodding at qupzilla wondering if Qt qt-everywhere-opensource-src-4.7.4.tar.gz (220 MB source - could mean problems) would be a safer bet
i have firefox 2.0, other than "you must upgrade" it rocks. firefox 5.0 slower but scrolls fast, but still doesn't do some important web sites.
i tried firefox 20.0 TWENTY and i still get "your old upgrade", and while google maps works: i found a few sites now broken.
i don't even like the idea of web browsers turn into a desktop within an app (and noting each browser emulates things in own code: it's a desktop within a desktop within a desktop)
i'll tell you what: running apps remote using X11 is a hell of allot faster, prettier, and easier !!
Qupzilla is an interesting QT-Webkit project. Installing from SBO is simple and easy on Slackware64 14.1/Multilib. It uses the same amount of memory as SeaMonkey (even more when you get beyond 6 tabs), which is a Gecko based browser. SeaMmonkey comes with Slackware base install, like Firefox. SeaMonkey is built off the stable versions of Firefox and uses many Firefox plugins, which gives broadest compatibility to all sites. SeaMonkey also has a USER AGENT extension that allows use with wine-pipelight for SilverLight apps on sites. If you must have a QT based browser then Konqueror, which is QT-KHTML or QT-WebKit, has a much smaller footprint and takes advantage of the QT and KDE pieces already loaded when running KDE as your DE. The only problem encountered with Konqueror is that you may have to edit the ~/.kde/share/config/kio-httprc to setup the latest user-agent strings for sites, like eBay and PayPal, or to use with wine pipelight (which it does load when needed).
If you are running a GTK only environment (for example when you installed Slackware you didn't' select KDE packages) with a WM or DE like LXQT or XFCE, then Midori would be a clear pick over the QT based browsers. Installing Midori 05.10 from SBO or using sbopkg is the simplest and easiest way. Midori struggles to print eBay postage labels correctly, possibly a javascript or EasyList blocking issue. It can be used with wine-pipelight, although it isn't easy to configure for up-to-date USER AGENT strings. Otherwise Midori is light on CPU usage and memory requirements, which makes it seem "fast". YMWV
Another light memory browser in SBO is NetSurf, although it uses it's own engine. I've not been able to get it to use wine-pipelight, and don't expect it will. It also says it supports javascript, but I've had numerous issues with javascript working correctly on sites.
I note that this was posted after the OP marked the thread as solved... but felt this additional information would be helpful to others looking for help with selecting browsers and installing Midori.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.