[mpich-discuss] handling illegal values in --enable-error-messages

[Halim Amer]

Sayan,

Configure options given at the root directory are propagated to the 
sub-directories that contain some independent components (in the sense 
they can have a standalone build) such as Hydra, ROMIO, OpenPA and so 
on. These components may have their own options and may not need some 
MPICH-core options. So, detecting illegal options at the root level is 
difficult and not supported at the current state. That's why you can 
pass illegal options and only detect them a complication time.

--Halim
www.mcs.anl.gov/~aamer

On 11/2/15 12:34 PM, Sayan Ghosh wrote:
> Hi,
>
> I noticed that if I pass something illegal to
> --enable-error-messages=<>, then configure just throws a warning and
> continues, but the build fails during compilation. Not sure if this is
> intended, so just reporting.
>
> src/mpi/attr/attrutil.c(99): error: expected an expression
>    #if MPICH_ERROR_MSG_LEVEL < MPICH_ERROR_MSG_ALL
>                              ^
>
> src/mpi/attr/attrutil.c(159): error: expected an expression
>    #if MPICH_ERROR_MSG_LEVEL < MPICH_ERROR_MSG_ALL
>
>
> --
> Regards,
> Sayan
>
>
> _______________________________________________
> discuss mailing list     discuss at mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss
>
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss