Hello Matthias, thanks for your rapid response. > Install g77-3.2, which contains this symlink. we installed this by chance. However I made the symlink as well, before actually trying the to build again. So it seemed to me that adding the symlink to /usr/lib fixed things.
I didn't try building after adding g77-3.2, because had no reason to think that g77-3.2 would provide the symlink; it seems an odd way to do things. When I removed it again, the build still worked, because of the link installed by g77-3.2. I think it would be simpler from the user's point of view if there were a libg2c0-dev package that supplied the link that g77-3.2 currently provides, or a dummy package that depended on g77-3.2. Then, the link would be installed when the user does the obvious thing: "oh, I want to build against that lib, I need the -dev package". However it is probably less work for you to put g77-3.2 in the "suggests" list for libg2c0. That would have helped me solve this on my own. > Is libg2c used without g77? Not sure. We were building c++ modules and linking to libraries built from fortran. I think g77 was being used for linking. Cheers Vince