So they keep including USELESSLY more and more HACK LANGUAGES required to build it. IE: python. This also requires (i can prove) that the system admin "either copy the system python" or have the system python become completely damaged
PYTHON 2.5, 2.7, 3.4, ... they all damage each other so you must have MULTIPLE INSTALLED 'languages'
KNOWNING THIS - FIREFOX MOZILLA CALIFORNIA HAS NOT STEPPED BACK BUT UPPED THE PROBLEM BY ADDING 'rust' language.
SO - you download "source" but you can't build it becuase YOU DIDN'T GET ALL THE SOURCE (it wants to "download" "Cargo.list" rust crates) - right there - that's a breach of public trust.
but the "download" IS HIGHLY BROKEN - reported by BLFS (beyond linux from scratch): ONE A GIVEN RUST VERSION works only with one firefox version - have the wrong version they both break each other (german design - they always attack others while HOARDING AND IMPROVING SUSE LINUX AND NOVELL/ANTHEM GERMAN SS, ru still mad about IPX).
SO THEY SAY THIS DOWNLOADED MYSTERY RUSTC OPERATING SYTEM FROM CHINA GERMAN IS HARMLESS - BUT THAT IS A LIE. (you'd have to be running it in a virtual simulator and or buy another PC: and that costs TIME AND MONEY - ALLOT OF BOTH)
========================
WHAT DOES ALL THAT DO? make broken makefiles which need to be REPAIRED in order for firefox to finally be compiles. JUST MORE china german OBSTRUCTIONS.
(python and rust hook themselves so terrorists can penetrate your web browser but they are not used for anythign while you read the news or do multimedia: their only function is penetration and hacking. their only purpose domination matrix, terror, AND THEY GET PAID $$$ PUBLIC USA FUNDS WHILE YOU HAVE NO TIME TO DATE TO FIND A WOMAN AND HAVE CHILDREN while they cuck with the money)
has python ever been described by some as "slowly strangling free software like a snake of the same name". YES IT HAS. and chinese germans do their best to IP ban and delete all evidence.
========================
this has been "going on" since they let one GERMAN suse working in Mozilla.org "help them make Makefiles more efficient". he immediately began writing malware "german mach go" which caused worldwide problems and made them worse until firefox-50, then also required RUSTC - all very smugly with german jizz names on what he was doing. farfegnugen yea. always hated it. a german national poisoned me i nearly died spent 5 years in recovery. ask me if "i like german farfegnugen". i do not.
=========================
https://www.linuxfromscratch.org/blfs/view/svn/general/rust.html
Currently Rust compiler produces SSE2 instructions for 32-bit x86, causing the generated code broken on 32-bit systems without a SSE2-capable processor. OBSTRUCTION
This package is updated on a six-weekly release cycle. Because it is such a large and slow package to build, is at the moment only required by a few packages in this book, and particularly because newer versions tend to break older mozilla packages, the BLFS editors take the view that it should only be updated when that is necessary
Although BLFS usually installs in /usr, when you later upgrade to a newer version of rust the old libraries in /usr/lib/rustlib will remain, with various hashes in their names, but will not be usable and will waste space. The editors recommend placing the files in the /opt directory. In particular, if you have reason to rebuild with a modified configuration (e.g. using the shipped LLVM after building with shared LLVM, perhaps to compile crates for architectures which the BLFS LLVM build does not support) it is possible for the install to leave a broken cargo program. In such a situation, either remove the existing installation first, or use a different prefix such as /opt/rustc-1.60.0-build2.
WHICH IS IMPOSSIBLE. RUSTC doesn't have a site for source code of past versions. And when firefox fires up it downloads the latest rust which means:
Development versions of BLFS may not build or run some packages properly if dependencies have been updated since the most recent stable versions of the book.
The testsuite will generate some messages in the system log for traps on invalid opcodes, and for segmentation faults. In themselves these are nothing to worry about, just a way for the test to be terminated. (THEY ARE NOT OK TO IGNORE - EACH ONE INICATES FUTURE PROBLEMS)
other tests might fail on some machines - if the number of additional failures is in the single digits, check the log for 'failures:' and review lines above that, particularly the 'stderr:' lines. Any mention of SIGSEGV or signal 11 in a failing test is a cause for concern.
if you aren't building ff-VER at the same time day and temperature they build it in california - your fucked. because the older newer RUSTC isn't compatible and ALSO NOT AVAILABLE
that's what they call german clock werk
https://www.linuxfromscratch.org/blfs/view/svn/general/rust.html
MORE AND MORE HORRIFIC DETAILS AT THE ABOVE URL
THIS IS JUST ONE HACK LANGUAGE FIREFOX HAS DEEMED "REQUIRED". IT IS NOW LIKE THE 10TH HACK LANGUAGE THOSE BASTARDS HAVE REQUIRED.
AND BTW - firefox is android ARM friendly so don't believe it. they are using "secret keys" to skip whole parts of the python rust C++ build for android. 'idea'
@fuck@
BLFS has a hwole team of people #funded by BIG TECH and always take a knee to big tech. i have: nothing.
if BLFS has dire warnings all over the place i have: A GIGANTIC MESS ON MY HAND AND AM IN PERIL OF FOREIGN ATTACK. my situation 100x worse than theirs.