From mint-bounce@lists.fishpool.fi Tue Jan 22 17:35:29 2008 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Date: Mon, 21 Jan 2008 11:55:42 -0500 (EST) From: Keith Scroggins To: mint Subject: Re: [MiNT] GCC 4.2.2 - Keith's Latest Progress (or lack thereof) In-Reply-To: <4793D6BA.9030806@freesbee.fr> Message-ID: References: <478A8F44.3030702@freesbee.fr> <47936072.4050702@freesbee.fr> <4793D6BA.9030806@freesbee.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: kws@radix.net Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=BAYES_00 X-Spam-Level: Status: X-Status: X-Keywords: Hello Vincent, > 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 ! I have done both, build it natively (still have the binaries) and also build it in Cygwin (My understanding is its a Canadian Cross because the resulting binaries are not for the build system, those are the guidelines I followed.) > 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 ? Yes, I can build a working executable (at list Valid in AranyM) with the C++ Cross Compiler. I was using the ScummVM tools to test this since there are 23 different utils, in either C or C++. The same source with the compilers running natively, the C tools build working executables, but the C++ tools that are built just crash with SIGILL. So I have tested both C++ bootstrapped (with GCC 2.95.3) and built natively (and then rebuilt with the bootstapped 4.2.2 natively), and also the compiler built using the Cross Compiler to build it. > 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-format I will try to do this a little later today, maybe send you both a working one and a broken one. Thanks! Keith