From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6427 invoked by alias); 19 Dec 2007 23:52:00 -0000 Received: (qmail 6418 invoked by uid 22791); 19 Dec 2007 23:52:00 -0000 X-Spam-Check-By: sourceware.org Received: from out4.smtp.messagingengine.com (HELO out4.smtp.messagingengine.com) (66.111.4.28) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 19 Dec 2007 23:51:54 +0000 Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id E3FF04BA45 for ; Wed, 19 Dec 2007 18:51:51 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Wed, 19 Dec 2007 18:51:51 -0500 Received: from [192.168.0.153] (TOROON12-1177741232.sdsl.bell.ca [70.50.231.176]) by mail.messagingengine.com (Postfix) with ESMTP id 9BB0720865 for ; Wed, 19 Dec 2007 18:51:51 -0500 (EST) Message-ID: <4769AE95.5000104@fastmail.fm> Date: Thu, 20 Dec 2007 08:03:00 -0000 From: tmm User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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] Using a different Standard C library. X-SW-Source: 2007-12/txt/msg00125.txt.bz2 Some of the eCos packages that I'm using require the Standard C library so I've included the CYGPKG_ISOINFRA (ISO C & POSIX Infrastructure) package and several of the CPYPKG_LIBC_* packages. But, I would rather use a different C library: the one that comes with my Code Sorcery ARM compiler. Though this is not the normal eCos way, I assume that it is not too unusual. But how is this typically done? I will probably continue to make my eCos library using the eCos C library headers. But I would hack the makefiles so that the source code for the C library packages doesn't get included in the my projects' library. In place of the eCos C library code I would link in my own C library when I link my applications. (When I write 'my own' C library I mean the compiler's.) The tricky part of this is the 'ISO C & POSIX Infrastructure' package. This contains a mix of code that I do need (the POSIX stuff) and code that will be provided by my C library. Perhaps instead I should take the code of my C library and replace the eCos C library code with it (and make corresponding changes to the package definitions)? Thanks for any suggestions, Tom. -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss