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.
Anyone have adjustments to slackbuild or patches to assist with this release? My most recent successful build is 84.0.2 - the last slackbuild patch at that time was:
Thanks very much @Ponce - I think I've broken something in my slackbuild so would you mind providing the full latest slackbuild you used in the 86 build?
Thanks very much @Ponce - I think I've broken something in my slackbuild so would you mind providing the full latest slackbuild you used in the 86 build?
it's the one available in the /sources/xap/mozilla-firefox/ directory of current with just the modifications above applied...
Thanks, I've started with a fresh copy of the source folder and applied the patch. Got the following:
Quote:
In file included from ../deps/v8/src/torque/ast-generator.cc:8:
In file included from ../deps/v8/src/torque/ast-generator.h:8:
In file included from ../deps/v8/src/torque/TorqueBaseVisitor.h:11:
In file included from ../deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/./antlr4-runtime.h:149:
../deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/pattern/ParseTreePattern.h:34:21: warning: explicitly defaulted copy assignment operator is implicitly deleted [-Wdefaulted-function-deleted]
ParseTreePattern& operator=(ParseTreePattern const&) = default;
^
../deps/v8/third_party/antlr4/runtime/Cpp/runtime/src/tree/pattern/ParseTreePattern.h:97:13: note: copy assignment operator of 'ParseTreePattern' is implicitly deleted because field 'patternRuleIndex' is of const-qualified type 'const int'
const int patternRuleIndex;
^
../deps/v8/src/torque/ast-generator.cc:123:32: error: type 'antlr4::tree::TerminalNode *' cannot be narrowed to 'bool' in initializer list [-Wc++11-narrowing]
ParameterList result{{}, {}, context->VARARGS(), {}};
^~~~~~~~~~~~~~~~~~
../deps/v8/src/torque/ast-generator.cc:123:32: note: insert an explicit cast to silence this issue
ParameterList result{{}, {}, context->VARARGS(), {}};
^~~~~~~~~~~~~~~~~~
static_cast<bool>()
../deps/v8/src/torque/ast-generator.cc:144:32: error: type 'antlr4::tree::TerminalNode *' cannot be narrowed to 'bool' in initializer list [-Wc++11-narrowing]
ParameterList result{{}, {}, context->VARARGS(), {}};
^~~~~~~~~~~~~~~~~~
../deps/v8/src/torque/ast-generator.cc:144:32: note: insert an explicit cast to silence this issue
ParameterList result{{}, {}, context->VARARGS(), {}};
^~~~~~~~~~~~~~~~~~
static_cast<bool>()
4 warnings and 2 errors generated.
make[1]: *** [deps/v8/gypfiles/torque.host.mk:278: /tmp/node-v10.21.0/out/Release/obj.host/torque/deps/v8/src/torque/ast-generator.o] Error 1
make: *** [Makefile:99: node] Error 2
So I've commented nodejs out in the build-deps.sh file (I have a system nodejs) and run build again. Completed this time and I have a 85.0.1 build now.
If anyone wants to try a PGO+LTO build (which won't work with gcc anymore, btw), use the lld linker. Gold is pretty borked these days (can't handle this build for me anymore... barfs with internal errors on the final linking of libxul since Firefox 84) and ld.bfd would likely OOM.
ac_add_options --enable-linker=lld
elfhack doesn't fail with lld currently, so no need to --disable-elfhack at this time (I'm saying that because it used to, at times)
Definitely want to use llvm-ar, llvm-nm, llvm-ranlib for a PGO+LTO build now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.