Date: Fri, 11 Feb 2005 13:47:38 +0100 From: "Devon H. O'Dell" <dodell@sitetronics.com> To: Robert Millan <rmh@debian.org> Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/77355: Detect i*86 subarches for uname Message-ID: <1108126058.4084.39.camel@localhost.localdomain> In-Reply-To: <20050211122554.GB27691@khazad.dyndns.org> References: <200502110840.j1B8eIUq074988@freefall.freebsd.org> <1108117105.4084.20.camel@localhost.localdomain> <20050211122554.GB27691@khazad.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2005-02-11 at 13:25 +0100, Robert Millan wrote: > On Fri, Feb 11, 2005 at 11:18:25AM +0100, Devon H. O'Dell wrote: > > > > > > With this change, the config.guess triplet becomes i686-unknown-freebsd5.3 > > > (or whatever suitable). Some programs detect this and use it for optimisation. > > > > The proper way to specify optimizations in FreeBSD is with relevant > > entries in /etc/make.conf. > > But this only affects the port system when passing --host and --build to > configure scripts, right? > > I'm more concerned about programs that run config.guess on their own. Actually, make.conf is used to modify various flags used in the files in /usr/share/mk and /usr/ports/Mk. Nothing would be passed to --host and --build; the Makefile would use the desired CFLAGS when building, which might include -march=whatever. Since FreeBSD encourages the use of its ports collection (and other package systems such as pkgsrc use similar tricks to do this), I really don't see this as an issue. Perhaps the only thing I see this useful for is if you don't particularly care to use any package system, which isn't really good for the project since we don't get to benefit from the software you're using. It's farily simple to wrap any software into a port file, regardless of what utilities you are using. --Devon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1108126058.4084.39.camel>