.exe files from compiled with some compilers do not start from the tcc command line

[knudvaneeden]

Hello,

Is this maybe some known issue?

1. Compiled with Borland C++ e-bor.exe = starts foobar.exe in JPSoft tcc.exe? YES

2. Compiled wit CLang version 19 e-clang.exe = starts foobar.exe in JPSoft tcc.exe? NO

3. Compiled with GCC: e-gcc.exe = starts foobar.exe in JPSoft tcc.exe? NO

4. Compiled with Microsoft e-msvc.exe = starts foobar.exe in JPSoft tcc.exe? NO

5. Compiled with Open Watcom e-wcc.exe = starts foobar.exe in JPSoft tcc.exe? YES

===

But using Microsoft cmd.exe works all the time:

1. Compiled with Borland C++ e-bor.exe = starts foobar.exe using cmd.exe /c e-bor.exe YES

2. Compiled wit CLang version 19 e-clang.exe = starts foobar.exe using cmd.exe /c e-clang.exe YES

3. Compiled with GCC: e-gcc.exe = starts foobar.exe using cmd.exe /c e-gcc.exe YES

4. Compiled with Microsoft e-msvc.exe = starts foobar.exe using cmd.exe /c e-msvc.exe YES

5. Compiled with Open Watcom e-wcc.exe = starts foobar.exe using cmd.exe /c e-wcc.exe YES

When you run such a .exe by typing the .exe on the tcc.exe command line , typically basically nothing happens.

Used tcc version latest 36.52 build 88
but this seems reproducible in any earlier version of tcc.exe.
It never works thus.

Root cause: Maybe something with mandatory compiler options if you want it to let start in tcc.exe?

Note that Borland C++ command line compiler was in the past always used to compile that program
and that always worked. Now it is moved e.g. to CLang as a compiler and starting such .exe does not start
anymore from the command line. Similar for Microsoft MSVC and MinG gcc, it does not start.

 

[vefatica]

What is the EXE? What does it do? What is the exact failing command line you are trying to execute in TCC?

 

[knudvaneeden]

At the moment more interested if anyone has experience with some .exe not starting from the command line in JPsoft tcc command line. Let say the name is foobar.exe. So you type that name foobar.exe then press enter. After a slight delay nothing happens. Expected is that the program starts doing or showing something. Running the same executable in cmd.exe either by typing that cmd.exe in tcc and then running foobar.exe or otherwise similarly typing cmd.exe /c foobar.exe in tcc works fine, no issues.