Hello everyone!

This is a version of FASM that can be used with BeOS. It's now at version 1.56. The icon that theuserbl contributed can optionally be added to the binary. I've tested this under BeOS R5 Pro; reports on using it with Haiku or Zeta would be appreciated as well.

To build and install it, run make. This should work under GCC 2.9x and 3.x, but I haven't tried it under the 3.x versions yet. If you want the icon to be added to the binary, also run make icon before installing it.

I'll try not to take as long between updates in the future.

The latest version can now be found at BeBits! See http://www.bebits.com/app/3917 for the BeBits page on FASM

One small note: I think you should pass the parameter that you've got in AL on the entry to "exit_program" routine to the "exit" call. Because without this it's not possible to check whether there were some errors from outside the program.

I'm making headway with the exit routine, but it's not quite there yet. Is there an easy way for me to print the exit code BEFORE exiting, so I can isolate the problem more easily?

I updated the attachment in the first post to version 1.55. There are a few additional improvements to the build process as well. See the updated text for details.

Hi

I build fasm from source for BeOS, but when i run it i receive error "fasm has encountered an error which prevents it from continuing. The BeOS will terminate the application and clean up". Details shows this:
"
Thread Name: fasm
Error: segment violation

Team ID: 597 Thread ID: 3440
EIP: 0x80005f1f
"

What should i do?

Thanks

stanks

What version of BeOS are you using?

BeOS R5 MaxEdition v3.1

gcc v2.9

Try this:

In source/BeOS/system.inc change:

Code:

exit_program:         ccall   free,[additional_memory]         mov     esp,[stack_frame]         pop     ebp   cmp eax, 8   jnz .a   mov eax, 0 .a:     push dword eax         call exit         ret

to:

Code:

exit_program:         push dword 0         call exit         ret

Recompile and the new binary should work properly. I'll see about fixing the exit function when I start on the port of FASM 1.56 for BeOS in a week or so.

Still same problem.

Now I'm very confused. That *should* have worked

Maybe the problem is with my BeOS installation. I don't know either.

This is happening (probably) when fasm have to show usage info. Maybe i can help? How to debug it under BeOS?

Try this: http://www.retroforth.org/dev/fasm156-crc.tar.gz

If it fully rebuilds, you'll have a working copy of Fasm 1.56 for BeOS.

New fresh installation of BeOS but same problem. np ... v1.53 works ok.

stanks

hello,

ANYONE can you tell me exactly how to make fasm executable

to run on BeOS.......

thanks

newbie

hamoz, try this in a Terminal:

Code:

wget http://flatassembler.net/fasm-1.67.tar.gz tar xzvf fasm-1.67.tar.gz cd fasm gcc fasm.o -o fasm

That should create a FASM binary that you can use. I'll revive my build farm in a few weeks; then I should be able to provide current FASM binaries for BSD and BeOS users. (My current contract job is nearly done; it's tied me up for the last few months)