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.
Running Slack64-current with latest update as of 30.8.2017 (with Cargo built into Rust). Using the SlackBuild and everything from the Slackware source folder. The build dies after a while. Running AlienBob's checkpkg on the build log gives the following -
root@missi:/patches/mozilla-firefox$ ./checkpkg -l build.log
++ Checking logfile 'build.log' (no news is good news):
57258: firefox-55.0.3/dom/html/test/forms/FAIL.html
209109: Fatal server error:
209441: js/src> checking for the Android toolchain directory... not found
210127: dom_geolocation nsIDOMGeoGeolocation nsIDOMGeoPosition nsIDOMGeoPositionCallback nsIDOMGeoPositionCoords nsIDOMGeoPositionError nsIDOMGeoPositionErrorCallback
210607: storage mozIStorageAggregateFunction mozIStorageAsyncConnection mozIStorageAsyncStatement mozIStorageBaseStatement mozIStorageBindingParams mozIStorageBindingParamsArray mozIStorageCompletionCallback mozIStorageConnection mozIStorageError mozIStorageFunction mozIStoragePendingStatement mozIStorageProgressHandler mozIStorageResultSet mozIStorageRow mozIStorageService mozIStorageStatement mozIStorageStatementCallback mozIStorageStatementParams mozIStorageStatementRow mozIStorageVacuumParticipant mozIStorageValueArray
212755: if (U_FAILURE(status)) {
222083: roundingError -= 1;
226018: /tmp/firefox-55.0.3/media/webrtc/trunk/webrtc/modules/rtp_rtcp/source/h264_sps_parser.cc:17:0: warning: "RETURN_FALSE_ON_FAIL" redefined
226019: #define RETURN_FALSE_ON_FAIL(x) \
226023: #define RETURN_FALSE_ON_FAIL(x) \
232811: #define SkFAIL(message) SK_ABORT(message)
232813: /tmp/firefox-55.0.3/gfx/skia/skia/src/gpu/gl/GrGLPath.cpp:199:13: note: in expansion of macro 'SkFAIL'
232814: SkFAIL("Incomplete Switch\n");
232865: #define SkFAIL(message) SK_ABORT(message)
232867: /tmp/firefox-55.0.3/gfx/skia/skia/src/gpu/gl/GrGLPathRendering.cpp:71:13: note: in expansion of macro 'SkFAIL'
232868: SkFAIL("Unexpected path fill.");
234896: #define SkFAIL(message) SK_ABORT(message)
234898: /tmp/firefox-55.0.3/gfx/skia/skia/src/gpu/GrPathRendering.cpp:18:13: note: in expansion of macro 'SkFAIL'
234899: SkFAIL("Unexpected path fill.");
235134: #define SkFAIL(message) SK_ABORT(message)
235136: /tmp/firefox-55.0.3/gfx/skia/skia/src/gpu/instanced/InstanceProcessor.cpp:1678:13: note: in expansion of macro 'SkFAIL'
235137: SkFAIL("Unexpected antialias mode.");
241989: /tmp/firefox-55.0.3/media/webrtc/trunk/webrtc/modules/audio_device/linux/audio_device_alsa_linux.cc:2155: undefined reference to `LogLatency(AsyncLatencyLogger::LatencyLogIndex, unsigned long, long)'
241990: /tmp/firefox-55.0.3/media/webrtc/trunk/webrtc/modules/audio_device/linux/audio_device_alsa_linux.cc:2152: undefined reference to `LogTime(AsyncLatencyLogger::LatencyLogIndex, unsigned long, long)'
241993: collect2: error: ld returned 1 exit status
241994: make[6]: *** [/tmp/firefox-55.0.3/config/rules.mk:642: webrtc-gtest] Error 1
241996: make[5]: *** [/tmp/firefox-55.0.3/config/recurse.mk:73: media/webrtc/trunk/gtest/target] Error 2
242004: make[4]: *** [/tmp/firefox-55.0.3/config/recurse.mk:33: compile] Error 2
242006: make[3]: *** [/tmp/firefox-55.0.3/config/rules.mk:519: default] Error 2
242008: make[2]: *** [/tmp/firefox-55.0.3/client.mk:419: realbuild] Error 2
242010: make[1]: *** [/tmp/firefox-55.0.3/client.mk:232: profiledbuild] Error 2
242012: make: *** [client.mk:170: build] Error 2
|install mawk). For LFS: we put mktemp in /usr/bin not /bin, remove
root@missi:/patches/mozilla-firefox$
It looks like one of the major faults is -
js/src> checking for the Android toolchain directory... not found
I have no idea why it would be looking for an Android toolchain. Any thoughts?? Thanks in advance
Wonder how the Slackware folks got it built if this is a bug.
To note that I have a pair of clean and up to date installations of Slackware(64) current, installed in its own partitions.
And, on this reference installations, the Firefox 5.0.3 builds fine and the resulted packages works just like the ones shipped by the Slackware Team.
I tested/built this on both i586 and x86_64 archs.
Then, could be some of your own customization of the operating system which affects the Firefox build. Most likely, you tried a PulseAudio "free" build?
Finally, to note that, from what I read, is supposed that the new versions of Firefox does NOT use multiple audio backends for WebRTC, rather relying on the system's PulseAudio for Linux targets. You know, everyone have it now, even Slackware...
Last edited by Darth Vader; 08-30-2017 at 01:16 PM.
Well, I tried the patch and it tells me that it had already been applied (and do I want to reverse it). I have the Slackware version of Pulseaudio installed so that's not it. Will have to assume that it is something added to the system that is causing the problem. Since FF works fine I will stop my effort to build it myself. Thanks to all for your responses.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.