Cross compilation first steps

Hello,

I had setup the SDK for cross compiling in my Debian machine (following Joachim Birging's and Nicolas Mendoza's guides) and want to give it a try, but need some help. Practically I'm starting from zero.

So, after getting the source code I'm interested, first thing would be to see what dependencies it has, right? The best way for that would be looking in the makefile or cmakelists if there aren't available in other place?

If those dependencies are available for AmigaOS4.x, where should I put them?

I think that is enough for a start Thanks for any help.

@emeck

Much like with native SDK: under sdk/local
For example /usr/local/amiga/ppc-amigaos/sdk/local/newlib/lib/libtiff.a

So for much the same reason you put your own additions to debian but also to the SDK, into a dir named local.

Did your hello world work?

@Thematic

Quote:
Thanks, got that.

Quote:
Yes, I think. An executable was created and no warnings nor errors showed in the console. Don't have a working AOS4.x machine now , so I'll also need to find a willing betatester.

@emeck

Ok, next issue.

The C "Hello World" test program compiled without errors and worked in an AOS4.x machine (thanks for testing Thematic). But the C++ "Hello World" test throws many undefined references, like:
/home/zerohero/svn/gcc-build/ppc-amigaos/libstdc++-v3/libsupc++/../../../../adtools-gcc-4.4.2/libstdc++-v3/libsupc++/vterminate.cc:80: undefined reference to `_Unwind_SjLj_Resume'

I have libsupc++ and libstdc++ in /usr/local/amiga/lib/gcc/ppc-amigaos/4.4.3/newlib/lib/ and /usr/local/amiga/lib/gcc/ppc-amigaos/4.4.3/clib2/lib/ in my SDK tree.

How can I fix that problem? Did I missed something?

@emeck

4.4.3 is broken, use 4.2.4 instead.

@diegocr

Quote:

Tried that, but still the same. I'll do it again from scratch; maybe I missed a step.

@emeck

you have to link the exe with -lgcc_eh with 4.4.4

@afxgroup

This works for statically linkage, as suggested by Trev at UtilityBase:

ppc-amigaos-g++ -o hello++ hello++.cpp -lstdc++ -lgcc_eh

But for dinamic linkage I now get

/usr/local/amiga/lib/gcc/ppc-amigaos/4.2.4/../../../../ppc-amigaos/bin/ld: hellocpp: hidden symbol `__gtdf2' in /usr/local/amiga/lib/gcc/ppc-amigaos/4.2.4/libgcc.a(_gt_df.o) is referenced by DSO
/usr/local/amiga/lib/gcc/ppc-amigaos/4.2.4/../../../../ppc-amigaos/bin/ld: final link failed: Nonrepresentable section on output
collect2: ld returned 1 exit status

using

ppc-amigaos-g++ -use-dynld -o hellocpp hello.cpp

or

ppc-amigaos-g++ -use-dynld -o hellocpp hello.cpp -lstdc++ -lgcc

@emeck

Did you compile the cross compilers yourself or did you take precompiled binaries? There were some changes in the mean time, so it would be important to know whether you are using the most recent version of gcc of the 4.2.4 and 4.4.4 branch. Any gcc 4.4.3 is definitively obsolete.

The gcc 4.4.4 branch can be found in the branches directory of the adtools project (http://www.sf.net/projects/adtools). The gcc 4.2.4 branch is trunk at the moment. There is also a file with instructions how to compile a cross compiler (improvements to this file are very welcome). Questions regarding the process should be directed to the adtools mailing list.

After you compiled the cross compiler yourself and the problem persists, please supply a full basic example with Makefile that demonstrates the problem and post it as a bug in the adtools tracker. Thanks!

@sba

Quote:
No, I downloaded Joachim Birging's x86_64 version.

Quote:
Thanks, I'll give it a try then.

@emeck

with 4.2.4 (and reading your post, it seems so) you should not use -lgcc_eh.
I think you have mixed 4.4.4 and 4.2.4 library.. try to restart from scratch using only 4.2.4 (or 4.4.4) and avid to mix compiler stuff.
I've compiled both 4.2.4 and 4.4.4 from adtools projects and they works very well on MacOSX x86

Yesterday i've compiled the adtools trunk to get V2 sobjs sup, and hundred of compiler warnings apart (on the first steps only, regarding some gcc macro iirc), the only issue i've noticed is that the libs libstdc++ libsupc++ libssp etc are now placed into a different directory than on the zh cross-compiler.

Trunk: /usr/local/amiga/ppc-amigaos/lib

ZH: /usr/local/amiga/lib/gcc/ppc-amigaos/4.2.4/newlib/lib

However, the new compiler still seems to look for the libs at the zh path, so i just created symlinks.

I've compiled a .so before noticing that and it was linked without using libgcc.so (and reporting no errors), then tried to compile a C++ program (statically linked) and noticed the mixed libs due i get the same undefined references to sjlj functions...

but still using the right libs, i was forced to specify -lgcc_eh (thx afxgroup ;), otherwise it does not link. It's really like that for the last trunk or i might have something wrong somewhere?

Anyhow, despite those little "issues", I really recommend everybody to build his own cross-compiler, it's really easy, well...it compiles OOTB! (great job adtools guys)

@afxgroup
Quote:
I know this was a looong time ago, but many thanks for this tip. Not sure I would have been able to solve my problem without this obscure solution.