DiscordMessenger/dm

Build for old no SSE2 CPU (Pentium III\Athlon Xp)

Opened this issue · 9 comments

Hello, can any one help me with more noob friendly step by step instruction to build Discord for older no SSE2 system, like Pentium III or Athlon xp?
Or request to author of this project to build parallel with main P4 package, version for no SSE2 in releases?

The pre-built MinGW version shouldn't use SSE2 instructions. Are you running into "Invalid Opcode" exceptions?

If yes, and you're willing to build it yourself, you may opt to add a compiler switch such as -march=pentium or similar, and you can add them to https://github.com/DiscordMessenger/dm/blob/master/Makefile#L69 (CXXFLAGS). See a complete list here: https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html

As for OpenSSL I believe the precompiled version does not use SSE2 instructions as I haven't had trouble opening the app on Windows NT 4 (it won't run but that's a wholly different story)

The pre-built MinGW version shouldn't use SSE2 instructions. Are you running into "Invalid Opcode" exceptions?

Yes I run MiniGW and have error. IMG_20240731_134049.jpg

I am not developer or programmer at all, so to understand all specific stuf how compile this project from scratch is to hard for me.

I request some step by step faq, how any one with zero knowledge can build it.
But how I gest now one interest about it and you must learn all this stuf by yourself.

Can you copy the error report and send it here?

Can you copy the error report and send it here?

yes sure, but i don't know if its correct log.

8f84_appcompat.txt

Not sure... isn't there a way to get a registry dump or something?

DID I SAY REGISTRY DUMP? sorry, I meant crash dump

DID I SAY REGISTRY DUMP? sorry, I meant crash dump

Do you mean this window?
It's don't copy by any way. I can only screenshot it but it's very long and be annoying
IMG_20240802_123615.jpg

.txt file from \Temp I copy in previous post.

Damn. Seriously looks like a bad instruction. And it looks like it's the fault of OpenSSL actually. That's... so weird.

Damn. Seriously looks like a bad instruction. And it looks like it's the fault of OpenSSL actually. That's... so weird.

If I can help with some tests, just ping me in this thread.