hmm tried adding lib as a symlink to lib64 .. but no help

we need to seek and locate where in the code it is.. It's too late for me to start digging into mozilla python lol

I'm not a kid anymore.. I get tired after being up 16 hours these days

;)

which is why I typically stop at 12 or 10

and relax more afterward

i need older cbindgen to build 71 .. too many things to make it work with newer

the code crashes cbindgen due to rust being terrible.. emillio fixed it.. well beyond the rust code compat range i need for the moment so screw him..

still further along than I HAVE gotten building anything past UXP unmodified

I still love configure/make much easier to trace down the simple things .. hard coded lib , missing #include or wrong path etc :) rust,python.meson(horrible lately for not honoring LDFLAGS when no .pc) etc

not using the mach runner directly can cause additional issues because its a superset

whats runner?

i would PREFER to use client.mk directly like the old days and I can.. but it doesn't ALWAYS work in EVERY situation EVERYWHERE like it used to ever since mach was added

mach is a command runner

but also sets up the environment

now too

in the build script(for packaging) ./mach build and the .mozconfig

ah yeah

oneforall2: remember you have a custom launcher creating a custom environment for a custom build system and configure system that also has to chain its horseshit to autohell and standard makefiles too

oh and its a mozilla codebase too

so already half custom in its setup anyway

let's do a test

oneforall2: build Pale Moon just to verify your environment is capable.. I say Pale Moon and not literally anything else because Pale Moon has build instructions..

it has nearly the same deps as seamonkey does but is still driven by python 2.7

if i .. and when I have had similar strange pythonic issues I verify by doing the same because I have screwed up my system that has rendered it unable to build anything properly .. still dunno how i did it but i couldn't reproduce with a new install so..

it's a residual benefit from years of driving home.. I will not play the commit revert commit revert commit revert commit release revert release again game more than a few times a year.

so UXP even today almost always stays building

Working is more of an uncertain aspect of that codebase these days.. but it will build.

I need to get out of this chair

peace

hey is there a channel for seamonkey on matrix ?

or iirc chat.mozilla.org

oneforall2: I was thinking you did mention a lib lib64 mismatch.. Didn't you mention your distro was somewhat custom as well?

there is a concept in virtualenv called platlib and purelib in a virtualenv

__version__ = "20.0.31"

Behavior changed in virtualenv 20

redhat likely alters their python packages to deal with it

which is why I haven't come across a lib/lib64 mismatch in paths

NOT TO MENTION

SeaMonkey 2.53's virtualenv only supports up to 3.9

in release

according to the virtualenv code

btw i figured out the real reason for comm under mozilla besides special provisions.. It's the only way the workspace hack would work it's a prereq

so its a rustism

Probbaly needs a backpport of bug 1732946

2.53.20 has lots more in already but not this one

"We're sorry but Tracking.postnord.com doesn't work properly without JavaScript enabled. Please enable it to continue."

even package tracking now requires the newest javascript and doesn't work on anything else than Firefox and Chrome...

to be fair its not exactly easy even if they wanted to to serve a modern expectation webapp without javascript. Keep that in mind.. even if some people would like to go back to server side and minimal js.. doing so may not be feasable for a number of reasons.. few technical but important reasons.. like the current web/primary/ mentality rather than good old fasioned webmaster mentality

I don't oppose to JS - used sparingly can enhance the end user experience (AJAX is actually nice to have, and not just in your kitchen!)

i actually disagree with ajax

the problem is frameworks adopting the very latest hot Chromeisms the very minute they ship on a Chrome alpha

for no good reason at all

that is A problem

but not THE problem

THE problem is with the entire WebApp concept

That's a industry-wide problem, yes

A problem with that is google forcing it and everyone using it to the exclusion of everything else

;)

context

but my biggest beef is with things that should not be app-ified becoming... apps

for example, informational websites

analog.com/en/index.html today's suspect. Analog Devices

tried to figure out if they still make audio codecs

instead found this... dog vomit

besides, generalities about who is at fault is quite a dangerous thing these days I am QUICKLY finding out.. must be specific and percise

because someone decided it was a bright idea to turn a corporate information site into an App-y Experience™

cirrus.com contrast with Cirrus Logic, which looks modern and yet works without falling apart

well i can't figure out what they do from their front page

(and yes, they still make audio codecs!)

i know what analog devices is just its a failure when the front page won't tell you or assume you already know

they have spent way too much time drifting into those newfangled "digital" devices, yes :D

I think they don't actually know what they do but they SURE AS HELL are doing it lol

from JUST the front page alone

look at the fish and the watch that programs a garden

and WINDMILLS!

tomman:

needs moar AI

tomman: AI controlled windmill fish?

and somehow we have a generation of programmers who are just simply unable to write vanilla javascript code

they literally don't know how to write stuff without using the latest megaframeworks

I don't understand how that's even possible

the frameworks don't do anything else than add some functions and classes

so how it is possible that someone can write stuff with them, but not without?

Sompi: that is why wasm

basically Sompi sophistication is one thing.. piling on abstraction after abstraction and only coding to that abstraction and then adding even more on top for PERCIEVED lacking support for things.. over 10 years you have a fuckin mountain of code that EVENTUALLY will be completely replaced by something else if not piece by piece never stopping never stabilzing never bothering

does that pretty well sum it up?

nsITobin will take a look and see if I can find a rpm src for python and see if it has that patch to deal with it.