Hyperion Entertainment Message Boards

Reth wrote: Regarding the native AOS4 build of GCC and G++ - can it be just downloaded and installed over existing SDK installation?

Instead of installing over the SDK gcc it's recommended to extract the adtools gcc in a directory of it's own, and then add something like the following to S:User-Startup after the SDK commands:

;BEGIN adtools-os4-20171209-407
path GCC:bin REMOVE
assign GCC: Development:adtools-os4-20171209-407
path GCC:bin ADD
;END adtools-os4-20171209-407

This way you can easily switch back to using the SDK gcc should you need to for some reason.

Also it is recommended that you remove APPDIR: from the Path command in S:Startup-Sequence if you have it there as it can cause the old gcc to still be used even after making the changes to User-Startup.

Also you might want to delete any files from "adtools/bin" that are not also in "SDK:gcc/bin". IIRC the adtools gcc used to include a compile of coreutils that wasn't working so well (this may or may not have been fixed since then?).

Thank you. Regarding the adtools - do I need more than the native-build/ part (e.g. the gcc drawer + binutils drawer +x)? Or is it described somewhere what exactly to download and to install in order to get a most up to date toolchain up and running (I am using C++ ATM)?

Ready compiled binaries can be downloaded from Aminet:

http://aminet.net/package/dev/gcc/adtools-8-os4

If you want to compile adtools gcc yourself you need to clone the adtools git repository and follow the instructions in the readme.

git clone https://github.com/sba1/adtools

Thanx again! Checked the adtools readme. It states that a SDK-Assign is also needed. Can the SDK assign of the standard SDK installation be used here or will this conflict with the adtools stack?

Reth wrote:Thanx again! Checked the adtools readme. It states that a SDK-Assign is also needed. Can the SDK assign of the standard SDK installation be used here or will this conflict with the adtools stack?

Yes, an existing SDK installation is expected and required.

The commands I quoted are for moving the GCC: assign to the adtools directory (SDK:S/gcc-startup sets it to SDK:gcc) and ensuring that only the correct GCC:bin is in the command path.

Thank you! Does gdb work with this new GCC/G++?

One year later.. I'd also like to know.

GDB never worked correctly with any GCC version.
Too much things broken and unimplemented.

As long as there isn't a new correct port you'd better not rely on it.
There is a new player on the game, called spotless on os4depot.net, but it's an early wip