I've also forwarded the relevant parts of this thread to Martin Peters, who can perhaps put something in the configure scripts to fix it more properly, e.g., by returning a non-zero exit code.
On 22/03/2012, at 10:02 AM, Daniel Roe wrote:
> Same issue in configure.in (line 386). I think the bottom line is,
> unless someone knows that mtkpp should/does work under cygwin, it
> should be disabled when '-cygwin' is specified.
>
> -Dan
>
> On Wed, Mar 21, 2012 at 2:46 PM, Jason Swails <jason.swails.gmail.com> wrote:
>> But configure is automatically generated by autoconf, yes? If so, is this
>> an issue with autoconf or the configure.in file?
>>
>> On Wed, Mar 21, 2012 at 4:39 PM, Daniel Roe <daniel.r.roe.gmail.com> wrote:
>>
>>> More details: MTKPP configure actually does choke under cygwin, but
>>> exits with no status (hence 0), so Amber configure doesnt think
>>> anything is wrong.
>>>
>>> The issue is on line 16654 of mtkpp/configure:
>>>
>>> *) platform=UNKNOWN
>>> is_unknown=yes
>>> echo 'ERROR: this platform is not supported at this time!'
>>> exit ;;
>>>
>>> That should be changed to 'exit 1'.
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Mar 21 2012 - 14:30:04 PDT
