From mint-bounce@lists.fishpool.fi Thu Jan 28 15:45:37 2010 Message-ID: <4B61F646.6050100@freesbee.fr> Date: Thu, 28 Jan 2010 21:40:38 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] __Unwind_Resume References: <4B6147EA.4060400@freesbee.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100128-0, 28/01/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o0SKjaus026514 Miro Kropacek wrote: > Be sure you don't use old C++ libraries if you compile your programs > with GCC 4.x. > > Everything is compiled from scratch No. Because... The "clean" target in zView's Makefile is incomplete. It doesn't remove pdf/*.o. As a result, pdf/pdflib.o is distributed in the source archive by error ! Then this file is not rebuilt when you type make. Finally, I'm right: you are mixing new object files with old ones :P The obvious solution is to fix the makefile to remove these .o files and compile them again. This brings us to a new question. GCC can be configured to use 2 different and incompatible exception models: - SJLJ (Setjump/Longjump) - DW2 (DWARF 2) I didn't know which method to use when configuring GCC for the first time, so I chose SJLJ. Also I thought that DW2 was available on ELF only (like DWARF debug info), but I was probably wrong. Source objects using SJLJ are tagged with __gxx_personality_sj0. The ones using DW2 use __gxx_personality_v0. So it seems that Zorro has configured his cross-compiler with DW2 exceptions, and it works fine for him. The question is: which exception model is good for us ? The answer is probably "the same as GCC 2.x", as usual. I don't know which choice had been made for it. -- Vincent Rivière