From mint-bounce@lists.fishpool.fi Sat Dec 19 05:28:09 2009 Message-ID: <4B2CAA08.9030902@freesbee.fr> Date: Sat, 19 Dec 2009 11:25:12 +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.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: mint mailing list Subject: [MiNT] mshort support Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 091218-1, 18/12/2009), 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 nBJAS9Ar030478 Hello. I'm currently compiling FreeMiNT and all its modules (including XaAES) for the first time (and I'm really frightened by the number of warnings). It seems that the kernel and all its modules are compiled with -mshort, am I right ? In this case, all the libraries used by FreeMiNT and its modules must be provided with -mshort, for all supported CPUs. This includes at least libgcc and libgem. Severe problems can appear when mixing libraries compiled with different short/CPU options. If the above is right, I will include all the required mshort libraries in my future cross-compiler distributions. -- Vincent Rivière