Date: Tue, 27 Jun 2000 08:08:15 +0200 From: Mark Murray <mark@grondar.za> To: obrien@FreeBSD.org Cc: current@FreeBSD.org Subject: 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-ID: <200006270608.IAA54558@grimreaper.grondar.za> In-Reply-To: <20000626140615.H64105@dragon.nuxi.com> ; from "David O'Brien" <obrien@FreeBSD.org> "Mon, 26 Jun 2000 14:06:15 MST." References: <20000626140615.H64105@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006270608.IAA54558>