Date: Thu, 1 Apr 1999 07:28:38 -0600 (CST) From: Richard Wackerbarth <rkw@dataplex.net> To: Chuck Robey <chuckr@mat.net> Cc: Satoshi - the Wraith - Asami <asami@FreeBSD.ORG>, jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: /var/db/pkg/.mkversion Message-ID: <Pine.BSF.4.05.9904010703520.3443-100000@nomad.dataplex.net> In-Reply-To: <Pine.BSF.4.10.9904010753340.498-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 1 Apr 1999, Chuck Robey wrote: > On Thu, 1 Apr 1999, Richard Wackerbarth wrote: > > > The natural tag for the TARGET would be in > > /usr/src/include. However, I can see some problems with this for > > the ports tree. > > Richard, don't forget that having /usr/src isn't required to build > ports. I don't think that I did forget. I explicitly reference that situation. The real solution (re the TARGET) has to depend on something that the USER sets for a particular "run". As such, it should be an environment variable which defaults to the HOST value. At the same time, the ports have to consider the purpose for which they need the identification. For example, "fetch -A" is a HOST/TOOLSET situation. But selecting the set of sysctls to compile into the code is a TARGET question. Nobody said cross compilation is easy :-) The "simple" solution for ports may be to build 3.1 packages on 3.1 machines and 4.0 packages only on 4.0 systems. In that case, TARGET == HOST and things are much easier. I still see nothing wrong with /usr/include for a place to store a tag about the HOST. Alternately, the traditional place would be /etc. The format of the tag should be considered. IMHO, it is best if we can have one knob which works for make, sh, and cc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904010703520.3443-100000>