|
NAMETest::Parser::KernelBuild - Perl module to parse output from Linux kernel builds.SYNOPSISuse Test::Parser::KernelBuild; my $parser = new Test::Parser::KernelBuild; $parser->parse($text); printf("Num Errors: %8d\n", $parser->num_errors()); printf("Num Warnings: %8d\n", $parser->num_warnings()); Additional information is available from the subroutines listed below and from the Test::Parser baseclass. DESCRIPTIONThis module provides a way to extract information out of kernel builds, suitable for use in kernel test harnesses, similar to if you did `cat build.log | grep 'errors:' | wc -l`, except that this module also checks if the system is in the 'make config' or 'make bzImage' stages and skips any false positives that might be encountered there.FUNCTIONSAlso see Test::Parser for functions available from the base class.new()Creates a new Test::Parser::KernelBuild instance. Also calls the Test::Parser base class' new() routine. Takes no arguments.make_targets() Returns a list of the different targets that were built by make. config_file() Returns the name of the kernel .config file used, if any states() Returns a list of the various steps in the build process (e.g. config, make, modules_install, etc.)
Override of Test::Parser's default parse_line() routine to make it able to parse kernel build logs. config_file()Returns the config file name, if one is indicated in the build log output. The parser expects this appears in a line of the form: "^Using default config file '(.+)'$"num_states()The number of states the parser noticedstates()Returns a reference to an array of the different build states (make config, make, make modules_install, etc.) found in the build.num_make_targets()The number of make targets seen during the build stage.make_targets()Returns a hash referencewarnings errors states make_targets AUTHORBryce Harrington <bryce@osdl.org>COPYRIGHTCopyright (C) 2005 Bryce Harrington. All Rights Reserved.This script is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSOTest::ParserPOD ERRORSHey! The above document had some coding errors, which are explained below:
Visit the GSP FreeBSD Man Page Interface. |