On Tue 2000-06-27 (02:41), John Baldwin wrote:
> On 26-Jun-00 David O'Brien wrote:
> > On Mon, Jun 26, 2000 at 10:28:53PM +0200, Mark Murray wrote:
> >> > Since I'm now through it, I don't know the latest problem, but the
> >> > last thing I saw that the old lib got used with the new perl (or the
> >> > other way round) and that looks like it can be fixed with some path
> >> > adjustments.
> >> 
> >> The problem here is that miniperl needs to be built early enough
> >> to be in the path perl "proper" is done.
> >> 
> >> I thought build-tools was the answer; sadly that seems to be wrong.
> >> Now I'm looking at cross-tools (out of src/makefile.inc1).
> > 
> > Adding something to bootstrap-tools implies that we can't use the
> > installed miniperl (backward compatibility problem) or the host doesn't
> > have miniperl.  The bootstrap-tools built miniperl would then be used
> > throughout the build and install stages.
> I think that's what we have in this case.  We need the newer version of
> miniperl to build perl, correct?

Yes, exactly.  We were only building libperl (statically) and miniperl
in the build-tools stage, so that miniperl (statically linked with
libperl) is available for the building later.

The choice to use crosstools is easier, since it by default installs the
tool into the "strict path", but Mark used build-tools and a path to
miniperl to do it instead, presumably since it is restricted to a very
minor bit of the tree.

(This reminds me that I have a skeleton document about 'make world' that
needs serious attention.  Too many projects.)

Neil Blakey-Milner
Sunesi Clinical Systems

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to