From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31452 invoked by alias); 15 Sep 2007 18:39:42 -0000 Received: (qmail 31443 invoked by uid 22791); 15 Sep 2007 18:39:42 -0000 X-Spam-Check-By: sourceware.org Received: from snape.ecoscentric.com (HELO snape.ecoscentric.com) (212.13.207.199) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 15 Sep 2007 18:39:38 +0000 Received: from localhost (snape.ecoscentric.com [127.0.0.1]) by snape.ecoscentric.com (Postfix) with ESMTP id 13FE6DC8087; Sat, 15 Sep 2007 19:39:36 +0100 (BST) Received: from snape.ecoscentric.com ([127.0.0.1]) by localhost (snape.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OvItiamx9+sK; Sat, 15 Sep 2007 19:39:35 +0100 (BST) Received: from [127.0.0.1] (unknown [212.13.207.199]) by snape.ecoscentric.com (Postfix) with ESMTP id 9BAEADC806E; Sat, 15 Sep 2007 19:39:34 +0100 (BST) Message-ID: <46EC26E6.1090309@eCosCentric.com> Date: Sat, 15 Sep 2007 18:39:00 -0000 From: Jonathan Larmour User-Agent: Mozilla Thunderbird 1.0.8-1.1.fc3.4.legacy (X11/20060515) MIME-Version: 1.0 To: eCos@sunnorth.com.cn CC: ecos-discuss@ecos.sourceware.org, Andrew Lunn References: In-Reply-To: Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: A question about _impure_ptr X-SW-Source: 2007-09/txt/msg00101.txt.bz2 eCos@sunnorth.com.cn wrote: > Dear all: > I have another question about _impure_ptr. > In a gcc4.2 compiler from codesourcery, the cplusplus library libstdc++ > uses a void * _impure_ptr pointer which is implemented in newlib. Now as > far as eCos concerned, because eCos provides its own newlib(c library) and > _impure_ptr isn't implemented in its c library, linker will complain > "undefined _impure_ptr". > How to solve this problem? You can either rebuild the codesourcery tools using eCos, or just define your own: void *_impure_ptr; Be warned if you do the latter, theoretically it could cause problems, but I don't think it applies to C code. Even in C++ code, last time I looked, it was only used for displaying an assertion failure message before termination, so crashing at that point wouldn't be such a big deal - you just won't know why until you look closer. BTW, please do not CC ecos-discuss-owner. That is for mailing list issues only. Jifl -- eCosCentric Limited http://www.eCosCentric.com/ The eCos experts Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571 Registered in England and Wales: Reg No 4422071. ------["The best things in life aren't things."]------ Opinions==mine -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss