Hello, Keith !I'm currently working on the Quake bug. It is very hard to find, maybe a bug in the Quake sources, or in GCC.
After that, I will have a look at the C++ problem.
Here are the configure params I used for the Canadian Cross:$ CC=/usr/local/m68k-atari-mint/bin/m68k-atari-mint-gcc AR=/usr/local/m68k-atari-mint/bin/m68k-atari-mint-ar RANLIB=/usr/local/m68k-atari-mint/bin/m68k-atari-mint-ranlib../gcc-4.2.2/configure --target=m68k-atari-mint --host=m68k-atari-mint--enable-languages="c,c++" --disable-nls --disable-libstdcxx-pch --program-suffix=-4.2.2 --disable-bootstrap --build=i686-pc-cygwin
So you are building GCC for MiNT on Cygwin. I think in that case, it is a classic cross-build of GCC. If I understood well, a Canadian Build is when all the triplets build/host/target are different. But it is not the problem !
If you build a C++ program using the Cross GCC on Cygwin, it produces a valid MiNT executable, right ? But if you try to compile the same program with your "native" MiNT GCC built on Cygwin, it links, but it causes SIGILL when run. Did I understand ?
If it is the case, you can send me the binary causing SIGILL. Please compile it for 68000 (the default) and link it with --traditional format. Something like this:
g++ hello.cpp -o hello.tos -Wl,--traditional-formatI will look at it with Steem and MonST2 as usual, I may find something wrong in it...
Keep going ! -- Vincent Rivière