Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
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 breaks at build time because it cannot be found. :-( M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
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, and it is doing that now. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
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 install stages. I think that's what we have in this case. We need the newer version of miniperl to build perl, correct? Yes, and it is doing that now. Except on alpha. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
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? -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Mak
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 -- Neil Blakey-Milner Sunesi Clinical Systems [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
