Christoph Kukulies wrote
>Besides I'd be curious what the problem is. f2c is so mature
>that it is unlikely that there is a 'problem' with f2c.
>
>It's more likely there is a problem with the fortran code
>not being 100% f77 standard or something.
Thanks to Christoph and others who responded. When I originally compiled
with Redhat Linux g77 I used no options and got the segmentation error.
Based on Reinhard Katzmann's suggestion, I tried it with -O2 -Wall and now
it ran all the way through! But by comparing it with a certified .tex, I
see that the resulting TeX file seemed to have some incorrect stuff in it
(haven't tried to TeX it yet for various logistical reasons). OTOH, I
downloaded Stefan Evert's package for PMX 2.1 to the Linux Box, typed
"make", ran the resulting binary, and got a perfectly fine .tex (Way to go,
Stefan!). I'm starting to wonder whether I'm "beating my head against a
wall" with g77, especially considering the other problems people have
reported with g77-generated binaries. As long a Stefan stays on the team, is
there any reason why all UNIX users cannot use his packages?
Still, I can't completely stifle my curiosity about the g77 problems. Is
there a utility out there that checks FORTRAN code for f77 compliance?
--Don Simons
