world's toolchain & CPUTYPE

[Ruslan Ermilov]

On Tue, Feb 28, 2006 at 07:45:20AM +0300, Alex Semenyaka wrote:
> On Sun, Feb 26, 2006 at 08:57:21PM +0200, Ruslan Ermilov wrote:
> > More details: during the install, part of the toolchain and
> > some special install tools that were built on the "build"
> > host are used.  They have been built using that host's
> > toolchain, CFLAGS, libraries, etc., but libraries is the
> > most important factor.  That means that the "install" host
> > should be CPU/syscall/etc. compatible with the "build"
> 
> Isn't is reasonable to add corresponding optional functionality
> into the buld process?
> 
No.

> For example, if -DSTATIC_TOOLCHAIN (or
> pick any other name) is set, then:
> 
> 1) build toolchain statically linked
> 
This is already the case (${XMAKE} has -DNO_SHARED).

> 2) use newly built libraries to link instead of libraries of
>   "build" host
> 
Impossible.  The tools are built "to be run on the build host".
(Some of them are also run on the install host, e.g. strip(1)).
Also, you cannot link with new libraries before you built them,
and these tools are needed to build the new libraries.

> It does not look dangerous, and it will break nothing since
> administrator will hav to take special action to turn it on.
> 
It's certainly dangerous.


Cheers,
-- 
Ruslan Ermilov
ru at FreeBSD.org
FreeBSD committer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20060228/c2e77417/attachment.bin