Date: Mon, 05 May 2003 23:33:04 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: arch@freebsd.org Subject: Re: cvs commit: src/sbin Makefile src/sbin/bsdlabel Makefile Message-ID: <46563.1052170384@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 05 May 2003 14:28:08 PDT." <200305052128.h45LS8Zk011878@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
With reference to the commit below, we need to decide our strategy with such disk maintenance tools. Do we compile&install only what is used for the current platform ? Do we compile&install all tools on all platforms ? I don't particularly care one way or the other. The intent is that the tools work on all platforms, but since we don't cross-build boot-code, there is some natural limits to their usefulness. For make [cross-]release, we can build the necessary tools as release tools, so that does not necesarily factor in this discussion. Poul-Henning In message <200305052128.h45LS8Zk011878@repoman.freebsd.org>, Poul-Henning Kamp writes: >phk 2003/05/05 14:28:08 PDT > > FreeBSD src repository > > Modified files: > sbin Makefile > sbin/bsdlabel Makefile > Log: > Compile bsdlabel on all platforms. > > Install a link to the disklabel(8) name on i386 and alpha platforms. > > Leave old disklabel(8) sources intact but disconnected from the build > for now. > > Revision Changes Path > 1.120 +1 -6 src/sbin/Makefile > 1.15 +10 -0 src/sbin/bsdlabel/Makefile > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46563.1052170384>