perl.perl6.build...Re: Building Perl6 on VMS by Brad Hughes- September 26, 2001 Brent Dax wrote:...> In the long term, we probably should implement something like MakeMaker;> for now, however, I think we can go with a much simpler approach.> Imagine this directory structure:> > +-+parrot> +---Makefile.in> +---(other stuff)> +--+hints> +---vms.pl> +---Makefile.vms> +---(other stuff)> > Makefile.vms would be VMS&39;s version of Makefile.in; when the VMS hints> file was called, it would copy Makefile.vms over the..http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg27.html RE: Building Perl6 on VMS by Brent Dax- September 26, 2001 (I&39;ve added perl6-build to the CC list, since this seems germane to thatlist.)Brad Hughes: Brent Dax wrote: ... > Okay. What do we need to support this Is it something that can be > done with a hints file and a few Makefile tweaks, or is it more involved > than that (My father (who worked on VMS in the Good Old Days) Gee, talk about making one feel old... :)"The Good Old Days" were only about ten years ago. (Understand, I&39;mpretty young myself, so ten years is a...http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg26.html Re: parrotconfig.h patch and others by Damien Neil- September 14, 2001 On Fri, Sep 14, 2001 at 10:20:00AM +0100, Simon Cozens wrote:> On Thu, Sep 13, 2001 at 08:54:40PM -0700, Damien Neil wrote:> > Here&39;s an updated version of my original patch, to account for recent> > changes in CVS. As before, this includes opcode-munging to let Parrot> > run on FreeBSD....> These three patches didn&39;t apply and I really want them. Hence, I&39;m> taking no more patches to:Third time&39;s the charm, maybe The following patch applies...http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg25.html Re: parrotconfig.h patch and others by Simon Cozens- September 14, 2001 On Thu, Sep 13, 2001 at 04:45:36PM -0500, Gibbs Tanton - tgibbs wrote:> I have a patch that puts parrot in front of all the header files and adds> -I.. to the makefile. However, I will wait until some of the other patches> get applied because my version is extremely hacked up and I don&39;t want to> keep sending all these patches munged together.On Thu, Sep 13, 2001 at 08:54:40PM -0700, Damien Neil wrote:> Here&39;s an updated version of my original patch, to account for...http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg24.html More Configure.pl Modifications by Brent Dax- September 13, 2001 Okay, this makes Configure generate a Parrot::Config module in thecurrent directory. This is analogous to Config.pm, except this exportsa %PConfig hash (to avoid collisions). I&39;m using Data::Dumper to createthe hash, so it&39;ll make sure you have it and just not generate the file(and tell the user) if Data::Dumper isn&39;t available. Patches after mysig. Someone suggested that we use .whatever_in instead of .whatever.infor portability reasons; this does so on the new file but leaves the.http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg23.html Re: on the long term Configure system by David L. Nicol- September 13, 2001 Jarkko Hietaniemi wrote:> The bootstrapping may take several rounds as Parrot learns...> - execute (collect output) (note that execution may not be native)I don&39;t think these two (cross-compile and build-own-tools) arestrictly compatible goals.If you are going to build your own tools and use them, thosetools will need to run in the local environment.At some point a cross-compiler will be trusting its cross-compilationtool to run in the other environment.Answering "what is a tool I.http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg22.html Re: on the long term Configure system by Jarkko Hietaniemi- September 12, 2001 On Wed, Sep 12, 2001 at 05:36:28PM -0500, David L. Nicol wrote:> Jarkko Hietaniemi wrote:> > > The bootstrapping may take several rounds as Parrot learns> ...> > - execute (collect output) (note that execution may not be native)> > I don&39;t think these two (cross-compile and build-own-tools) are> strictly compatible goals.>> If you are going to build your own tools and use them, those> tools will need to run in the local environment.Huh I do not follow..http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg21.html Re: on the long term Configure system by Dan Sugalski- September 12, 2001 At 05:36 PM 9122001 -0500, David L. Nicol wrote:>Jarkko Hietaniemi wrote:>> > The bootstrapping may take several rounds as Parrot learns>...> > - execute (collect output) (note that execution may not be native)>>I don&39;t think these two (cross-compile and build-own-tools) are>strictly compatible goals.>>If you are going to build your own tools and use them, those>tools will need to run in the local environment.I should point out that this isn&39;t...http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg20.html Re: on the long term Configure system by Simon Cozens- September 12, 2001 On Tue, Sep 11, 2001 at 04:19:12PM +0300, Jarkko Hietaniemi wrote:> P.S. Maybe the "long term" discussion should take place in> perl6-build, to draw fire from the "short term"Thanks for thinking about this; it&39;d probably be a good idea tomove to perl6-build. Simonhttp://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg19.html on the long term Configure system by Jarkko Hietaniemi- September 11, 2001 (To use Simon&39;s nomenclature)The long term goal of the Parrot build system (of which configuring isthe major part) is to bootstrap itself from ground zero, a la Parrotvon Münchausen.Ground zero is here defined as a simple C file (possibly augmented byone or more simple C headers) and a C compiler.We should not assume a certain build driver (make).We should not assume a native compilation or execution(think cross-compilation).All the above mean that neither Configure nor...http://www.nntp.perl.org/group/perl.perl6.build/2001/09/msg18.html |