From mint-bounce@lists.fishpool.fi Mon Feb 11 18:45:14 2008 Date: Mon, 11 Feb 2008 18:42:07 -0500 (EST) From: Keith Scroggins To: mint Subject: Re: [MiNT] Binutils 2.18 + GCC 4.2.3 In-Reply-To: Message-ID: References: <47ADDBA8.3050603@freesbee.fr> <47ADE386.8030501@freesbee.fr> <47AF2849.7000404@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: Hello Miro, >> at this point. Here are tests using latest make (which I believe show >> make is not at fault): >> > Actually, I maybe, just maybe, discovered the source of problem. Shame on > me, it's my patch -- look in the startup code of mintlib, I changed our > premilitary stack to 1 KB, to be sure we know what's going on in case of > some problems (ehm, it does work really well ;-). When I changed this stack > to 64 KB, libgcc gets compiled/linked. I didn't do further investigation > since gcc/binutils (btw I really recommend to do this "merged" chain, i.e. > binutils inside gcc) compilation finished just this morning. At the point the corruption occurs, it is just past 1532 bytes on the command line (ripping out the g++), so, just under 1.5k. I don't know if this is helpful info at all. Keith