|
From: | Smith, Ron D - Exelis |
Subject: | [bug-gnubatch] GNU Batch Fails To Build |
Date: | Mon, 4 May 2015 23:11:55 +0000 |
FWIW, I tried to find ‘\bline_count\b’ in the source code, and it is in util/msglex.l.
>grep --recursive -P '\bline_count\b' . ./util/msgparse.y:extern int line_count; ./util/msgparse.y: fprintf(stderr, "Parse error: %s on line %d\n", msg, line_count); ./util/msgparse.y: int lc = line_count; ./util/msgparse.y: while (line_count == lc); ./util/msgparse.y: fprintf(stderr, "Unknown help file %s on line %d\n", $1, line_count); ./util/alloc.c:extern int errors, line_count; ./util/alloc.c: fprintf(stderr, "Undefined name %s near line %d\n", ve->val_un.val_name->vn_string, line_count); ./util/alloc.c: fprintf(stderr, "Macro %s is redefined line %d\n", name, line_count); ./util/helpparse.c:extern int errors, line_count, pass1; ./util/helpparse.c: fprintf(stderr, "Help text definition at line %d not used anywhere: ", line_count); ./util/helpparse.c: line_count = 1; ./util/msglex.l:int line_count = 1; ./util/msglex.l:\n line_count++; ./util/msglex.l: int start_line = line_count; ./util/msglex.l: line_count++; ./util/msglex.l: line_count++; ./util/msglex.l: line_count, start_line); ./util/msglex.l: line_count++; ./util/msglex.l: int start_line = line_count; ./util/msglex.l: line_count++; ./util/msglex.l: line_count++; ./util/msglex.l: line_count, start_line); ./util/msglex.l: line_count++; ./util/msglex.l: fprintf(stderr, "Had a \'%c\' on line %d\n", yytext[0], line_count); Binary file ./util/helpparse.o matches Binary file ./util/msgparse.o matches Binary file ./util/msglex.o matches Binary file ./util/alloc.o matches Binary file ./util/helpparse matches However your log seems to be missing a lot of information because right after “make”, it goes directly into linking for helpparse, without building the source code. If you start with a clean tarball, what is the entire log? If you look
at the symbol table for msglex.o does it have an extern for line_count? Ron Smith Exelis 7850 S. Hardy Dr., Suite #120 This e-mail and any files transmitted with it may be proprietary and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of Exelis Inc. The recipient should check this e-mail and any attachments for the presence of viruses. Exelis Inc. accepts no liability for any damage caused by any virus transmitted by this e-mail. |
[Prev in Thread] | Current Thread | [Next in Thread] |