From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32397 invoked by alias); 25 Jul 2002 12:43:02 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 32384 invoked from network); 25 Jul 2002 12:43:00 -0000 Received: from unknown (HELO ns2.uk.superh.com) (193.128.105.170) by sources.redhat.com with SMTP; 25 Jul 2002 12:43:00 -0000 Received: from sh-uk-ex01.uk.w2k.superh.com (sh-uk-ex01 [192.168.16.17]) by ns2.uk.superh.com (8.11.6+Sun/8.11.6) with ESMTP id g6PCZ5K00694; Thu, 25 Jul 2002 13:35:06 +0100 (BST) Received: from superh.com ([192.168.17.40]) by sh-uk-ex01.uk.w2k.superh.com with Microsoft SMTPSVC(5.0.2195.4905); Thu, 25 Jul 2002 13:41:23 +0100 Message-ID: <3D3FF1EC.39BA039A@superh.com> Date: Thu, 25 Jul 2002 11:01:00 -0000 From: Joern Rennecke Organization: SuperH UK Ltd. X-Accept-Language: en MIME-Version: 1.0 To: Momchil Velikov CC: gcc@gcc.gnu.org, dje@transmeta.com, Zack Weinberg Subject: Re: Unreviewed patch / {PATCH] Do not override configure decision about inhibit_libc References: <87n0sgqlqu.fsf@fadata.bg> <3D3FCD3F.CEE12605@superh.com> <87d6tchyes.fsf@fadata.bg> <3D3FDC0F.77C915D0@superh.com> <87y9c0giej.fsf@fadata.bg> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Jul 2002 12:41:23.0548 (UTC) FILETIME=[959779C0:01C233D8] X-SW-Source: 2002-07/txt/msg01212.txt.bz2 Momchil Velikov wrote: > > >>>>> "Joern" == Joern Rennecke writes: > > Joern> Momchil Velikov wrote: > >> > >> >>>>> "Joern" == Joern Rennecke writes: > Joern> How do you build a usable sh-elf compiler without newlib > Joern> in the first place? > >> > >> Huh ? The compiler by itself does not require newlib nor does the > >> produced code, right ? > > Joern> It you need header files for the compiler if you compile code > Joern> that include any of them. And you need the c library if any > Joern> function of it is used. > > I can think of at least three legitimate cases: > > I. Use the compiler in a freestanding environment - no libraies or > headers exist at all. Is there a demand for this configuration? In that case, we should have something more fine-grained that inhibit_libc, which suppresses the profiling support along with eprintf. > II. Build and install the libraries after building the compiler - way > more convenient than installing headers only, building the compiler, > going back and building the libraries. It's also more convenient that writing all the binaries by hand. But still moe convenient is just to use a unified source tree and build everything in one go. > > III. In a cross compilation environment, the headers may not be on the > same machine. Why would you want to build the libraries on a different machine than the compiler? -- -------------------------- SuperH 2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ T:+44 1454 462330