Jose Romildo Malaquias wrote:

2. The compilation goes smoothly. Installation too. But should I keep the files /usr/lib/gcc-lib/i386-redhat-linux/2.8.1/{libgcc.a,spec} or they can be safely removed (and then GPC uses the ones from the EGCS installation)?

I think they can safely be removed -- for now. Currently, as you correctly noted, it is necessary to have the same version of GCC as of GPC. In the future, we hope to relax this restriction so GPC will work with any GCC version installed. If that's a different version, there won't be libgcc.a and specs in GPC's directory, so the files from GPC should be kept. But if it's the same version, the files from GCC should probably be used. This might be a problem. Does RPM provide a way to handle such situations?

I have worked out rpm packages for the latest GPC beta. As I am not an experienced GPC user, would somebody take a look at the spec file and comment it.

I'm not familiar with RPM specs, so I won't comment on them. Just two points: : Copyright: GPL If you want to be very precise, you could add LGPL (which holds for the run time system) here. : Url: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/ http://home.pages.de/~GNU-Pascal/ is preferable. Currently, it points to the same URL, but if the former should ever change, the latter will remain the same. Frank -- Frank Heckenbach, frank@fjf.gnu.de, http://fjf.gnu.de/ GPC To-Do list, latest features, fixed bugs: http://agnes.dida.physik.uni-essen.de/~gnu-pascal/todo.html