SDK addon package

@walkero

Thank you for your work!

@walkero

SDK/gcc/ppc-amigaos/bin/lib/gcc/ppc-amigaos/13.4.0/ has a CLIB4 drawer, shouldn't it be removed?

and I get:
gcc: warning: switch '-gstabs' is no longer supported

So -gstabs no longer works, then should use dwarfs/dwarfs2 ?
Does GR "support" dwarf debug?

@jabirulo

Quote:

Yeap, it is needed, just like it has the clib2 and the newlib libraries.


Quote:

Yes, that's right. gstabs where removed in gcc13


Quote:

I believe that dwarf/dwarf2 is the way to go, but I haven't tried that yet.

I am not sure if GR supports dwarf/dwarf2. Maybe it will need to be updated.

@walkero
Quote:
I assume this is the same as the release found on Hyperion's site?
If so, installed and working. Thanks!

@ktadd

Nah the new SDK release on the Hyperion website would be different and not support clib4.

---

Edit: Walkero below says clib4 is now supported by the gcc 6 and 11 compilers included in the official SDK. It's just clib4 itself that's not preinstalled.

Edit 2: Even though the compilers recognize -mcrt=clib4, the clib4 gcc linker libraries (libgcc.a libstdc++.a etc.) are still missing without SDK_Addon.

---

I've also noticed the paths have changed between official SDK 54.16 and 54.25, but 54.25 matches the paths SDK_Addon uses.

For SDK 54.25 and SDK_Addon 1.7.0, it doesn't put the newlib gcc linker libs into a dedicated newlib directory, and the location has changed in other ways too.

SDK 54.16
SDK:gcc/lib/gcc/ppc-amigaos/11.2.0/newlib/lib/libstdc++.a

SDK 54.25 and SDK_Addon 1.7.0
SDK:gcc/ppc-amigaos/bin/lib/gcc/ppc-amigaos/11.5.0/libstdc++.a

When you go to install 54.25 it does warn that installing on top of an existing SDK is not supported. As for SDK_Addon, it's probably ok to install over SDK 54.25.

@MickJT
Quote:
Ok, so it sounds like I should install a clean SDK based on 54.25 on Hyperion's site. Then install this addon package.
Thanks for the info.

Will this end up causing conflicts with any updated SDK that Hyperion might release in the future?

Why the hell doesn't the new SDK include the addon??

It seems on the Amiga world we always have to make the most abstruse and incomprehensible choices...

@samo
Like you discover amiga yesterday ?:)

But for real, why should Hyperion with limited resources, handle more than they can handle? Addon what George do it's all what done in experimental manner, highly untested but on some bits, which can't fits for official real SDK too fast as who know what it will bring. See : latest GCC remove -gstabs support, and that discovered only now , so if Hyperion include that to SDK, without proper support of dwarf in GR everyone will cry loud. But what you want then, Hyperion release nothing for one more year then because of needs of many other improvements ?

So, Hyperion release what they can , minimum baseline which stable and prove to be ok. Then, you can on top play with it as you wish. Yeah, may sounds boring, but such a limited resources. By exactly same reasons SDK shouldn't have 3d party libraries too, because it mean to HANDLE them in actual shape. It's all can and should do 3d party developers too. And George with his addon probably add some of them too (not sure even if addon have all 3d party libs from os4depot, as it nightmare to handle).


And in end, the ones who want : do. The ones who don't, find a problem to use original SDK or update original SDK with experimental addon if they need it at all. The baseline SDK already provide all you need. Just do what you want to do.

@kas1e

I think the Hyperion SDK should necessarily include the latest clib4, which is becoming an increasingly indispensable tool for modern applications... and the latest compiler wouldn't hurt either...

Let me clarify a few things that they might already been mentioned by Roman.

1. The official SDK released by Hyperion has all the software you need to develop for AmigaOS 4. This is also what is used for the OS development. That's the stable SDK that you should start with.

2. clib4 is supported by the official SDK, but not included. The gcc11 and gcc6 that come with the official SDK, support clib4. To use it you need to download the clib4 for OS4Depot or the AmigaLabs github repository and use the included installer to install it.

3. The SDK AddOn, is a more experimental package that adds more features into the official SDK, i.e. the new gcc13. Later versions might include newer binutils, etc. This addon should be installed on top of the official SDK, and it doesn't touch the header files or something else.

4. The purpose of the AddOn is to have a package withh all the latest work that AmigaLabs team is doing on our development tools and have frequent updates. Any fixes and improvements will go into the SDK Addon for those who would like to try them and provide feedback.

If there are ideas of a different way to share these updates, or if you need additional information, please let me know.

One more thing.
Now that we have gcc13 working and the gstabs are not used any more, look at it as a good opportunity to create new tools that would use new debug methods.

If Hyperion wants to update GR to support it, that would be great. It is their decision, I guess.

Quote:

I just saw that I was wrong on the above. It seems the SDK 54.25 have the clib4 code removed from the compilers. So, it is necessary to have the SDK Addon installed on top of the official SDK to use the clib4. Alternatively, you have to compile the gcc compilers yourself.

You are welcome to contact me if you need anything.

@walkero
Thanks for the clarification and the work you are doing with the SDK addon. It's good we have people to help push things in a forward direction given the limited resources in the OS4 world, even if it adds some complications.

@walkero
Are you sure -mcrt=clib4 not there ? It should (at least it wasnt specilly removed from compiler, maybe just clib4 libs leftovers). Jyst grab gcc11 binary on clib4 word

@kas1e

While the various gcc versions in SDK 54.25 recognize -mcrt=clib4, the gcc linker libraries for clib4 are missing such as libgcc, libstdc++ and others, so SDK_Addon is still required at the moment.

@MickJT
Quote:You don't need to change anything in the gcc nor binutils sources to add support for additional C libraries, you only need to add support for them to the "specs" and maybe "script.ld" files. At least that was the case in GCC 2.95.x and 3.x.y where I added support for the libnix, ixemul, and in very early and obsolete clib2 builds of GCC/binutils, newlib as well, C libraries by just adding them to the specs file, using the unmodified GCC and binutils executables.
libgcc is, or at least was 20-25 years ago, independent of the C library as well and the same libgcc.a (at that time with some bug fixes and optimizations from me) was working with all of the 4 C libraries I had in my specs file.
Only for libstdc++ you need different versions for each C library because datatypes like FILE, off_t (32 bit in obsolete AmigaOS C libraries like libnix, ixemul, clib2 and my ancient newlib port, 64 bit instead in anything still usable), etc., are different in different C libraries.