This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Cross-compilers co-residence question
- To: GCC Bug List <gcc-bugs at gcc dot gnu dot org>
- Subject: Cross-compilers co-residence question
- From: Bill Webster <billw at lineo dot com>
- Date: Tue, 05 Sep 2000 17:17:34 -0600
- Organization: Lineo, Inc.
I have been working with two cross-compilers, an Intel version and a
PowerPC version. I have installed both of them into /usr/local. While do
some evaluation of how the packages co-reside I discovered that there
are 5 binaries which are unique exe's but which exist in the same
directory.
When I build the Intel cross-compiler and install it the five files are,
and they all appear to be Intel specific files:
/usr/local/bin/cpp - executable
/usr/local/bin/gcov - executable
/usr/local/lib/libbfd.a - library
/usr/local/lib/libiberty.a - library
/usr/local/lib/libopcodes.a - library
When I build the PowerPC cross-compiler and install it the above five
files are replaced by PowerPC versions. Now if I am correct the first
two are created from the build of gcc but the remaining 3 library files
come from glibc.
Is this apparent overlap of binaries a problem?
Is it safe to either version of these files regardless of the desired
target?
Are these files in the correct location? or do they need to be placed
into a platform specific directory?
--
=============================================================
Bill Webster