On Wed, 28 Jun 2000, Mark Murray wrote:
> > > 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
> > 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
> 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.
Also because miniperl and libperl want libm, and that
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 t
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 fi
