Strange. Development:bin should be already available among PATHs, since the startup-sequence should execute Development:S/package-startup, which includes these lines:

Quote:

I have just looked at a test Icaros virtual machine, and the path command lists also AROS:Development/bin among the available ones. So I guess your only issue was with your former virtual machine. Maybe setting the 64bit option enabled some weird virtual SCSI controller in your "hardware" and it gave issues. Happy it's been resolved, anyway.

Your message, in any case, showed me that I had repeated the ASSIGN usr: and lib: two times and this led to a double assignation to the same directory, which might not have been harmful, but it's ugly to see. I deleted the repeated lines in icaros-sequence and this should enhance things a little.

Anytime.

Quote:

That is great, then we can have hacking school together! :)

Quote:

I'm constantly switching between Bash, ArosShell, AmigaShell nowadays.. I can't separate %?#% from a ?#?% anymore.
Confusing

SUCCEEESSSSSSSS!!!!!!

@elwis I think you were right.

So I was running AROS in a Virtual Box VM with the Operation System set to Other/Unknown(64 bit).

I tried a fresh Icaros install from a downloaded 2.2.1 ISO (as with the VM above) but this time set the OS to Other/Unknown. In the new VM, gcc and g++ ran from Development:bin but not elsewhere. I ran "path Development:bin add" and everything worked.

On the 64 bit VM gcc and g++ do not run from Development:bin and adding this dir to the path had no effect.

Case closed...?

Thank you so much to everyone for your help with this. Now time to start hacking away!

Quote:

To use find, just type find from the shell. Or to get help with AROS commands type help.

Typing sh will take you to a bash like shell but it may not be what you want in this case.

Quote:

I just tried doing a Hello world on Icaros and it works.

Try changing the line to read, gcc hello.c -o HelloWorld
Nevermind, don't do that. It was just a stab in the dark.

Instead, I would completely reinstall Icaros and try again. You do not need to add any development files. It should be ready to go.

If that does not work, try using a ABIv0 nightly. Gcc should also work on the nightly without adding any extra files.

If you still have problems with a simple compile, then the machine might not be configured right, if possible try another machine.

If I remember correctly, putting the dev stuff together to make g++ in Murks work has been difficult. I believe that the include Development Drawer contained a working g++:

see:
http://archives.aros-exec.org/index.php?function=showfile&file=development/ide/murks-0.6.0.i386-aros.zip

But even if it still works, this stuff is about 10 years old...

To be honest, I don't even know how to search properly without bash...
I did however compile a simple c file myself, no problem.

It's not the usual 32/64 bit problem somehow?

That's my read on it too. Do you have cc1 or cc1plus anywhere on your AROS install?