Re: lynx-dev LYMainLoop.c -- gcc signal 11, egcs-1.1.2

[brian j pardy]

On Sun, Oct 17, 1999, T.E.Dickey wrote:
> > On Sat, Oct 16, 1999, T.E.Dickey wrote: 
> > > > Is anyone else having any problems compiling LYMainLoop.c in dev.12?  
> > > >   
> > > > gcc  -DHAVE_CONFIG_H  -DLOCALEDIR=\"/usr/local/share/locale\" -I. -I.. 
> > > > -Ichrtrans -I./chrtrans -I.. -I../src -I../WWW/Library/Implementation   
> > > > -O2 -DLINUX  -c ./LYMainLoop.c  
> > > > gcc: Internal compiler error: program cpp got fatal signal 11  
[...]
> > > > gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release)  
> 
> I'm building with that version right now, to check (seems to work - but I'll
> try with your configuration settings).

Here are my ./configure flags:

./configure --disable-dired --disable-nls --disable-menu-options
--enable-prettysrc --enable-read-eta --enable-source-cache --enable-cgi-links
--enable-default-colors --enable-internal-links --enable-externs
--enable-nsl-fork --enable-file-upload --enable-persistent-cookies
--with-zlib --enable-gzip-help --with-screen=slang

[...]
> > Any suggestions on which functions to start with?  Probably the main 
> > loop.  Also, I just noticed in what I have up there -- it says "cpp" 
> 
> yes - or the functions "handle_LYK_xxx" that I split-out of the main
> loop.  That would be possibly better (since chopping out the main
> loop would leave a lot of orphaned private functions, while chopping
> out the functions themselves would just leave a lot of implicit
> declarations).

I've narrowed it down to within handle_LYK_digit().  It looks like the
code in the #ifndef DONT_TRACK_INTERNAL_LINKS (nasty double negatives
again) is causing it.  I'll keep digging around to try to get it down
to the particular line of code.  Defining DONT_TRACK_INTERNAL_LINKS
will allow it to compile successfully.

-- 
[A computer is] like an Old Testament god, with a lot of rules and no mercy.
                -- Joseph Campbell