Thread: [Comp-hist-devel] Re: Troubles with the C parser

comp-hist-devel

[Comp-hist-devel] Re: Troubles with the C parser

From: Kurt R. <ku...@ra...> - 2000-08-30 17:02:33

The C parser in CVS fails to compile:
 
 [kurt@linux new]$ make
 cc -o html html.c
 /tmp/cciPM1HH.o: In function `main':
 /tmp/cciPM1HH.o(.text+0xa2): undefined reference to `parse_files'
 collect2: ld returned 1 exit status
 make: *** [all] Error 1
 
 [kurt@linux new]$ make parser
 cc     parser.c   -o parser
 parser.c: In function `get_line':
 parser.c:111: `by' undeclared (first use in this function)
 parser.c:111: (Each undeclared identifier is reported only once
 parser.c:111: for each function it appears in.)
 make: *** [parser] Error 1
 
 [kurt@linux new]$ make html
 cc -o html html.c
 /tmp/ccU0bnzp.o: In function `main':
 /tmp/ccU0bnzp.o(.text+0xa2): undefined reference to `parse_files'
 collect2: ld returned 1 exit status
 make: *** [html] Error 1

Re: [Comp-hist-devel] Re: Troubles with the C parser

From: Hans B P. <ha...@di...> - 2000-09-02 08:53:17

Kurt Raschke wrote:

>  [kurt@linux new]$ make parser
>  cc     parser.c   -o parser
>  parser.c: In function `get_line':
>  parser.c:111: `by' undeclared (first use in this function)
>  parser.c:111: (Each undeclared identifier is reported only once
>  parser.c:111: for each function it appears in.)
>  make: *** [parser] Error 1

This is a corruption presumably on the upload, I get the same problem
when I download and I see a difference between my master copy and the
downloaded one. One more check to do when uploading files - check that
you can download a good copy!

Oh and the mlist.ccc file also appears corrupt - duh!!!

I will put up a .tgz file directly off my linux box later on taday, at
least then any corruptions will be flagged by gzip.

>  [kurt@linux new]$ make html
>  cc -o html html.c
>  /tmp/ccU0bnzp.o: In function `main':
>  /tmp/ccU0bnzp.o(.text+0xa2): undefined reference to `parse_files'
>  collect2: ld returned 1 exit status
>  make: *** [html] Error 1

avn't seen this specific issue, but I will try it before doing the
upload later today.

Regards (and apologies)

 -- Hans B Pufal

Re: [Comp-hist-devel] Re: Troubles with the C parser

From: Hans B P. <ha...@di...> - 2000-09-02 19:05:34

Kurt Raschke wrote:
> 
> The C parser in CVS fails to compile:

This problem is fixed - it was a currupted upload.

>  [kurt@linux new]$ make html
>  cc -o html html.c

This one you need to link with parser so cc should read

   cc -o html html.c parser.c

New files available as <ftp://aconit.org/pub/files.tgz>
I downloaded the file, expanded it and built and tested the sources on
my Mandrake 70 system, all seemed OK.

Regards

  -- Hans B Pufal

Re: [Comp-hist-devel] Re: Troubles with the C parser

From: Kurt R. <ku...@ra...> - 2000-09-03 02:20:57

Well, when I try to run all of comp-hist (in other words the output of 'make dump') through the html parser, look what happens:

 Date: TBD       ^
../../dump[560] Year out of range

 Date: 1992-8-34                ^
../../dump[1736] Day out of range

 Date: 1994-12-40                 ^
../../dump[2930] Day out of range

 Type: announcemnet       ^
../../dump[6110] Invalid field value - using default

 Type: Os       ^
../../dump[6360] Invalid field value - using default

 Date: ?       ^
../../dump[6867] Year out of range

 Date: when was IRIX announced?       ^
../../dump[6969] Year out of range

 Type: Os       ^
../../dump[6999] Invalid field value - using default

 Date: ?       ^
../../dump[7101] Year out of range

 Date: ?       ^
../../dump[7108] Year out of range

 Date: ?       ^
../../dump[7115] Year out of range

 Type: Os       ^
../../dump[7565] Invalid field value - using default

 Name: Apple Computer, Inc.
      ^
../../dump[9145] Duplicate field

 Type: company
      ^
../../dump[9147] Duplicate field

 Name: Computing-Tabulating-Recording Company
      ^
../../dump[10029] Duplicate field

 Date: 1911
      ^
../../dump[10030] Duplicate field

 Type: company
      ^
../../dump[10032] Duplicate field

 Type: other       ^
../../dump[10787] Invalid field value - using default

 Type: other       ^
../../dump[10795] Invalid field value - using default

 Type: other       ^
../../dump[10801] Invalid field value - using default

 Date: would be nice       ^
../../dump[10815] Year out of range

 Date: needed       ^
../../dump[10864] Year out of range

 Type: companyhp       ^
../../dump[11597] Invalid field value - using default

 Name: Hewlett-Packard
      ^
../../dump[11598] Duplicate field

 Date: 1939
      ^
../../dump[11599] Duplicate field

 Type: company#########################
      ^
../../dump[11601] Duplicate field
Node fortran66, required field Name: not specified
be : Cannot find Code taken from  node 'apple'
next : Cannot find Code taken from  node 'apple'
Node rt11, required field Name: not specified
ibm : Cannot find Successor to  node 'ctr'
1410 : Cannot find Successor to  node '303ctr'
macos9.0.4 : Cannot find Successor to  node 'macos9apple'
macos9.0.4 : Cannot find Code taken from  node 'hp'
Node windows98sp1, using default value for required field Type:
irix6.2 : Cannot find Successor to  node 'irix 5.3'
sysVr4 : Cannot find Successor to  node 'sysVr3.2 10000'
sysVr3 : Cannot find Successor to  node 'sysVr2 1000'
sysVr2 : Cannot find Successor to  node 'sysV 1000'
sysV : Cannot find Successor to  node 'sysIV 1000'
unixsystem3 : Cannot find Code taken from  node 'ts3.0.1 1000'
v10 : Cannot find Successor to  node 'v9 100'
v9 : Cannot find Successor to  node 'v8 1000'
v7 : Cannot find Successor to  node 'v6 1000'
v6 : Cannot find Successor to  node 'v5 100'
v5 : Cannot find Successor to  node 'v4 100'
v4 : Cannot find Successor to  node 'v3 100'
v3 : Cannot find Successor to  node 'v2 100'
v2 : Cannot find Successor to  node 'v1 100'
v1 : Cannot find Successor to  node 'updp7 100'
netbsd1.4.2 : Cannot find Successor to  node 'netbsd1.4.1 1000'
netbsd1.4.1 : Cannot find Successor to  node 'netbsd1.4 1000'
netbsd1.4 : Cannot find Successor to  node 'netbsd1.3 2000'
netbsd1.3.3 : Cannot find Successor to  node 'netbsd1.3.2 1000'
netbsd1.3.2 : Cannot find Successor to  node 'netbsd1.3.1 1000'
netbsd1.3.1 : Cannot find Successor to  node 'netbsd1.3 1'
netbsd1.3 : Cannot find Successor to  node 'netbsd1.2.1 1000'
netbsd1.2.1 : Cannot find Successor to  node 'netbsd1.2 1000'
netbsd1.2 : Cannot find Successor to  node 'netbsd1.1 1000'
netbsd1.1 : Cannot find Successor to  node 'netbsd1.0 1000'
freebsd5.0 : Cannot find Successor to  node 'freebsd4.0 1000'
freebsd4.0 : Cannot find Successor to  node 'freebsd3.0 1000'
freebsd3.5 : Cannot find Successor to  node 'freebsd3.4 1000'
freebsd3.4 : Cannot find Successor to  node 'freebsd3.3 1000'
freebsd3.3 : Cannot find Successor to  node 'freebsd3.2 1000'
freebsd3.2 : Cannot find Successor to  node 'freebsd3.1 1000'
freebsd3.0 : Cannot find Successor to  node 'freebsd2.2 1000'
freebsd2.2.8 : Cannot find Successor to  node 'freebsd2.2.7 1000'
freebsd2.2.7 : Cannot find Successor to  node 'freebsd2.2.6 1000'
freebsd2.2.6 : Cannot find Successor to  node 'freebsd2.2.5 1000'
freebsd2.2.5 : Cannot find Successor to  node 'freebsd2.2.2 1000'
freebsd2.2.2 : Cannot find Successor to  node 'freebsd2.2.1 1000'
freebsd2.2 : Cannot find Successor to  node 'freebsd2.1 1000'
freebsd2.1.7 : Cannot find Successor to  node 'freebsd2.1.6 1000'
freebsd2.1.6 : Cannot find Successor to  node 'freebsd2.1.5 1000'
freebsd2.1 : Cannot find Successor to  node 'freebsd2.0.5 1000'
freebsd2.0.5 : Cannot find Successor to  node 'freebsd2.0 1000'
freebsd2.0 : Cannot find Successor to  node 'freebsd1.1.5.1 1000'
freebsd1.1.5.1 : Cannot find Successor to  node 'freebsd1.1 1000'
freebsd1.1 : Cannot find Successor to  node 'freebsd1.0 1000'
4.4lite2 : Cannot find Successor to  node '4.4lite 1000'
4.4lite : Cannot find Successor to  node '4.4bsd 1000'
4.4bsd : Cannot find Successor to  node '4.4alpha 1000'
4.4alpha : Cannot find Successor to  node '4.3reno 1000'
4.3reno : Cannot find Successor to  node '4.3tahoe 1000'
4.3bsd : Cannot find Successor to  node '4.2bsd 1000'
4.1cbsd : Cannot find Successor to  node '4.1bbsd 1000'
4.1bbsd : Cannot find Successor to  node '4.1absd 1000'
4.1absd : Cannot find Successor to  node '4.1bsd 1000'
4.1bsd : Cannot find Successor to  node '4bsd 1000'
4bsd : Cannot find Successor to  node '3bsd 1000'
2.11pl400 : Cannot find Successor to  node '2.11pl335 1000'
2.11pl335 : Cannot find Successor to  node '2.11pl300 1000'
2.11pl300 : Cannot find Successor to  node '2.11pl200 1000'
2.11pl200 : Cannot find Successor to  node '2.11pl100 1000'
2.11pl100 : Cannot find Successor to  node '2.11bsd 1000'
2.11bsd : Cannot find Successor to  node '2.10.1bsd 1000'
2.10.1bsd : Cannot find Successor to  node '2.10bsd 1000'
2.10bsd : Cannot find Successor to  node '2.9seismo 1000'
2.9seismo : Cannot find Successor to  node '2.9.1bsd 1000'
2.9.1bsd : Cannot find Successor to  node '2.9bsd 1000'
2.9bsd : Cannot find Successor to  node '2.8.2bsd 1000'
2.8.2bsd : Cannot find Successor to  node '2.8.1bsd 1000'
2.8.1bsd : Cannot find Successor to  node '2.8bsd 1000'
2.8bsd : Cannot find Successor to  node '2.79bsd 1000'
2.79bsd : Cannot find Successor to  node '2bsd 1000'
2bsd : Cannot find Successor to  node '1bsd 1000'
Segmentation fault (core dumped)

On Sat, Sep 02, 2000 at 09:05:04PM +0100, Hans B Pufal wrote:
> 
> Kurt Raschke wrote:
> > 
> > The C parser in CVS fails to compile:
> 
> This problem is fixed - it was a currupted upload.
> 
> 
> >  [kurt@linux new]$ make html
> >  cc -o html html.c
> 
> This one you need to link with parser so cc should read
> 
>    cc -o html html.c parser.c
> 
> 
> New files available as <ftp://aconit.org/pub/files.tgz>
> I downloaded the file, expanded it and built and tested the sources on
> my Mandrake 70 system, all seemed OK.
> 
> Regards
> 
>   -- Hans B Pufal
> _______________________________________________
> Comp-hist-devel mailing list
> Com...@li...  
> http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel

Re: [Comp-hist-devel] Re: Troubles with the C parser

From: Hans B P. <ha...@di...> - 2000-09-03 08:28:40

Kurt Raschke wrote:
> 
> Well, when I try to run all of comp-hist (in other words the output of 'make dump') through the html parser, look what happens:
> 
>  Date: TBD       ^
> ../../dump[560] Year out of range

Well, that date is not correct!

>  Date: 1992-8-34                ^
> ../../dump[1736] Day out of range

Yes, day number must be < 31

 ...  snip snip ...  more of the same

>  Type: announcemnet       ^
> ../../dump[6110] Invalid field value - using default

Missspelt 

>  Type: Os       ^
> ../../dump[6360] Invalid field value - using default

Accespt os or OS only

>  Name: Apple Computer, Inc.
>       ^
> ../../dump[9145] Duplicate field

Presumably there is already a Name: defined for this node

> Node fortran66, required field Name: not specified

No name specified for fortran66

> be : Cannot find Code taken from  node 'apple'
> next : Cannot find Code taken from  node 'apple'

The node apple is not found

> Node rt11, required field Name: not specified

rt11 has no name node

  ... snip snip ..

> 2.8bsd : Cannot find Successor to  node '2.79bsd 1000'
> 2.79bsd : Cannot find Successor to  node '2bsd 1000'
> 2bsd : Cannot find Successor to  node '1bsd 1000'

Most of the above are nodeids which cannot be found, is it a spacing 
issue? e.g should the last one read "lbsd1000"

> Segmentation fault (core dumped)

Hmm, this one worries me!

Well mostly, the parser is doing its job of validating the input. There
are a lot of invalid datae fields, some Type fields with unsupported
values and node links which don't!

What do you suggest? I can relax the parser checking, but I think the
better solution is to fix the bad fields. I am more than open to
adjusting the parser checks in appropriate ways, eg making the type
field case insensitive would fix one or two issues.

Let me know.

-- Hans

Re: [Comp-hist-devel] Re: Troubles with the C parser

From: Kurt R. <ku...@ra...> - 2000-09-03 11:13:18

I agree that the primary solution is to fix the fields that don't work, and then go back and fix whatver is causing the parser to coredump.  However, with the exception of the date fields, a lot of the errors that were flagged run fine on other parsers, so it may be a matter of both cleaning up the code a bit and loosening up the parser's strictness.

-Kurt
On Sun, Sep 03, 2000 at 10:27:45AM +0100, Hans B Pufal wrote:
> (removed program output) 
> Well mostly, the parser is doing its job of validating the input. There
> are a lot of invalid datae fields, some Type fields with unsupported
> values and node links which don't!
> 
> What do you suggest? I can relax the parser checking, but I think the
> better solution is to fix the bad fields. I am more than open to
> adjusting the parser checks in appropriate ways, eg making the type
> field case insensitive would fix one or two issues.
> 
> Let me know.
> 
> -- Hans
> _______________________________________________
> Comp-hist-devel mailing list
> Com...@li...  
> http://lists.sourceforge.net/mailman/listinfo/comp-hist-devel

Re: [Comp-hist-devel] Re: Troubles with the C parser

From: Hans B P. <ha...@di...> - 2000-09-03 11:54:49

Kurt Raschke wrote:
 
> I agree that the primary solution is to fix the fields that don't work, and then go back and fix whatver is causing the parser to coredump.  However, with the exception of the date fields, a lot of the errors that were flagged run fine on other parsers, so it may be a matter of both cleaning up the code a bit and loosening up the parser's strictness.

Actually none of the errors you see are fatal, e.g for the date errors,
I simply flag the error and continue, ditto for the link errors.

I have changed the parser a little to loosen up date handling and space
sin node links (though not yet in node ids) are suppressed.

Can you send me by private e-mail a copy of the data file, I still don't
have all the necessary components in place to run the make. 

My biggest worry in the core duump so if I can have the data file I can
work on that...

Regards

 -- Hans

[Comp-hist-devel] Fixes for motorola/68xxx and changes to html.c

From: Hans B P. <ha...@di...> - 2000-09-05 08:05:42

I have uploaded to <ftp://aconit.org/pub/sep5.tgz> two files:

   motorola/68xxx

	Added date for 6809 and reference where I got the date (GMPP)
   
        Commented out 88100, with a comment as to why: 88000 is a
chipset
        comprising a processor the 88100 and an MMU the 88200, so we do
not
        need to cite both 88000 and 88100.

with this file changed, the C parser reports no errors - Yeah!

   scripts/new/html.c

         For references which begin with "http:" I make them real web
links
         so you can follow those linkes. 
         Todo: recognize other web addresses like ftp://, mailto: etc


 -- Hans

[Comp-hist-devel] The whole enchilada

From: Hans B P. <ha...@di...> - 2000-09-06 01:24:47

I generated an HTML file from all the data we currently have on-line. It
took a little editing and I will upload the necessary files later on.

Its a 2Mb file ! available at <http://www.aconit.org/dd.html>

All internal links should work fine, external links as always are
subject to verification.


Enjoy,

  -- Hans