WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Seamonkey 2.53.17.1.tcz corrupted  (Read 11262 times)

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #45 on: November 24, 2023, 11:29:06 AM »
Hi cute curtis. Please post the output of:
Code: [Select]
$ cat ~/lab/seamonkey-2.53.17.1/mozconfig
« Last Edit: November 24, 2023, 11:42:51 AM by GNUser »

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11703
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #46 on: November 24, 2023, 01:56:58 PM »
Hi GNUser
In reply #31 he got:
Code: [Select]
/home/tc/lab/seamonkey-2.53.17.1/python/mozbuild/mozbuild/mozconfig_loader: /home/tc/lab/seamonkey-2.53.17.1/mozconfig: line 2:
: not found
Line 2 should be blank and I think the error message confirms that.
Typically the second line of that error message reads:
Code: [Select]
SomeCommandName: not foundSo for some reason it's looking for a command called "" (empty string).
mozconfig  contains build options, not commands.

Then in reply #33, it suddenly accepts mozconfig and proceeds to read
it starting at timestamp 0:09.95:
Yes, I put mozconfig inside the seamonkey folder as instructed. BTW here is the error of the default mozconfig from Seamonkey website

Code: [Select]
tc@box:~/lab/seamonkey-2.53.17.1$ CC=clang CXX=clang++ ./mach configure
 0:01.58 Clobber not needed.
 0:01.58 Adding make options from /home/tc/lab/seamonkey-2.53.17.1/mozconfig
    MOZ_OBJDIR=/home/tc/lab/seamonkey-2.53.17.1/obj-i686-pc-linux-gnu
    OBJDIR=/home/tc/lab/seamonkey-2.53.17.1/obj-i686-pc-linux-gnu
    FOUND_MOZCONFIG=/home/tc/lab/seamonkey-2.53.17.1/mozconfig
    export FOUND_MOZCONFIG
 0:01.58 /usr/local/bin/make -f client.mk -s configure
 0:01.59 cd /home/tc/lab/seamonkey-2.53.17.1/obj-i686-pc-linux-gnu
 0:01.59 /home/tc/lab/seamonkey-2.53.17.1/configure
 0:02.31 Creating Python 3 environment
 0:04.02 Using base prefix '/usr/local'
 0:04.02 New python executable in /home/tc/lab/seamonkey-2.53.17.1/obj-i686-pc-linux-gnu/_virtualenvs/init_py3/bin/python3
 0:04.02 Also creating executable in /home/tc/lab/seamonkey-2.53.17.1/obj-i686-pc-linux-gnu/_virtualenvs/init_py3/bin/python
 0:04.02 Installing setuptools, pip, wheel...
 0:07.57 done.
 0:08.73 Error processing command. Ignoring because optional. (optional:setup.py:third_party/python/psutil:build_ext:--inplace)
 0:08.74 Re-executing in the virtualenv
 0:09.95 Adding configure options from /home/tc/lab/seamonkey-2.53.17.1/mozconfig
 0:09.95   --disable-dbus
 0:09.95   --disable-necko-wifi
 0:09.95   --disable-gconf
 0:09.95   --with-system-icu
 0:09.95   --with-system-libevent
 0:09.95   --with-system-nspr
 0:09.95   --with-system-nss
 0:09.95   --with-system-webp

 ----- Snip -----

So I guess the question is, what changed?

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #47 on: November 24, 2023, 02:18:14 PM »
That's a good point, Rich. In some instances, mozconfig is being interpreted as a list of commands on cute curtis's machine. In other instances it is being interpreted as configuration options (as expected). The variable behavior is a bit mysterious.

I tried building seamonkey myself, following Juanito's steps exactly, just to see if I could reproduce cute curtis's problem. I couldn't reproduce it. I copied and pasted the file from BLFS (minus the first and last lines containing EOF) and I did not get the : not found error.

Nevertheless, I cannot get past the
Code: [Select]
CC=clang CXX=clang++ ./mach configure
step. I get an error about gconf-2 missing. I should have copied the exact error message, but I'm at work and was doing this piecemeal with distractions/interruptions. No need to look into this for my sake, though. If cute curtis can get farther along and encounters the same error, then we can look into it.

P.S. I can understand his desire to be able to compile this himself. I, too, like knowing how to compile my favorite applications.
« Last Edit: November 24, 2023, 02:20:03 PM by GNUser »

Offline CardealRusso

  • Full Member
  • ***
  • Posts: 181
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #48 on: November 24, 2023, 02:23:07 PM »
...I get an error about gconf-2 missing...
Também tive este problema com o Palemoon, precisa do --disable-gconf

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #49 on: November 24, 2023, 02:57:26 PM »
Hi CardealRusso. Thanks for the tip. It made me realize that Juanito posted his mozconfig (available here) and that it has some options (e.g., --disable-gconf) not included in the BLFS version of mozconfig.

If I use Juanito's build notes, his mozconfig, and follow the steps exactly, everything works:
Code: [Select]
$ CC=clang CXX=clang++ ./mach configure
---snip---
 0:30.00 FasterMake backend executed in 0.61s
 0:30.00   9 total backend files; 9 created; 0 updated; 0 unchanged; 0 deleted
 0:30.00 Total wall time: 10.67s; CPU time: 10.66s; Efficiency: 100%; Untracked: 0.36s
Configure complete!
Be sure to run |mach build| to pick up any changes


Hi cute curtis, I bet if you use Juanito's mozconfig and follow the steps carefully, you will succeed. Also, note this starred comment at the top of Juanito's build notes:
Code: [Select]
*** needs utf-8 locale ***
If you are not using a utf-8 locale, please try using one. Run locale in a terminal to see your current locale. If yours is not a utf-8 locale, use the  getlocale.tcz  extension to create an extension (e.g., mylocale.tcz) for your desired locale. Then put mylocale.tcz  in tce/optional/, add mylocale.tcz to your tce/onboot.lst file and reboot. When rebooting, include a boot code that specifies your desired locale (e.g., lang=en_US.UTF-8).
« Last Edit: November 24, 2023, 03:22:23 PM by GNUser »

Offline CardealRusso

  • Full Member
  • ***
  • Posts: 181
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #50 on: November 24, 2023, 04:34:36 PM »
A propósito, eu nem consegui rodar o Seamonkey do repositório.

Code: [Select]
XPCOMGlueLoad error for file /tmp/tcloop/seamonkey/usr/local/lib/seamonkey/libxul.so:
/usr/local/lib/libnss3.so: version `NSS_3.79' not found (required by /tmp/tcloop/seamonkey/usr/local/lib/seamonkey/libxul.so)
Couldn't load XPCOM.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11703
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #51 on: November 24, 2023, 05:34:59 PM »
Hi GNUser
... If I use Juanito's build notes, his mozconfig, and follow the steps exactly, everything works: ...
Same here with minor tweaks.

This failed because the coreutils.tcz cp will not overwrite
the symlink because it considers it to be the same file:
Code: [Select]
sudo cp /tmp/tcloop/llvm15-dev/usr/local/bin/llvm-config /usr/local/binbusybox cp will overwrite the symlink:
Code: [Select]
sudo busybox cp /tmp/tcloop/llvm15-dev/usr/local/bin/llvm-config /usr/local/bin
Then:
Code: [Select]
sudo ln -s /lib /lib64
wget http://repo.tinycorelinux.net/14.x/x86_64/tcz/src/seamonkey/mozconfig
tar -xf seamonkey-2.53.17.1.source.tar.xz
cd seamonkey-2.53.17.1
cp ../mozconfig ./
 ...

Quote
Code: [Select]
*** needs utf-8 locale ***
I don't have a UTF-8 locale set:
Code: [Select]
tc@E310:~$ locale
LANG=C
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #52 on: November 24, 2023, 06:24:16 PM »
Hi Rich. You are so refreshingly thorough.
This failed because the coreutils.tcz cp will not overwrite
the symlink because it considers it to be the same file:
Code: [Select]
sudo cp /tmp/tcloop/llvm15-dev/usr/local/bin/llvm-config /usr/local/bin
I did not bump into this because I use busybox and not coreutils.

I don't have a UTF-8 locale set:
Code: [Select]
tc@E310:~$ locale
LANG=C
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=
Good to know. I always use en_US.UTF-8 and didn't try to disable it--I took Juanito's word that it was required because he is correct 99.999999% of the time ;D

Hopefully cute curtis has all the information he needs at this point.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11703
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #53 on: November 24, 2023, 07:43:58 PM »
Hi GNUser
Hi Rich. You are so refreshingly thorough. ...
Annoying, isn't it.  ;D

Quote
... I took Juanito's word that it was required because he is correct 99.999999% of the time ;D ...
Maybe it's required for running seamonkey? Also, I only ran the
configure command. Maybe it's required to run the build command.

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #54 on: November 24, 2023, 08:20:52 PM »
Also, I only ran the configure command. Maybe it's required to run the build command.
Hi Rich. Good point. Same here. Juanito's build notes say it took 1h 43m to build seamonkey on his machine. On my old clunker it would take at least twice as long and I didn't see the need since cute curtis's problem is at the configure step.


Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #55 on: November 24, 2023, 08:23:38 PM »
A propósito, eu nem consegui rodar o Seamonkey do repositório.
Oi CardealRusso. Vou responder em inglês para que todos possam entender bem.

Which version did you try running? When I load seamonkey (version 2.53.17.1)  from the TC14 x86_64 repository, it runs without any errors.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11703
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #56 on: November 24, 2023, 10:34:14 PM »
Hi GNUser
Out of curiosity, I decided to continue where I left off and run:
Code: [Select]
./mach build
8 minutes later it ended with this:
Forum error, see attachment.

Googling UnicodeDecodeError returns UTF-8 errors and python
among other things.

Offline GNUser

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 1530
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #57 on: November 25, 2023, 06:45:50 AM »
Googling UnicodeDecodeError returns UTF-8 errors
I always use en_US.UTF-8 and didn't try to disable it--I took Juanito's word that it was required because he is correct 99.999999% of the time ;D
Hi Rich. It seems my number was an underestimate.
« Last Edit: November 25, 2023, 06:48:10 AM by GNUser »

Offline CardealRusso

  • Full Member
  • ***
  • Posts: 181
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #58 on: November 25, 2023, 08:08:12 AM »
Depois testa o librewolf que enviei, devem atualizar amanhã.

Foi um trabalho retado para compilar, mas consegui. Utilizei -Os -g0 que reduz brutalmente o tamanho dos binários (e também reduz o desempenho) mas também utilizei --enable-lto. Esse enable lto supostamente melhora notavelmente, como melhorou notavelmente, o desempenho geral do navegador. Se eu não tivesse usado -Os, o resultado provavelmente seria melhor
Eis o benchmark da versão 120 disponível no site:
https://i.imgur.com/CslvoRF.png
E a que eu compilei hoje:
https://i.imgur.com/lc5GOfk.png

@edit
este teste sintetico deve dar resultados mais comparaveis
palemoon https://i.imgur.com/77O5u17.png
librewolf https://i.imgur.com/Rk6sHQI.png
ungoogled https://i.imgur.com/7aB9UAg.png
brave https://i.imgur.com/BTgDHUI.png
firefox https://i.imgur.com/fPdLbyC.png

realmente em questão de desempenho o brave é inbativel


Por curiosidade testei o brave-browser no mesmo site e deu 60k de pontos, embora isso não necessariamente queira dizer uma melhora bruta no desempenho, uma vez que o librewolf desativa várias opções por questões de privacidade, e essas opções não testadas são reduzidas do resultado.
« Last Edit: November 25, 2023, 08:28:14 AM by CardealRusso »

Offline CardealRusso

  • Full Member
  • ***
  • Posts: 181
Re: Seamonkey 2.53.17.1.tcz corrupted
« Reply #59 on: November 25, 2023, 08:42:44 AM »
Eu estava utilizando o Palemoon mas por causa do DBUS, acho muito desnecessário forçar o uso do dbus.
O problema é que, como pode ver, o Palemoon é realmente muito lento. Decidi então me esforçar para compilar um navegador mais moderno e o mais fácil foi o librewolf.

Porém, o --disable-dbus é totalmente desrespeitado no mozconfig. Eu reportei isso em https://codeberg.org/librewolf/issues/issues/1682 e estou aguardando uma resposta.