suppress the "Could not resolve" warning when 'warningLevel' is zero

Ghost User requested to merge (removed):warning-level into master

Two years ago, commit c8cfca25 changed an error to a warning but forgot to add a check for 'warningLevel'.

This partially addresses issue #20 (closed).

Reported-by: Vincent Lefevre

Signed-off-by: Benno Schulenberg

(The second commit suppresses four more warnings when 'warningLevel' is zero. There are still other places where 'warningLevel' is not checked, but... this will have to do for now.)

Merge request reports