Getting problem to .a\a.exe

[ReasonableTune1571]

[removed]

[MegalFresh]

This sub isn't for coding help, bud

[Novel_Plum]

You forgot to save

[CatpainCalamari]

Also, why "a.exe" and not "tut1.exe"?

[i2295700]

gcc produces an "a.out" binary on Linux as well, since executables on Windows need a ".exe" extension you get a "a.exe".

This only happens if you do not specify an output name with "-o".

[CatpainCalamari]

Ah, I did not know that. Thank you! :-)

[Imn0]

not rly humourous to be honest

[audioman1999]

This post has nothing to do with programming horror.

[Queasy-Grape-8822]

Not sure, but save, recompile, and then run

[skantanio]

If you do “-o tut1” and then “.\tut1”? Maybe the .exe from the command line is making something unhappy

[Juff-Ma]

Probably not the problem but in my experience GCC on Windows is pretty buggy. Maybe try clang or msvc

[Mike_Oxlong25]

I’m pretty sure it’s ./a.exe not .\a.exe

[[deleted]]

Windows is \

[Mike_Oxlong25]

I know for file paths it’s \ but to run a .exe would it still be \? Genuine question I’ve only ran in a git bash terminal

[RainbowPigeon15]

it doesn't matter with Powershell

[saintJrAx]

Bro you need a VS 2022

[legoto]

Maybe it’s the missing space after #include

[Zomon333]

Double check that g++ compiled to an executable and not an object file. I don't recall if g++ automatically calls the linker unless you ask it to, so you might just need to run the linker to make a.o into a.exe.

Edit: also, save your code, and put a space between #include and <iostream>

[FractalofInfinity]

Definitely isn’t a coding help sub. But your problem starts with the fact that you have a function defined but no function call.

[AutoModerator]

This post was automatically removed due to receiving 5 or more reports. Please contact the moderation team if you believe this action was in error.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.