@tonyw

So this pretty much sounds like what I have experienced. Looking forward to fix.

Thanks
Doug

I don't know if the battery on my X5000 ever has worked. Technically its not required to make this machine boot.

Changing the battery I have never found the clock to survive turning off(or unplugging) the the Power Supply. I have just given up it ever working and use utilities to update time at reboot and don't turn off Power supply.

Considering the MB is pretty niche I suspect there are all sorts of bugs/issues and we have to accept them as that. But from a reliability stand point. For a machine I don't use as much as primary PC. I have had RAM fail, Power Supply fail, video card fail, clock does not work.

Don't get me wrong I like my machine and playing with OS4.1 but there is some wonky stuff in these forums relating to stability issues with the X5000 hardware.

Doug

@afxgroup

Ill give a shot at rebuilding toolchain time permitting. This might get my LLVM port back on track. I had tabled it due to lack of ability to get shared libs as the executables because unduly large linking int 30+megs of C++ runtime. It also made JIT difficult to work with as the symbols for basic Clib functions are not visible.

Now to find time to rebuild it all.

Doug

@afxgroup

I am pretty excited about the shared library support. Question has anyone build cross compiler with shared support for C++?

Regards
Doug

@walkero

I personally prefer the Ctrl as that pretty much is across Windows/Linux and other IDEs.

Regards
Doug

@walkero

Very nice! I have tried most editors available, like this alot that it with Amiga, it can be same editor on all platforms. I know it is heresy but does it support key mapping so I can use Ctrl-X/C/V consistently across platforms?

Regards
Doug

@Samurai_Crow

I just wish I could get it to build with Shared Libraries. But at moment only the clib2 was close enough to support GCC 11 and std libraries and I had to make a few changes to that.

Right now huge weakness in Amiga toolchains is dated C library support. Clib is ok but only static libraries and has hacks to work around missing bits and bobs.

For AmigaOS4 updated NewLib would be ideal. Its closed source unfortunately and I have no idea if we will ever see a new version publicly available.

Part of what makes Amiga fun is also its greatest weakness its does not have strong POSIX compatibility.

Regards
Doug

@NinjaCyborg

I am not that familiar with Rust and I could not find to straight forward instructions on porting. My understanding the big dependency is the LLVM libraries which should be usable in current state(sans bugs with my code). The next big part to my understanding is the STD library which seems to be the big deal.

Since I am not interested in Rust it would not be something I would do, but would assist anyone who took it on to ensure the LLVM is in good shape.

Regards
Doug

Steps to build LLVM
1. Build GCC 11 from adtools
2. Clone my repos for Clib2 and LLVM
3. Build Clib2
4. Build LLVM with bash script below to configure cmake changing variables to point to location appropriate for your cross compiler location.

I suggest reading how to build LLVM with CMAKE located here:
https://llvm.org/docs/CMake.html





Regards
Doug

@NinjaCyborg

I have the LLVM tools compiling and running it is the current development branch. This is not Clang. Right now it is the LLVM libraries which Clang is based upon. The development fork is available on my github.

https://github.com/DStastny/llvm-project

It does require my fork of Clib2 to build that address some issues with data definitions and the latest GCC 11.

I will be creating a separate repo with the configuration parameters for CMAKE required to build as well as some instructions but my I have been bit busy as of late.

Regards
Doug

@alfkil & @Raziel,

I just want to chime in on this about dynamic linking. I am with Raziel with this. For the size of executables we are now looking at static linking is almost to point of unusable with C++. Right now only viable option for C++ on AmigaOS is Clib2 statically linked.

For LLVM a Debug build is almost a 1.5 Gig and the Amiga Elf loader struggles runs executable two three times and memory is hosed.

Striped you are looking at minimum of 30+meg executable. The libStdc++ for Clib unstripped is almost 26megs. I would love to try to get Clang building but until a newer version of newlib becomes available that supports C++ 14 and the std namespace. I am not sure how much further I can go. And for LLVM there is no way to compile native. I had to reconfigure my Hyper-V to give at least 16 gigs of ram to my Linux instance to get LLVM cross to build.

Anyway just sharing some thoughts on dynamic vs static linking. Teach me to not just stick with C!

Regards
Doug

@alfkil

That is awesome. I wont lie I spent many days working on LLVM build as it was my first time working with CMAKE. It can be finicky but it is super powerful and I like it better than the old config scripts. I was able to build LLVM without having to work on anything more than code issues not flaying about with the build system.

Look forward to playing with QT6

Regards
Doug

@alfkil

Quote:

You should not need Ninja it should build a regular Unix makefile too.

I think its -G Unix

Now Ninja will definitely make it build faster...

But I would try to remove the option and get working first.

Regards
Doug

@Afkil,

I have successfully cross compiled my working branch of LLVM with CMAKE.

Change this
SET(CMAKE_SYSTEM_NAME AmigaOS)

to this
SET(CMAKE_SYSTEM_NAME Generic)

I handled the flags this way.

SET(CMAKE_CXX_FLAGS_INIT, "-mcrt=clib2 -athread=native")
SET(CMAKE_C_FLAGS_INIT, "-mcrt=clib2")

I did not require setting as they all got picked up or set by CMAKE interrogating ppc-amigaos-gcc

SET(CMAKE_MAKE_PROGRAM make)
SET(CMAKE_ASM_COMPILER ppc-amigaos-as)

Originally I started with a toolchain file but was able to get it all working with just defines on configuration of the variables.

For C++ I am using the latest build due to need of fixes for std library. Your mileage may vary depending on what you are trying to build.

Here is invocation of CMAKE for LLVM

Quote:


Regards
Doug

@sTix

I built cross under Ubuntu 20.10 with gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.10).


According to this:https://gcc.gnu.org/gcc-11/changes.html

Dwarf5 is the default for gcc-11. But doubt binutils for amiga is even close to current. So this would explain it.


As for LLVM, been trying to get this built for while but too many issues with std:: namespace.

But for first time I got it to point of linking the first parts and missing symbols are intentional as I need to provide Amiga specific implementations.

Regard and thanks again for efforts.

Doug

@sTix



I ran into this issue it appears the cross compiler is generating version dwarf 5 but ld .... Not sure if this is config during build. For now easy work around set the build flags -gdwarf-4.

Lots of symbols for me to resolve

Regards
Doug

@geennaam

Sorry to hear this but get it. I do however really appreciate your contribution of this driver and hope a respite finds you well.

Regards
Doug

@sTix

Thank you sir! I cloned the main repo. Built and moving forward. Prior to this was pointless to try to port the codebase I am attempting. Moving further along. Now to replace the platform code and create Amiga specific implementations.

Really appreciate work on clib2.

Regards
Doug

@sTix

Thanks I will clone from your repo.

Doug

GCC cross compiler.

Checking in on best approach to getting a cross compiler up that supports std:max_align_t. Does sba or sodero for k currently support and do I need to build a more up to date cLib as I know newlib does not support this.

Any help pointing me at pieces would be appreciated.

Regards
Doug