behavior of --with-config-file=foo.bar [SOLVED]

[jzwanzig]

Hi, currently the command ../configure --with-config-file=foo.bar runs, even if "foo.bar" doesn't exist. That is, configure churns along with its own defaults and guesses. But if the user (me for example) wants a specific config file and mistypes the name or in some other way gives a file name that doesn't exist, I think the configure system should just stop immediately with a warning that the requested config file was not found. What does everyone else think about this proposal?

Joe

[mverstra]

Great idea, happened to me countless times. One major progress in 6.0 was that it now complains about relative paths that it is unable to parse (instead of skipping the file like it used to). This means your check should be possible if Yann has time to fiddle.

Cheers

Matthieu

[pouillon]

Up to now, the choice was to ignore the file if it didn't exist, because this was what I had been requested to do. If you change your mind, I will adapt.

Let's thus say that, if there is no complaint about increasing the severity to an error by the end of the week, I'll just do it.

[jzwanzig]

Thanks, Yann, I think it would be better for the system to stop if it can't find the requested file.

Joe

[pouillon]

Will be available in Abinit 6.2.0.