On Mon, 7 Aug 2000, Peter Prymmer wrote:

> 
> 
> On Mon, 7 Aug 2000, Craig A. Berry wrote:
> 
> > Thanks so much for posting this.  At first blush it looks like it has all 
> > the File::Temp stuff (except for what I don't have working yet :-( ) and the 
> > b.t patch, but not the cgi-function.t patch and only one of two hunks from 
> > the descrip_mms.template patch.  The descrip template in 6529 has 
> > "[.lib]lib.pm" in the  LIBPREREQ target instead of utils2 -- I'm not sure 
> > which is better or if we need both.
> 
> Hmm... I was able to build without altering [.vms]descrip_mms.template.
> Thanks for turning this up.  I'll have to take a closer look.

OK I had a look and I like the fact that it works in the LIBPREREQ macro
(which I think is used in the unix Makefile.SH -> Makefile).   I had in
fact tried to build perl with [.lib]lib.pm listed in
LIBPREREQ.  Unfortunately for me I listed it first in that macro, but it
needs (at least) Config.pm for the PL extraction process to work.  Hence
I put it in utils2 and someone (Jarkko?) put it into LIBPREREQ where it
belongs.

> I think the latter was what I had in mind when I wrote the "not".  Thanks
> too for that.  I'll let you know how the patching went when I get home.

OK a few things: the attached patch had carriage returns at each endl
that some uudecode programs complained about.  At any rate you saved
you local copy of the configure_com_faq.html file with a browser
that managed to set line breaks in places where the original did not
have them so all 13 hunks failed.  However, I *think* I managed to
apply the patch by hand so you might want to pay another visit to
see what I might have missed.  I may add to the doc at some point as well.
I really appreciate your input.  Thank you.

Oh,

I have posted an updated configure.com5.gz on the web at:

  http://www.best.com/~pvhp/vms/cfgperl_6529/

so have at it.  Btw the gzipped configure.com is just over 40k and
won't make it in its entirety to the p5p list owing to message size
restrictions.

Peter Prymmer


Reply via email to