Nicholas Clark <[EMAIL PROTECTED]> wrote:

> I don't like the build blowing up on me when there is no perldoc, and on
> some machines that I use I'm not in a position to change this.

So, as opinions aren't really matching, let's try this approach:

The configure step from that patch doesn't bail out, but prints a big
fat warning about the lack of accessing perl and parrot docs, disables
the parrot doc make target and continues.

> Nicholas Clark

leo

Reply via email to