From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 11 11:09:56 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8405037B401; Wed, 11 Jun 2003 11:09:56 -0700 (PDT) Received: from mail.tcoip.com.br (erato.tco.net.br [200.220.254.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDBF743FBD; Wed, 11 Jun 2003 11:09:53 -0700 (PDT) (envelope-from dcs@tcoip.com.br) Received: from tcoip.com.br ([10.0.2.6]) by mail.tcoip.com.br (8.11.6/8.11.6) with ESMTP id h5BI9ql02913; Wed, 11 Jun 2003 15:09:52 -0300 Message-ID: <3EE77070.7000604@tcoip.com.br> Date: Wed, 11 Jun 2003 15:09:52 -0300 From: "Daniel C. Sobral" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4b) Gecko/20030606 X-Accept-Language: en-us, en, pt-br, ja MIME-Version: 1.0 To: Ruslan Ermilov References: <3EE76761.1030103@tcoip.com.br> <20030611180122.GC14100@sunbay.com> In-Reply-To: <20030611180122.GC14100@sunbay.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Tony Finch cc: hackers Subject: Re: build-tools and sed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 18:09:56 -0000 Thanks for the clarificaton. Ruslan Ermilov wrote: > On Wed, Jun 11, 2003 at 02:31:13PM -0300, Daniel C. Sobral wrote: > >>Shouldn't sed be part of the build tools? >> > > No. build-tools are a different beastie; they are the tools > that are only built during buildworld to "build" something > else. sed(1) isn't such a tool. Yes, it can be put under > the bootstrap-tools if there's some backward incompatibility > it in, but there's just no reason to do it right now. Please > see below for a further explanation. > > >>It's used in src//gnu/usr.bin/binutils/libbfd/Makefile, at the very least: >> >>targmatch.h: targmatch.sed config.bfd >> sed -f ${.ALLSRC:M*.sed} ${.ALLSRC:M*.bfd} > ${.TARGET} >> >>config.h: config.h.fbsd >>.if ${TARGET_ARCH} == "i386" >> sed -e 's,!!TRAD_HEADER!!,"hosts/i386bsd.h",g' ${.ALLSRC} > >>${.TARGET} >>.else >> sed -e 's,!!TRAD_HEADER!!,,g' ${.ALLSRC} > ${.TARGET} >>.endif >> >> >>Which was rather annoying when I got caught in the sed bug. Updating >>sources did not fix the problem, because it kept using the install sed... >> > > I asked for an UPDATING entry when I saw this bug for the first > time, and got a positive reply saying this was a good idea, but > this never actually happened, and this is now the third report I > have heard. > > In short: if your build environment is broken, the chances are > low you will be able to build your world. E.g., if you do not > have /usr/include you cannot win. Similarly, when your gcc(1) > is broken (for example), you won't be able to build world too. > We depend on a good shape of the build environment, and if it > breaks, we put this sort of info into UPDATING. > > When we create a backward incompatibility, this is completely > another case, and we put stuff either in bootstrap-tools or > cross-tools, depending on their nature. (cross-tools are similar > to bootstrap-tools except for also directly depending on the > value of TARGET_ARCH/TARGET.) > > > Cheers, -- Daniel C. Sobral (8-DCS) Gerencia de Operacoes Divisao de Comunicacao de Dados Coordenacao de Seguranca VIVO Centro Oeste Norte Fones: 55-61-313-7654/Cel: 55-61-9618-0904 E-mail: Daniel.Capo@tco.net.br Daniel.Sobral@tcoip.com.br dcs@tcoip.com.br Outros: dcs@newsguy.com dcs@freebsd.org capo@notorious.bsdconspiracy.net Life is a whim of several billion cells to be you for a while.