-
JamminUnit
Any news regarding the rust-1.56 front? I still would like to see some sm release compiling with it.
-
njsg
JamminUnit: I think WG9s's builds are already built with rust 1.56
-
JamminUnit
njsg: so where can I grab the patches for seamonkey-2.53.10b1? :D
-
WG9s
444444444444444444444444444444444444444444444444444444444444\\\\\\\\\\Iiiii';
-
WG9s
U&
-
WG9s_
good morning Bellla!
-
tomman
-
tomman
and of course, it has to be a goddamned bank
-
frg_Away
-
TheSHADOW
Howdy. Got a couple of bug reports, probably noticed before but I'd like to mention them...
-
TheSHADOW
1. Following a direct link to a youtube channel doesn't work. eg.
youtube.com/c/NASASpaceflightVideos Using latest version of Seamonkey, note that Noscript is also in the mix. Can anyone verify this?
-
TheSHADOW
2. Wayback machine link on
archive.org disappears behind other page elements, no way to enter a link. Verification also requested on this.
-
njsg
for 1) there have been reports on newsgroups and here of some youtube pages showing up blank, that might be related to user-agent sniffing; login state was also leading to different outcomes?
-
njsg
It's always possible some videos are missing because Scripp News took them down, of course
-
njsg
and noscript - how's noscript configured regarding youtube and google? youtube does require javascript, I think
-
njsg
for 2) I've been just assembling archive URLs directly, I don't think I've tried to enter these in the front page, let me see
-
njsg
"redirecting you to a lite version of archive.org", fancy
-
njsg
which is... JSON?
-
njsg
ah no, it shows a link to a json document, but that's not the actual redirect
-
njsg
okay, they've changed this recently, it's not caused by seamonkey changes, the home page is definitely different
-
TheSHADOW
njsg: I've disabled all blocking on noscript with the same result, though noscript's presence might be doing something.
-
TheSHADOW
Huh. Opening that channel page in a private window resulted in the page coming up, so it is login related.
-
TheSHADOW
And yes, it shows up as blank except in the top elements.
-
njsg
until there's a solution for archive.org,
web.archive.org/address-goes-here should be enough if there's a stored snapshot
-
njsg
saving should work with /save/address but that hasn't been working properly for months (years?) now, sometimes works, sometimes works but fails to load the saved copy, sometimes fails
-
JamminUnit
frg_Away: thank you. It worked! :D
-
TheSHADOW
If I sneak up to the channel page, searching for it and clicking the link in search, it works. Hit it directly, and blank.
-
TheSHADOW
And clicking "send feedback" to report the problem gives me a 403 error, lol.
-
WG9s
JamminUnit: are you a Vob Marley fan?
youtube.com/watch?v=oFRbZJXjWIA
-
JamminUnit
WG9s: not really, but that music is very nice :)
-
frg_Away
seems archive.org uses now some adavanced css features whatever they are.
-
WG9s
i suppose could be same failing clang-13 new warnings
-
WG9s
oops worng channel
-
mlh85386
frg_away: I went one step forward with the rustc cross-compiling problem. I was confused by the fact that rustc lists the needed target i586-unknown-linux-gnu (for CPUs without SSE) when asked but a component for this target had to be installed with rustup. Having done this, I get different binaries when compiling a simple file like helloworld.rs. Transferred the my old hardware, only the...
-
mlh85386
...binary build with rustc --target i586-unknown-linux-gnu works. The other shows "Ungültiger Maschinenbefehl".
-
njsg
and with LC_ALL=C before the command? :-)
-
mlh85386
Having found out this, I introduced ac_add_option --target=i586-unknown-linux-gnu in the mozconfig file and no my host is about to build.
-
mlh85386
njsg: "Illegal instruction" is the evil formula you wanted to read, didn't you? :-)
-
mlh85386
-
WG9s
mlh85386: I comile using i686-pc-linux-gnu
-
WG9s
dont you lov it when someone askes for help and then disconects!
-
WG9s
Oh you nare back I do my 32-bit builds by using the target i686-pc-linux-gnu
-
njsg
mlh85386: for what kind of processor was this?
-
mlh85386
njsg: For an AMD Duron
-
mlh85386
wg9s: It's one of the mysteries of rust, when to use i686-pc-linux-gnu and when i686-unknown-linux-gnu. We will see whether this leads to new problems
-
WG9s
my processor is amd also
-
WG9s
of course you might need to do a rustup target install i686-pc-linux-gnu
-
WG9s
perhbaps you should do a rustup target list|to see what targets are avalable for your rust version
-
mlh85386
wg9s: the i686-pc-linux-gnu was provided by default, (no cross-compiling)
-
WG9s
so I think that is what you shuld try
-
WG9s
it works for me
-
frg_Away
WG9s much older CPU. Won't work.
-
njsg
i686-pc-linux-gnu is probably the default on a GNU/Linux system on IA-32
-
mlh85386
wg9s: with i686-pc-linux-gnu, the SSE2 set of instructions will be used and the binary does not work
-
WG9s
i do my 32-bit builds whidh seem to work for everyone who has tried on 64-bit os with 64 bit tools so specify that as the target and all seems well
-
mlh85386
rust documentation says i586-unknown-linux-gnu is for CPUs without SSE2
-
WG9s
OIC your processor does not have sse2 instructions?
-
mlh85386
wg9s: This forces me to build Seamonkey
-
» njsg would expect i586 to be "for pentium or newer" :-P
-
WG9s
so you are corect i586-unknown-linux-gnu should be corret for that. hmm
-
WG9s
wonder if this is a SeaMonkey issue or a Mozilla issue
-
njsg
and then... why not i586-pc-linux-gnu?
-
WG9s
njsg: perhaps because that target does not exist?
-
njsg
mlh85386: and yes, thanks for the "Illegal instruction". I need to learn German.
-
WG9s
these are the 32-bit targets that exist
-
WG9s
i586-pc-windows-msvc
-
WG9s
i586-unknown-linux-gnu
-
WG9s
i586-unknown-linux-musl
-
WG9s
i686-linux-android
-
WG9s
i686-pc-windows-gnu
-
WG9s
i686-pc-windows-msvc
-
WG9s
i686-unknown-freebsd
-
WG9s
i686-unknown-linux-gnu (installed)
-
WG9s
i686-unknown-linux-musl
-
mlh85386
wg9s: It is a mozilla issue. But the mozilla documentation is poor. Fortunatly linuxfromscratch made me hope being able to compile Seamonkey it on my own. They delivered as well a mozconfig file to start with
-
mlh85386
njsg: I only teach bavarian german :-)
-
WG9s
mlh85386: so when i ask is this a mozilla i mean a mozilla issue versus a SeaMonkey issue. can you build the latest firefox and get it to run?
-
WG9s
if not then file a mozilla bugzilla bug on the issue
-
mlh85386
wg9s: I did not try. The firefox from Debian Buster worked out of the box. But crashes too often.
-
WG9s
well then try filing a bug agianst the Debian Buster version about the crashing issue would be my ingestion. rather than trying to roll your own build.
-
mlh85386
wg9s: I do not like working with Firefox. It serves just as substitute until a Seamonkey-Version works with the current Debian release.
-
mlh85386
It's getting late. The build will take several hours. Good night.
-
frg_Away
WG9s SSE2 is mandatory since around 53 or so.
-
WG9s
mlh85386: so seems frg_Away is saying we no longer support non SSE2 PUas
-
WG9s
cpus
-
WG9s
beacuse moazilla/Firfos no longer does
-
frg_Away
Yes. 100% unsupported in 2.53.x and already for Windows in 2.49.x
-
WG9s
mlh85386: so for SeaMonkey might need ot stay on 2.49
-
mlh85386
wg9s: I know. 2.49 was the last version that worked. 2.53.1 was the first I built on my own last year. I only hope that it's possible to compile 2.53.9.1 as well now.
-
mlh85386
I will see tomorrow and I'm going to inform you.