New AmigaOS 4.1 SDK 53.34 is available now.

Please note that at this time GCC and the other tools were not yet updated but are scheduled for release with a new version of the SDK in the course of 2022.

So that nothing "big" but just being in sync with all the latest includes for released components and co.

There are what changes since the latest public 53.30 release:

SDK 53.33 (10.3.2021) - internal
- Updated AmiSSL SDK v4.7
- Updated expat v53.6
- Updated minigl SDK v2.24 2021-01-26
- Updated MUI SDK 2020R3
- Added execsg SDK 54.18
- Added dos SDK 54.112
- Added SDK from AmigaOS 4 Final Edition Update 1 (v53.31)
- Added SDK from AmigaOS 4 Final Edition Update 2 (v53.32)
- Added the missing dlfcn.h
- Added missing libdl.so link under local/newlib/lib
- Updated newlib to 53.62

SDK 53.34 (15.12.2021)
- Updated AmiSSL SDK v4.11
- Updated MUI SDK MUI-5.0-20210831
- Added execsg SDK 54.26
- Added dos SDK 54.117
- Updated SDK Includes and Autodocs


The next stage for 2022 is to have new SDK with all new GCC and stuff.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

A small Christmas gift, waiting for the full release.
Have fun with Amiga, always!

_________________
Pegasos II G4@1GHz 2GB Radeon 9250 256MB
AmigaOS4.1 fe - MorphOS - Debian 9 Jessie

@kas1e

Thanks, I have not had time to look at it, will do in the next week or two.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@kas1e

Hyperion's site indeed lists this product, but when I click its link, all I get is a message stating that the file does not exist. Funny...

OldFart

_________________
More then three levels of indigestion and you're scroomed!

@OldFart

Checked now: works.

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@kas1e

Much needed updates. No AmiUpdate?

Updated GCC components will be the big one. If GDB ever works again it will will be very welcome addition. Debuggers tend to come and go on OS4 with no fully working solution.

No HP printer driver making a come back? This was removed some years back. Never mind I uploaded it.

Last edited by Hypex on 06-Sep-2022 at 01:02 PM.

I downloaded this a while ago. As my SDK over the years had become a bit of a mess with additions and beta files I thought it would be best to get something that should work straight out of the box with the latest OS4 update 2.

However evertime I try to compile somethying I get the following message:

assertion "cached == 0" failed: file "../../gcc/libcpp/line-map.c", line 277
cc1: internal compiler error: Aborted

Any ideas as to what this is and how I get rid of it.

Does anyone else get this weird message. Surely as it was downloaded from the Hyperion site it should work without any need for alterations ?

@BillE

Sound like you should do a clean installation of the SDK.

When I have strange problem, I don’t understand, its often due to defines, one way to understand, what is going on, is to use the “-E” this will tell GCC to only run the pre-compiler. “-o” will return a text file, instead of a binary.
Now look for line with error, in output file.

Last edited by NutsAboutAmiga on 06-Sep-2022 at 12:47 AM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@BillE

How have you managed it? I also add stuff to my SDK and manage it ok. But I only add stuff to Local folder and don't modify anything else.

This is the accepted way put forwards years ago. So every new SDK, I move my Local folder out to keep it safe. I then delete the SDK contents. And disable assigns.

After reboot I install new SDK fresh. I then move my Local folder back in. And my SDK update is complete with all my additions intact. If only updating OS4 was as easy. Still some manual effort required but mostly trivial.

@BillE

Does you compile refer to a non existing dirctory? That can cause odd compiler errors like this.

ie

gcc -o foo foo.c -I"Some included directory that doesn't exist"

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@NutsAboutAmiga

Quote:

Sound like you should do a clean installation of the SDK.

That is exactly what I did, I only got the problem with the freshly installed SDK.

I will have a look at using the -E option so thanks for the tip.

@Hypex

Quote:

How have you managed it? I also add stuff to my SDK and manage it ok. But I only add stuff to Local folder and don't modify anything else.

Easy, a lot of beta files had been installed.

So I wanted to get back to a plain SDK that just had public files only and the availability of a new and updated SDK for OS4 Final uipdate 2 seemed to fit the bill perfectly, except it does not work as I mention above.

@BillE

Quote:

Easy, a lot of beta files had been installed.

Okay, so beta system files? One thing I didn't have is SDK on a beta volume. But just need to assign it.

Quote:

So I wanted to get back to a plain SDK that just had public files only and the availability of a new and updated SDK for OS4 Final uipdate 2 seemed to fit the bill perfectly, except it does not work as I mention above.

Do you have a Workbench with no beta files it can work on? Or test with after assigning the SDK?

@Hypex

Quote:

Do you have a Workbench with no beta files it can work on?

My main partition is a recent install of OS4.1FE Update 2 plus Enhancer 2.2, but not the replacement commands. The beta list these days seems mostly about the X5000 which I don't have so the beta partition gets less use now.

The SDK 53.34 was a red herring as I get exactly the same with the old SDK.

There is more info at.
https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=8957

@BillE

Quote:

My main partition is a recent install of OS4.1FE Update 2 plus Enhancer 2.2, but not the replacement commands. The beta list these days seems mostly about the X5000 which I don't have so the beta partition gets less use now.

Okay. Mine is similar. I have up to Update 2 with Enhancer 1.5, and no replacement commands, but do have installed replacement Pref editors. When I bought it that was the latest.

I checked and I do have SDK 53.34 installed and working.

Quote:

The SDK 53.34 was a red herring as I get exactly the same with the old SDK.

Okay. Just checked how I compile. I do actually compile to RAM also. So I CD into my source directory in shell. I run a script that compiles it from sources to RAM for testing. I just have one line using gcc with some options to compile my main C file into RAM. The other sources are included in from my main source. I refer to ram disk as RAM:

Read the Amigans thread. Have you tried running Snoopy? And do you have a simple example you can make up for reproducing it?

@Hypex

Quote:

Okay. Just checked how I compile. I do actually compile to RAM also.

I compile from RAM: to RAM:

I copy all the source files and all the obectfiles to RAM: and then compile there. That way I do not change any of my files on hard drive until the code id doing what I want.

So its probably compiling FROM RAM: that is causing the problem ?


Edit:

I just tried creating a RAD: disk for a test. Compiling from that does NOT give the error message. This method also has the advantage that it should survive a soft reboot.

Last edited by BillE on 10-Sep-2022 at 10:11 AM.

@BillE

Quote:

I copy all the source files and all the obectfiles to RAM: and then compile there. That way I do not change any of my files on hard drive until the code id doing what I want. So its probably compiling FROM RAM: that is causing the problem ?

After some testing I don't think so. But our systems are different.

I tested dragging a project folder to my RAM disk and CD to it in a shell. It compiled fine.

I then wiped it and copied the source files direct into RAM disk root and CD to it. It also compiled fine.

It seems for once I am unable to produce a bug.

Quote:

I just tried creating a RAD: disk for a test. Compiling from that does NOT give the error message. This method also has the advantage that it should survive a soft reboot.

Yes that would be an advantage and good to know it still works.