Recent Posts

61

General (but related to Code::Blocks) / forums.codeblocks.org Cert has expired

« Last post by Wkerry on October 24, 2025, 11:10:45 am »

Some bits from the expired cert:

Common Name forums.codeblocks.org
Organization   Let's Encrypt
Not Before      Sat, 26 Jul 2025 07:51:01 GMT
Not After        Fri, 24 Oct 2025 07:51:00 GMT
DNS Name     forums.codeblocks.org
Serial Number   05:31:D6:45:C8:BE:C3:89:15:F5:4B:39:68:46:A8:E7:14:47
Distribution Point   http://r11.c.lencr.org/72.crl

62

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by nenin on October 24, 2025, 07:39:38 am »

I am sure that there is only codeblocks 25.03 mingw 64 bit version. I triple checked

You can switch on html logging and submit compiler logs here to figure out what compiler is used actually.

63

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by alfredo on October 23, 2025, 09:39:27 pm »

I have to manually change the compiler from GCC to mingw64 only for the third machine?

For me this is strange. What could be the reason?

Probably (or May be), on your 3rd config, there was already a 32b compiler installed somewhere. So, when you installed C::B, it's installer has detected this compiler and configurated it as the default one, instead of the compiler distributed with C::B. This could explain why you had to change manually the configuration and why it compiled before your changes.

I am sure that there is only codeblocks 25.03 mingw 64 bit version. I triple checked

If I manually force -m 64 on the first machine, I get sorry, unimplemented: 64-bit mode not compiled in..

The -m64 is not "manually forcing" anything, you set it to compile 64 bit programs. If the compiler doesn't support it you may get an error like that. Also, if you use sizeof properly the pointer size doesn't matter, whatever it might be.

A 64 bit compiler on 64 bit OS should compile 64 bit binary by default.

64

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by Krice on October 23, 2025, 05:42:03 pm »

If I manually force -m 64 on the first machine, I get sorry, unimplemented: 64-bit mode not compiled in..

The -m64 is not "manually forcing" anything, you set it to compile 64 bit programs. If the compiler doesn't support it you may get an error like that. Also, if you use sizeof properly the pointer size doesn't matter, whatever it might be.

65

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by gd_on on October 23, 2025, 04:15:13 pm »

I have to manually change the compiler from GCC to mingw64 only for the third machine?

For me this is strange. What could be the reason?

Probably (or May be), on your 3rd config, there was already a 32b compiler installed somewhere. So, when you installed C::B, it's installer has detected this compiler and configurated it as the default one, instead of the compiler distributed with C::B. This could explain why you had to change manually the configuration and why it compiled before your changes.

66

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by nenin on October 23, 2025, 02:56:13 pm »

That's clear. Can you explain why, on three different machines, with the same Windows 11 25H2 64 bit, the same Codeblocks 25.03 64 bit, and therefore the same mingw (GCC) compiler, with the same project (no copied and pasted code), I have to manually change the compiler from GCC to mingw64 only for the third machine?

• intel i5-11400 ok
  
• ryzen 7 7840u ok
  
• i5-10400 I have to change the settings
  

For me this is strange. What could be the reason?
Thank you

I cannot explain you this strange observation. I never faced these or similar problems, but I've never used a C::B distribution with a compiler. I`m using C::B now with 3 compilers ( 64b gcc 14.2, 32b gcc 14.2 and 32b for XP gcc 9.3) and C::B always keeps proper compiler in project, if this compiler is actually is installed. If compiler is not installed, strange things may happen, but not the one you described.

67

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by alfredo on October 23, 2025, 02:19:46 pm »

"sizeof(int*)==4"  means that you somehow generated 32b code. It is not dependent on C::B, by default C::B uses default compiler, and the choice of the compiler options is not affected by this selection. It may be OK for exact compiler or may be wrong. For example, if you put something like "-march=x86-64-v2" for 32b compiler, it will be unhappy. Check name of compiler in project options on top of the dialog. If it is something like "GCC MINGW64" - it should be 64b,  if "GCC MINGW" or "GCC MINGW32" - 32b.

That's clear. Can you explain why, on three different machines, with the same Windows 11 25H2 64 bit, the same Codeblocks 25.03 64 bit, and therefore the same mingw (GCC) compiler, with the same project (no copied and pasted code), I have to manually change the compiler from GCC to mingw64 only for the third machine?

• intel i5-11400 ok
  
• ryzen 7 7840u ok
  
• i5-10400 I have to change the settings
  

For me this is strange. What could be the reason?
Thank you

68

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by nenin on October 23, 2025, 01:24:59 pm »

"sizeof(int*)==4"  means that you somehow generated 32b code. It is not dependent on C::B, by default C::B uses default compiler, and the choice of the compiler options is not affected by this selection. It may be OK for exact compiler or may be wrong. For example, if you put something like "-march=x86-64-v2" for 32b compiler, it will be unhappy. Check name of compiler in project options on top of the dialog. If it is something like "GCC MINGW64" - it should be 64b,  if "GCC MINGW" or "GCC MINGW32" - 32b.

69

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by alfredo on October 23, 2025, 01:03:08 pm »

Okay. Can you explain why the same project created on the latest version of Codeblock on Windows 11 25H2 works fine on some computers but not on others, and I have to manually change the compiler? The settings are the same. In my opinion, it has something to do with Codeblock and its integrated mingw compiler.

"project" means  "software project in C::B" or exe file, generatated by mingw gcc using C::B?
At that moment I can only suspect that you somehow installed on one PC 32b version from here: https://sourceforge.net/projects/codeblocks/files/Binaries/25.03/Windows/32bit/

Right, a Codeblocks project with the code in the first post. You can compile it yourself on another computer (I can share it). No, I am 99.99% sure that I installed 64-bit Mingw bundled with Codeblocks. In fact, if I manually change the compiler settings, I can compile it correctly. My question is: why does the same project created and used by the same version of software and compiler behave differently on different machines with the same Windows 11 25H2 64-bit?
Moreover, why in such machine I have to manually setup the compiler to mingw 64 bit and compile with -m 64?
Thank you

70

General (but related to Code::Blocks) / Re: Windows 11: pointer size varies depending on computer

« Last post by nenin on October 23, 2025, 12:21:24 pm »

Okay. Can you explain why the same project created on the latest version of Codeblock on Windows 11 25H2 works fine on some computers but not on others, and I have to manually change the compiler? The settings are the same. In my opinion, it has something to do with Codeblock and its integrated mingw compiler.

"project" means  "software project in C::B" or exe file, generatated by mingw gcc using C::B?
At that moment I can only suspect that you somehow installed on one PC 32b version from here: https://sourceforge.net/projects/codeblocks/files/Binaries/25.03/Windows/32bit/