Fixed minor Boost Build error reporting bugs caused by module rules not being directly available using their full names when imported from inside a class rule - an error about rule errors.error or errors.user-error not being defined was getting reported instead of the desired error. This is due to the fact that rule name resolution does not look in the current module in that case but uses the class module instead.

[SVN r79621]

v2/build/scanner.jam

@@ -40,7 +40,7 @@ class scanner
     #
     rule pattern ( )
     {
-        import errors ;
+        import errors : error : errors.error ;
         errors.error "method must be overriden" ;
     }
 
@@ -49,7 +49,7 @@ class scanner
     #
     rule process ( target : matches * )
     {
-        import errors ;
+        import errors : error : errors.error ;
         errors.error "method must be overriden" ;
     }
 }

v2/tools/gcc.jam

@@ -326,7 +326,7 @@ class gcc-pch-generator : pch-generator
         if $(header-basename) != $(name)
         {
             local location = [ $(project).project-module ] ;
-            import errors ;
+            import errors : user-error : errors.user-error ;
             errors.user-error "in" $(location): pch target name '$(name)' should
                 be the same as the base name of header file '$(header-name)' ;
         }