On Thu, Apr 19, 2001 at 10:35:30PM -0700, Prymmer/Kahn wrote:
>
> Jarkko Hietaniemi wrote:
>
> >> Sorry about that... could the extension finding be made somehow dynamic?
> >
> > Just to clarify the obvious: I was under no misconception that just
> > adding the new extensions to the list would make the new extensions
> > magically build in VMS. It's just my not-so-subtle way of throwing
> > the ball to you (and then quickly run away, myself), so to speak.
>
> I ought to have been clearer myself: the extensions list does not
> break in 9718 but if you add to it the various ext/ensions missing
> from the VMS build then it breaks and my patch addresses both of
> those issues.
>
> Indeed the extension finding _should_ be done dynamically, and doing so
> has been a longer term goal of the work on configure.com. The patch that
> I provided earlier today is a first step toward that goal since it allows
> for a larger list of extensions than is currently possible on VMS (prior
> to the patch the limit was around 250 characters). A subsequent patch
> should allow the extensions list to exceed about 1000 characters.
>
> After that the task of dynamically generating the list could be
> carried out but I'll mention some of the reasons why it hasn't
> been done yet (apart from severe tuit shortages). The current
> method used on more POSIXly oriented systems (this excerpted from
> Configure in perl@9698 since it was handy at the time I wrote this)
> looks a bit like:
Thanks for the explanation.
I'll apply the skip-the-tests-if-not-built patch but I'll skip the
configure.com patch since in the 7962 snapshot I diddled some more with
configure.com.
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
