Configure fails because of overzealous hostname matching

[aowen87]

A small, but highly confusing issue. Silo comes packaged with a number of preset conf files in config-site/*.conf, and will any that match the current machines hostname. In particular there is a config-site/localhost.conf (links to delenn.conf) which explicitly sets the fortran compiler to g77. It is very common that a machine will not have an explicit hostname set, especially on virtual machines.On these machines silo will not configure without explicitly overriding the "FC" environment variable.I'm sure you have some reasons for loading settings based on hostname, but maybe consider removing those conf files from the release tarball?

-----------------------REDMINE MIGRATION----------------------- This ticket was migrated from Redmine. As such, not all information was able to be captured in the transition. Below is a complete record of the original redmine ticket.

Ticket number: 2447 Status: New Project: VisIt Tracker: Bug Priority: Low Subject: Configure fails because of overzealous hostname matching Assigned to: Mark Miller Category: - Target version: 4.10.3 Author: Alex Hartsell Start: 11/05/2015 Due date: % Done: 0% Estimated time: Created: 11/05/2015 06:00 pm Updated: 11/05/2015 06:02 pm Likelihood: 3 - Occasional Severity: 2 - Minor Irritation Found in version: 4.8 Impact: Expected Use: OS: All Support Group: Any Description: A small, but highly confusing issue. Silo comes packaged with a number of preset conf files in config-site/*.conf, and will any that match the current machines hostname. In particular there is a config-site/localhost.conf (links to delenn.conf) which explicitly sets the fortran compiler to g77. It is very common that a machine will not have an explicit hostname set, especially on virtual machines.On these machines silo will not configure without explicitly overriding the "FC" environment variable.I'm sure you have some reasons for loading settings based on hostname, but maybe consider removing those conf files from the release tarball?

Comments: Well, maybe that explains why I often have so much trouble getting it to configure a fortran compiler.Thanks for pointing this out and getting to the bottom of it.Will fix in next release.