GCC 6.2 toolchain for AmigaOS 3

[bebbo]

Originally Posted by bebbo

What's the output with '-v'? When I'm using '-nostdlib' then there is no lib in the parameters for 'collect'.

It's the file a500.ld. This is a linker command file and contains the directives what to link:

GROUP(-lc -lgcc)

[wawa]

Originally Posted by ross

Yes, this is what I meant

if you have enbough programming expertise, you could even be the person to do that. unfortunatelly i dont think i do, but im starting to think about pinging toni again, about what would make sense in this respect given bebbos work.

thing is, probably aros would have to switch to gcc6 for good first, because earlier versions might stop working if another way of dealing with amiga baskend features was introduced.

[ross]

Originally Posted by wawa

if you have enbough programming expertise

I think it's not just a matter of programming expertise (which is important!) but also knowledge of compilers stuff (which I largely miss).
I like more low level programming and this is not properly my taste. But can be interesting..
[I would rather rewrite AROS exec/kernel.resource/mmu.library in 68k asm ]

im starting to think about pinging toni again, about what would make sense in this respect given bebbos work

I hope Toni has followed Bebbo's progress.

thing is, probably aros would have to switch to gcc6 for good first, because earlier versions might stop working if another way of dealing with amiga baskend features was introduced.

I agree.

Cheers!
ross

[ovale]

This is what I get with -v and -mcrt=clib2 :

m68k-amigaos-gcc -v -mcrt=clib2 exception_68000.o standalone.o hex.o pkt.o cmd.o stub_arch.o a500_init.o uart.o -T a500.ld -o main -Wl,-Map=main.map
Using built-in specs.
COLLECT_GCC=m68k-amigaos-gcc
COLLECT_LTO_WRAPPER=/opt/m68k-amigaos/libexec/gcc/m68k-amigaos/6.3.1b/lto-wrapper
Target: m68k-amigaos
Configured with: /root/amigaos-cross-toolchain/submodules/gcc-6/configure --prefix=/opt/m68k-amigaos --infodir=/opt/m68k-amigaos/m68k-amigaos/info --mandir=/opt/m68k-amigaos/share/man --prefix=/opt/m68k-amigaos --prefix=/opt/m68k-amigaos --target=m68k-amigaos --enable-languages=c,c++,objc --enable-version-specific-runtime-libs --disable-libssp --with-headers=/root/amigaos-cross-toolchain/.build-m68k/sources/ixemul-48.2/include
Thread model: single
gcc version 6.3.1b 20170320 (GCC)
COMPILER_PATH=/opt/m68k-amigaos/libexec/gcc/m68k-amigaos/6.3.1b/:/opt/m68k-amigaos/libexec/gcc/m68k-amigaos/6.3.1b/:/opt/m68k-amigaos/libexec/gcc/m68k-amigaos/:/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b/:/opt/m68k-amigaos/lib/gcc/m68k-amigaos/:/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b/../../../../m68k-amigaos/bin/
LIBRARY_PATH=/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b/:/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b/../../../../m68k-amigaos/lib/
COLLECT_GCC_OPTIONS='-v' '-mcrt=clib2' '-T' 'a500.ld' '-o' 'main' '-mcpu=68000'
/opt/m68k-amigaos/libexec/gcc/m68k-amigaos/6.3.1b/collect2 -L/opt/m68k-amigaos/m68k-amigaos/clib2/lib -o main /opt/m68k-amigaos/m68k-amigaos/clib2/lib/ncrt0.o -L/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b -L/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b/../../../../m68k-amigaos/lib exception_68000.o standalone.o hex.o pkt.o cmd.o stub_arch.o a500_init.o uart.o -Map=main.map -lc -lamiga -ldebug -lgcc -lc -T a500.ld
/opt/m68k-amigaos/lib/gcc/m68k-amigaos/6.3.1b/../../../../m68k-amigaos/bin/ld: final link failed: Invalid operation
collect2: error: ld returned 1 exit status
Makefile:31: recipe for target 'main' failed
make: *** [main] Error 1

[bebbo]

Originally Posted by bebbo

It's the file a500.ld. This is a linker command file and contains the directives what to link:

GROUP(-lc -lgcc)

I compiled and linked "something". It's untested and required

• some underscores for vasm <--> gcc-6
• some linker hacking for -mpcrel linking
• a strcpy function

maybe it's working... /duck

AGAIN: updated the zip file

asm source is looking ok now - but still no time to test this...

[wawa]

Originally Posted by ross

I think it's not just a matter of programming expertise (which is important!) but also knowledge of compilers stuff (which I largely miss).

unfortunatelly hardly anyone wants to take the responsibility to mess with it.

I like more low level programming and this is not properly my taste. But can be interesting..

seems a bit of tonis profile, maybe you could help witha an issue that is bothering s all. aros has problems to boot up on a number of amiga ide pio controllers, including vampire/apollo stuff, we are a bit stuck in this area. imho, having it boot on "genuine" hardwre might enforce progress in areas an end user is interested in.

[I would rather rewrite AROS exec/kernel.resource/mmu.library in 68k asm ]

well, you might be allowed to do that for arch/amiga-m68k if it gains anything significant, that is, but part of architecure related code is asmalready.

I hope Toni has followed Bebbo's progress.

i think he has noticed it, but given the crowd bothering him in all kinds of areas im thankful for every peace of commitment..

[Marlon_]

One thing I've noticed with the toolchain is that it doesn't like to link stuff when using singletons. I've managed to compile MilkyTracker 0.9.86 with the toolchain, but as soon as it is trying to link ppui, it fails:

DialogResample.o(.text+0x92c): In function `_ZN14DialogResampleC4EP8PPScreenP15DialogResponderi':
/home/marlon/tmp/MilkyTracker/milkytracker-0.90.86/src/tracker/../../src/ppui/Singleton.h:44: undefined reference to `PPSingleton<PPUIConfig>::instance'
DialogResample.o(.text+0x910):/home/marlon/tmp/MilkyTracker/milkytracker-0.90.86/src/tracker/../../src/ppui/Singleton.h:43: undefined reference to `PPSingleton<PPUIConfig>::instance'
DialogResample.o(.text+0x932): In function `_ZN14DialogResampleC4EP8PPScreenP15DialogResponderi':
/home/marlon/tmp/MilkyTracker/milkytracker-0.90.86/src/tracker/../../src/ppui/PPUIConfig.h:65: undefined reference to `PPSingleton<PPUIConfig>::instance'
EnvelopeEditor.o(.text+0x18): In function `PPSingleton<EnvelopeEditor::ClipBoard>::getInstance()':
/home/marlon/tmp/MilkyTracker/milkytracker-0.90.86/src/tracker/../../src/ppui/Singleton.h:44: undefined reference to `PPSingleton<EnvelopeEditor::ClipBoard>::instance'
EnvelopeEditor.o(.text+0x2):/home/marlon/tmp/MilkyTracker/milkytracker-0.90.86/src/tracker/../../src/ppui/Singleton.h:43: undefined reference to `PPSingleton<EnvelopeEditor::ClipBoard>::instance'
EnvelopeEditor.o(.text+0x20):/home/marlon/tmp/MilkyTracker/milkytracker-0.90.86/src/tracker/../../src/ppui/Singleton.h:47: undefined reference to `PPSingleton<EnvelopeEditor::ClipBoard>::instance'

And it goes on like this for every function that references the PPSingleton template.

I'm not sure how that could be fixed. My solution right now is to reprogram the software not to use the PPSingleton template.

[bebbo]

Originally Posted by Marlon_

One thing I've noticed with the toolchain is that it doesn't like to link stuff when using singletons. I've managed to compile MilkyTracker 0.9.86 with the toolchain, but as soon as it is trying to link ppui, it fails:
...

How?

Would look into it, if I could get that far.

[Marlon_]

Originally Posted by bebbo

How?

Would look into it, if I could get that far.

To get it to configure properly I did this:

SDL_CONFIG=/opt/m68k-amigaos/bin/sdl-config CPPFLAGS="-g -Os -D__AMIGA__ -fpermissive -mcrt=clib2 -m68020 -I/opt/m68k-amigaos/include/SDL -I/opt/m68k-amigaos/include -L/opt/m68k-amigaos/lib -L/opt/m68k-amigaos/m68k-amigaos/lib -fomit-frame-pointer -lSDL -ldebug -ljpeg -lSDLstub -lSDL_image -Xlinker --allow-multiple-definition" CXXFLAGS="-g -Os -D__AMIGA__ -fpermissive -mcrt=clib2 -m68020 -I/opt/m68k-amigaos/include/SDL -I/opt/m68k-amigaos/include -L/opt/m68k-amigaos/lib -L/opt/m68k-amigaos/m68k-amigaos/lib -fomit-frame-pointer -lSDL -ldebug -ljpeg -lSDLstub -lSDL_image -Xlinker --allow-multiple-definition" CFLAGS="-g -Os -D__AMIGA__ -fpermissive -mcrt=clib2  -m68020 -I/opt/m68k-amigaos/include/SDL -I/opt/m68k-amigaos/include -L/opt/m68k-amigaos/lib -L/opt/m68k-amigaos/m68k-amigaos/lib -fomit-frame-pointer -lSDL -ldebug -ljpeg -lSDLstub -lSDL_image -Xlinker --allow-multiple-definition" ./configure --build x86_64 --host m68k-amigaos

Some of that might be redundant and unnecessary, but it gets it to compile.

After you've run that, all you need to do is "make". Eventually some code errors pops up, that requires minor edits which I can't remember at the moment. You'll notice! =)

[bebbo]

Originally Posted by Marlon_

To get it to configure properly I did this:

...

Some of that might be redundant and unnecessary, but it gets it to compile.

After you've run that, all you need to do is "make". Eventually some code errors pops up, that requires minor edits which I can't remember at the moment. You'll notice! =)

The archive I got only contains a configure.in and autoconf (2.69) is complaining...

Guess you compiled and installed a bunch other stuff?

[Marlon_]

Originally Posted by bebbo

The archive I got only contains a configure.in and autoconf (2.69) is complaining...

Guess you compiled and installed a bunch other stuff?

Oh, the archive I got had a proper configure and such, I didn't need to use autoconf, automake or autoreconf.
Let me dig it up for you!

[Marlon_]

Here you go:
http://www.marlonbeijer.com/download....90.86.tar.bz2

[bebbo]

Originally Posted by Marlon_

Here you go:
http://www.marlonbeijer.com/download....90.86.tar.bz2

downloading... let's see how far I get ^^

[Marlon_]

Originally Posted by bebbo

downloading... let's see how far I get ^^

Good luck!

[bebbo]

Originally Posted by Marlon_

Good luck!

... missing:

libSDL -> SDL2-2.0.5.tar.gz ?
libjpeg -> jpegsrc.v9b.tar.gz ?

[Samurai_Crow]

SDL 1.2 on Aminet, I would imagine... since SDL 2 doesn't have an Amiga version.

[Marlon_]

Originally Posted by bebbo

... missing:

libSDL -> SDL2-2.0.5.tar.gz ?
libjpeg -> jpegsrc.v9b.tar.gz ?

What? 0.90.86 is before they went over to SDL2 afaik. I haven't gotten that message yet and I've successfully linked with SDL-1.2.6.
SDL-1.2.6 and libjpeg is available on aminet.

[Marlon_]

I have managed to compile SDL-1.2.15 for AmigaOS3.x with your toolchain, however I'm not done testing it yet, so I don't know how stable it is.

[bebbo]

Workaround for the missing template class member is adding

PPUIConfig * PPUIConfig::instance = NULL;

to PPUIConfig.cpp.

EDIT: correct (no warning)

template<> 
PPUIConfig * PPSingleton<PPUIConfig>::instance = NULL;

This creates the missing

	.globl	__ZN11PPSingletonI10PPUIConfigE8instanceE

And do the same for all others (e.g. GlobalColorConfig, ...)

[Marlon_]

Originally Posted by bebbo

Workaround for the missing template class member is adding

PPUIConfig * PPUIConfig::instance = NULL;

to PPUIConfig.cpp.

EDIT: correct (no warning)

template<> 
PPUIConfig * PPSingleton<PPUIConfig>::instance = NULL;

This creates the missing

	.globl	__ZN11PPSingletonI10PPUIConfigE8instanceE

And do the same for all others (e.g. GlobalColorConfig, ...)

Alright, sorted most of them now. The only ones left are PPSingleton<EnvelopeEditor::ClipBoard> and PPSingleton<SampleEditor::ClipBoard>, but when I try to sort it, it complains about the instance being private. I'll probably figure it out soon enough. :P