Hi everyone,
After a year of using my computer, a few days ago I discovered that I have a 64-bit processor , no information on the computer labels indicated this, so I happily used my computer in 32-bit mode for very close to a year. After my shocking discovery, and not having any 64-bit windows os to use, I installed Ubuntu 7.10-Linux 64-bit OS, hoping to try out some 64-bit assembly programming using fasm. I've already downloaded the fasm package and have it in my "documents" folder. but when I run the terminal program and change to fasm directory, the fasm executable wouldn't execute, It keeps giving me an "command not found" error message. Can any one help me out here? (by the way, I'm making my first post on this forum using Ubuntu Linux! )

erm, just to be sure... did you type "./fasm" instead of just "fasm"? second one searches in "/bin" directory

Thanks vid! That worked. but I copied hello64.asm/hello64.exe to the main fasm directory and tried to compile it and gave me a "source file not found", how could that be?

if you have both FASM executable and source (hello64.asm) in current directory, then it should be simply:



just like in WinXP cmd.exe, you can use TAB key in console to finish path to file - this way you can check if path to file is okay

And remember to add execution permission to the file (chmod +x exe-file).

Thanks Vid and Locodelassembly, I've got everything to compile now. Does anybody have any 64-bit assembly examples of making a window? I'm using the gnome interface.

Yes, Feryno provided some http://flatassembler.net/examples/fasm_amd64_linux64_samples.tar.gz

Bazik provided some examples for GTK http://flatassembler.net/examples/gtk-examples.tar.gz , but these ones are for 32-bit.

Or here
http://board.flatassembler.net/topic.php?t=7490

Thanks.

also if you want to execute fasm instead of ./fasm, you can add "." (single dot) to your PATH environment variable (e.g PATH="${PATH}:.") which means adds the current directory to the PATH environment variable.

I wouldn't suggest doing that, it's pretty bad practice.

Well mainly for the reason that if you want to execute fasm instead of ./fasm you can't unless you reset the PATH variable.

wouldn't it be better to copy "fasm" to "bin\", instead of hacks like this?

So anything that is command line only, copy it to the bin directory and you won't have to type the './'?

yeah, on unix like systems, "everything has it's place", and "/bin" is place for executable binaries. Not just command line, all binaries.

in fact, there are more such directories, for different types of executable binaries: /bin, /sbin, /usr/bin, ...

Check the Filesystem Hierarchy Standard for deep info about this.

That's what makes unix based operating systems so nice -> its much more structured than windows.

Until you look at different distros...

it just for convinience.. when i was new to linux, i tend to forget to type "./" in front of any program in my project dir. but anyway, the key here is the "PATH" environment variable.. if you have any non-standard place where you want to put your binaries, add them to the PATH variable. Windows has it also.