Hi,
Has anyone tried to install Firefox-101 on LFS 11.1 yet? I run in the following error:
0:08.44 File "/sources/firefox-101.0.1/third_party/python/PyYAML/lib3/yaml/reader.py", line 101, in forward
0:08.44 self.update(length+1)
0:08.44 File "/sources/firefox-101.0.1/third_party/python/PyYAML/lib3/yaml/reader.py", line 169, in update
0:08.44 self.check_printable(data)
0:08.44 File "/sources/firefox-101.0.1/third_party/python/PyYAML/lib3/yaml/reader.py", line 143, in check_printable
0:08.44 raise ReaderError(self.name, position, ord(character),
0:08.44 yaml.reader.ReaderError: unacceptable character #x0080: special characters are not allowed
0:08.44 in "/sources/firefox-101.0.1/toolkit/components/nimbus/FeatureManifest.yaml", position 14415
0:08.44 ./TelemetryScalarData.h.stub
0:08.44 make[3]: *** [backend.mk:804: toolkit/components/nimbus/lib/.deps/NimbusFeatureManifest.h.stub] Error 1

Has anybody an idea, what goes wrong here?
Luc

Error 1 is 'Operation not permitted' usually but not always a permissions error. You have a python tailspin, followed by the crash It looks like something in the source. But it could be version numbers. It's possible LFS aren't on the latest versions, or a lack of up to date python modules. Websearch for it, and file a bug if needed.

i've not tried FF on LFS/BLFS but here's some advice

the last FF that published open source was 44.0 (and it's an ugly build - 42.0 was easier)

FF requires rustc python cargo all kinds of junk that phones home to california uploads you don't know what and likely will fail so they keep their jobs safe providing you the binaries! (that's just a guess - shhhh)

If I were you I'd provide all the requirements for FF (make your libs), run FF binary. Then compile FF using CARGO if you have time.

> what goes wrong here?

I would guess allot more than LQ would allow in a single thread, I might be wrong.

FF's dependencies are extreme. OTOH, there are clones like Palemoon, Waterfox, Basilisk & possibly others that didn't like the Google ownership or the many strange decions that were made and have forked themselves off as separate projects. Palemoon for sure distributes source, and the other two probably also do. FF is reliant on google now, and it's policies & tracking reflect that.

Falkon builds and runs well on LFS it's qt 5 based, been running it for years now had no great problems.

Even BLFS dev. book sticks to firefox ESR versions. You're on your own. I suggest seeing how Arch linux builds it (especially what up to date deps it requires) or some other distro.

I've now replaced Firefox with Falkon. I'm going to miss some FF extensions Falkon doesn't have but it (Falkon) is a better browser. Good thing it exists - otherwise, i would be driven to try and build Chromium - doesn't look like much fun..

Just thought of something. To the OP - Do you have cython installed?

If not, install it (it's in the development blfs book under python modules). Then, rebuild py-yaml, then try building firefox again. IIRC, the only reason cython was added to the book is because py-yaml was not being built correctly.