Generating Executables in Linux Environment

flat assembler
Message board for the users of flat assembler.

Index > Linux > Generating Executables in Linux Environment

Author

Thread

0xArjun

Joined: 27 Nov 2018
Posts: 3
Location: India

0xArjun 27 Nov 2018, 09:17

In Windows platform, I can use the statements:
format PE console
include 'win32a.inc' ; Already added as an environment path

But in GNU/Linux when I try the above code segment, and run using the terminal, I get an error as 'win32a.inc' not found. Is there a way I can generate .exe in GNU/Linux with no errors? I am a 19 year old x86 programmer. Sorry in advance if my query is out of scope.

Description:		Download
Filename:	first_program.asm
Filesize:	459 Bytes
Downloaded:	776 Time(s)

_________________
0xArjun

27 Nov 2018, 09:17

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20300
Location: In your JS exploiting you and your system

revolution 27 Nov 2018, 09:23

Yes.

You can add/copy the files from the windows download into a folder in your PATH in Linux.

Make sure that that capitalisation matches exactly in Linux. In Windows this is not checked, but Linux requires it to match..

27 Nov 2018, 09:23

TmX

Joined: 02 Mar 2006
Posts: 841
Location: Jakarta, Indonesia

TmX 27 Nov 2018, 09:41

Try running the Win32 version of FASM on Linux with WINE.

27 Nov 2018, 09:41

0xArjun

Joined: 27 Nov 2018
Posts: 3
Location: India

0xArjun 27 Nov 2018, 16:21

I don't want to use wine, I want to use the "apt-get install fasm" version. Can anyone provide a reply as what I should write instead of "include win32a.inc" in order to generate an executable using GNU/Linux?

_________________
0xArjun

27 Nov 2018, 16:21

revolution
When all else fails, read the source

Joined: 24 Aug 2004
Posts: 20300
Location: In your JS exploiting you and your system

revolution 27 Nov 2018, 23:12

0xArjun wrote:

Can anyone provide a reply as what I should write instead of "include win32a.inc" in order to generate an executable using GNU/Linux?

You don't need to write anything different. What you need is to have the file win32a.inc, and the other windows header files, in your INCLUDE path.

27 Nov 2018, 23:12

< Last Thread | Next Thread >

Forum Rules:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum