On Tue, Jun 10, 2008 at 06:00:39AM -0700, Will Coleda via RT wrote:
> Interesting. I tried to duplicate this error by removing my platform's
> hints file and re-running. I get the message you describe, but then
> Configure.pl completes, and at the -end-, gracefully says:
> 
> During configuration the following steps failed:
>     01:  init::manifest
>     05:  init::hints
> You should diagnose and fix these errors before calling 'make'
> 
> Did you get this far, or did Configure.pl just stop completely for you
> where your log cuts off?

That was the end.  The next line was a prompt.

> Now, the desired behavior here IMO should be that if we can't find a
> hints file for your platform... the build should continue with no
> problems or warnings, except that perhaps in verbose mode we say
> something like "no hints file, assuming defaults.".

That sounds reasonable.

> The offending line is in config/init/hints.pm, where we say:
> 
>     eval "use $hints";
>     die $@ if $@;
> 
> We should probably first check to see if the file exists before running
> the use statement; then the die is only because of invalid perl, not
> "file not found."
> 
> Your workaround, btw, is probably:
> 
>  touch config/init/hints/hurd.pm

I'll try this when I get home.

> Thanks for the report, I'm interested to see how we do here once we get
> past this small config bump.

Well, that's what I thought: "Hmm, I've got this new Hurd install, I
wonder if parrot will run on it."

This is definitely just an experiment.  Kind of uber-geek if we get it
working, though.

-kolibrie

Attachment: signature.asc
Description: Digital signature

Reply via email to