buc Funny bug day. Archiving newsgroup messages seem to lock the folder. Already in 2.49.5 and also in TB 78. Seems to be in shared coded and needs a restart to unblock it. Might be related if something is not coming to an end. Anyway tomorrow is another day. Nighty night.

Google thinks 2.49.5 is a bot now, too often prompting me to answer I am not a robot :(

NVM

wrong tab

Google thinks 2.49.5 is a bot now, too often prompting me to answer I am not a robot :(

I thought Google believed that Seamonkey was now a cellphone...

haven't bothered resetting my UA override for Google since I'm on a Real Computer™

gettr.com produces nothing but white in the viewport.

> SyntaxError: expected expression, got keyword 'import' 2.8d189ded.chunk.js:2:3102817

found a clue here: zadam/trilium #648

apparently there is a name collision somewhere in their sea of Javascript vomit with an actual keyword, but that's supposed to work on "modern"/Chrome browsers

something similar: forum.palemoon.org/viewtopic.php?t=24899

so yeah, it's some newfangled Javascript module thing

it's this: developer.mozilla.org/es/docs/Web/JavaScript/Guide/Modules

more precisely, dynamic module loading, aka import('more/javascript/vomit.js')

so it turns out checking for CPU_TYPE being arm in the media/webrtc/trunk/moz.build was definitely incorrect CPU_TYPE=arm implies a 32-bit arm processor and for 64 bit th3e CPU_TYPE is aarch64

\was wondering if you could test the patch at wg9s.com/comm-253-de/patches/WIP-9999999-aarch64-support.patch and see if building with that works. I would try witch both --enable-webrtc and --disable-webrtc

I am still unable to get cross-compiles to work properly so can;t do my own testing here

tomman: actually checking for a bot more often probably means you don't allow cookies for the site. I bet if you enabled cookies it would only ask this once and then next time would not ask because a cookie would say you already did this.

frg_Away: have you looked into the autoconf thing to determine how it is supposed to work? seems to me it is chicken and egg issue won;t have a builtin autoconf working untill after build step which is dependent on configure step which is dependent on a working autoconf

oops wrong channel

so perhaps for building on aarch64 still needs the scops patch

perhaps I should jusrt land all 3 changes

1 is for building under aarch64 and two for building with target of aarch64 so perhaps split into two patches?