Updated Gnu compiler?

Hello,


i'm working on a little project with mingw.

I would like to port this little project on Amiga.
The problem is that in the code i use c++ 11 feature such: future, chrono and so on...

WHat about threads programming with the actual gnu compiler?

There's a GCC 4.9 port maintained here:
https://github.com/sba1/adtools

There are ready to use Debian packages, I tried them on Ubuntu. Not sure about the native compiler, I couldn't build it under cygwin the last time I checked.

When I built version 4.9, the version in trunk didn't build right away. Instead you have to check out the tagged version 4.9, and also change some makefiles.

I used salas00 guide: http://www.os4coding.net/blog/salass0 ... -compiler-adtools-project and also made minor changes to the version used in the makefiles. Think I only had to change in two places; where it CD'ed to "trunk", I changed to "4.9.x", or something like that.

This is however the cross-compiler. But I guess that could be used in order to compile a PPC version, on the cross-compile system.

@jaokim

So we don't have any native AmigaOS version of the GCC 4.9?

@AmigaBlitter

No you most compile it your self.

maybe in the next sdk update who knows...

GCC 5.3.0 is now available on Aminet:

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

@salass00

Wow, this is good news. Thanks everybody involved.

@salass00

Thank you to all involved.

It's native or cross?

@salass00

What about to release the Cairo-Amiga surface skeleton file too?

Thank you very much.

@AmigaBlitter

Quote:

That would be mostly Sebastian Bauer AFAIK.

Quote:

Native.

A cross-compiler if needed can be compiled from:

https://github.com/sba1/adtools

@salass00

Just for notes...anyone who uses that adtools setup will preferably be running it on Ubuntu "Wily Werewolf" and I recommend the LTS branch for making GCC 4.9

Hope this helps...

now we just need a cross compiler users guide

@salass00

Quote:

Could somebody sum up for a noob the main advantages of GCC 5.3.0 over the latest found in the SDK (AFAIK 4.2.4).

@lazi

Can possible create faster programs.

@lazi
It supports the latest C++11 and C++14 standards.

@lazi

Better code generation as LiveForIt said and more useful warnings.

Newer gcc versions can analyse code to tell if for instance a variable can actually be used uninitialised or not whereas gcc 4.2.4 often gives false positives.

To give an example a code like this produces a warning in gcc 4.2.4 but not in gcc 4.9.2:


Because do_something() is only called if x is 0 (which is also the condition for setting y) the variable y is in fact never used uninitialised but gcc 4.2.4 does not see this.

The example may seem a little artificial but I run into this kind of situation often enough for it to be annoying when switching between gcc 4.9.2 (cross-compiler) and 4.2.4 (native).

@salass00

Can anyone help me finding out what's going wrong?

Installed 5.3.0
Fixed the missing newlib folder in GCC:lib/gcc/ppc-amigaos/5.3.0/ by clonign the lib dir in the same directory

But whatever i do i always get a "GCC compiler...not found!" from ./configure.

I also get it now when i use the 4.2.4 gcc install (of course, adapted the path and assign and rebooted)

HELP!

edit:
I get this when trying to build/compile:
ld: cannot find -lgcc
ld: cannot find -lgcc_eh

How to cure that?

FIXED:
The "fix" has to be

1) create a newlib subdir in GCC:lib/gcc/ppc-amigaos/5.3.0/
2) copy GCC:lib/gcc/ppc-amigaos/5.3.0/lib to GCC:lib/gcc/ppc-amigaos/5.3.0/newlib

Here GCC:lib/gcc/ppc-amigaos/5.3.0/newlib didn't work, so the library files are now in GCC:lib/gcc/ppc-amigaos/5.3.0/newlib/lib . Snoopy will tell you where else ld looks for them if you think that's way too long.

@Thematic

Thanks i "fixed" it in the meantime.

Problem was that i was building with -dynld.
It didn't find the correct versions of the libs afterwards.

Went back to using static builds completely as it opposes my understanding of using "shared" libs, when most of the programs have to provide a specific sobjs/ dir with said (updated/special built) shared objects, to make it run for everyone anyway.

I get the same error:

ld: cannot find -lgcc
ld: cannot find -lgcc_eh

it points to another directory