Mariusz Zynel wrote:

Claude, Victor and Others

Khimenko Victor wrote:

...

30-Jun-00 13:16 you wrote:

...

Maruisz,

...

The package wants to install in /usr/local. Will this clobber (i.e. overwrite) my existing gcc 2.95.2 installation?

If gcc is installed in /usr/local then it CAN do it. Probability is SMALL, though: files common for gcc and gpc should be equal anyway.

Victor is right. Since my package is based on gcc 2.95.2, I think common files i.e. libgcc.a, collect2 and specs should be equal up to functionality.

One problem I've seen with libgcc.a:

It contains common code used by all compilers and some special code for C++ (and perhaps other languages such as Fortran). So, if the GPC binary was built with C++ disabled, the libgcc.a might be missing this code, causing C++ programs to fail.

However, GPC does not add special code to libgcc.a (all of GPC's runtime code is in libgpc.a), so keeping (or restoring) the libgcc.a from the GCC installation is safe for C and C++, and should work for GPC as well.

Files my differ due to compiler used. Please, correct me if I'm wrong.

Different compiler versions might have slightly different libgcc.a's (though I've done a mixed C/C++/Pascal project with different versions of GCC, G++ and GPC, and it was linked without problems under Solaris and Linux), but in this case there's no danger of overwriting files because the compiler backend version (e.g., 2.95.2) is part of the directory name.

Sorry List for being a bit OT,

Not really, IMHO. :-)

Frank