Re: Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
> It is possible the Perl build Makefiles have a slight bogon that prevents > things from working properly in this stage? :-) Uh Huh! > > > Note that bootstrap-tools are built (and installed under /obj) to be run > > > > OK - I'll try again fro build-tools. > > I tried that (on my Alpha). Same breakage. Erm - I meant I'll try to use (and fix) build-tools instead of cross-tools. 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
On Tue, Jun 27, 2000 at 08:08:15AM +0200, Mark Murray wrote: > What you say supports the theory that build-tools is the answer; however > build-tools seems to want to do an in-place build - not to install the > tool(s) somewhere into the path like cross-tools. I'm in trouble with > cross-tools because libraries are not available :-(. It is possible the Perl build Makefiles have a slight bogon that prevents things from working properly in this stage? > > Note that bootstrap-tools are built (and installed under /obj) to be run > > OK - I'll try again fro build-tools. I tried that (on my Alpha). Same breakage. -- -- David ([EMAIL PROTECTED]) 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
> > 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. What you say supports the theory that build-tools is the answer; however build-tools seems to want to do an in-place build - not to install the tool(s) somewhere into the path like cross-tools. I'm in trouble with cross-tools because libraries are not available :-(. > Note that bootstrap-tools are built (and installed under /obj) to be run > on the host. This means that miniperl is going to be built a second time > for the target architecture. The bootstrap-tools stage is designed to > solve incompatibilities caused by versions of tools installed on the > system and the requirements (for newer ones) by the source-tree. OK - I'll try again fro build-tools. 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
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. Note that bootstrap-tools are built (and installed under /obj) to be run on the host. This means that miniperl is going to be built a second time for the target architecture. The bootstrap-tools stage is designed to solve incompatibilities caused by versions of tools installed on the system and the requirements (for newer ones) by the source-tree. -- -- David ([EMAIL PROTECTED]) 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/
It seems Mark Murray wrote: > > If I'm not mistaken, all open problems are like "Perl lib version > > (v5.6.0) doesn't match executable version (5.00503) at Config.pm line > > 18." > > Hmm... > > > That should be easy to reproduce on your development system by just > > copying an old /usr/bin/perl executable to it and trying to build. > > What bothers me is how other boxes managed to get past this point. > I think there may be a race... I know of no boxes that made it past that point :( -Søren 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
> If I'm not mistaken, all open problems are like "Perl lib version > (v5.6.0) doesn't match executable version (5.00503) at Config.pm line > 18." Hmm... > That should be easy to reproduce on your development system by just > copying an old /usr/bin/perl executable to it and trying to build. What bothers me is how other boxes managed to get past this point. I think there may be a race... 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
> 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). 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
In <[EMAIL PROTECTED]>, Mark Murray wrote: > > Message to others for bootstrapping: > > > > Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624, > > build and install it manually, then update both dirs to HEAD and do a > > world with the new perl in place. > > Now you can colour me flummoxed. :-(. > > Have you a script(1) of that? Sorry, my -current box is now through it. If I'm not mistaken, all open problems are like "Perl lib version (v5.6.0) doesn't match executable version (5.00503) at Config.pm line 18." That should be easy to reproduce on your development system by just copying an old /usr/bin/perl executable to it and trying to build. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
In <[EMAIL PROTECTED]>, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Martin Cracauer writes: > : [CC'ed to current] > : Message to others for bootstrapping: > : > : Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624, > : build and install it manually, then update both dirs to HEAD and do a > : world with the new perl in place. > > Does this mean that I need to add a ntoe to UPDATING? I rather think that it should be fixed. Imagine going from 4-stable to 5-current: in that case you probably can't build the 2624 version manually due to other reasons. 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. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
> Message to others for bootstrapping: > > Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624, > build and install it manually, then update both dirs to HEAD and do a > world with the new perl in place. Now you can colour me flummoxed. :-(. Have you a script(1) of that? 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 Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
In message <[EMAIL PROTECTED]> Martin Cracauer writes: : [CC'ed to current] : : In <[EMAIL PROTECTED]>, Martin Cracauer wrote: : > In <[EMAIL PROTECTED]>, Mark Murray wrote: : > > May I have a login on your build box to have a look? : > : > It would be more useful if you could put a log of your buildworld (at : > least the perl-related parts) somewhere so I can look how EXTERN.h is : > supposed to be built and where it ends up. : : Never mind, I'm now through it, this time my tree has hosed due to the : testing I did earlier today. : : Message to others for bootstrapping: : : Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624, : build and install it manually, then update both dirs to HEAD and do a : world with the new perl in place. Does this mean that I need to add a ntoe to UPDATING? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Bootstrapping perl (Re: cvs commit: src/gnu/usr.bin/perl Makefile.inc src/gnu/usr.bin/perl/libperl Makefile src/gnu/usr.bin/perl/miniperl Makefile)
[CC'ed to current] In <[EMAIL PROTECTED]>, Martin Cracauer wrote: > In <[EMAIL PROTECTED]>, Mark Murray wrote: > > May I have a login on your build box to have a look? > > It would be more useful if you could put a log of your buildworld (at > least the perl-related parts) somewhere so I can look how EXTERN.h is > supposed to be built and where it ends up. Never mind, I'm now through it, this time my tree has hosed due to the testing I did earlier today. Message to others for bootstrapping: Checkout perl (contrib/perl5 and gnu/usr.bin/perl) from -D 2624, build and install it manually, then update both dirs to HEAD and do a world with the new perl in place. Martin -- % Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
