This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Libraray issue on Linux x86_64
- From: Kai Ruottu <karuottu at mbnet dot fi>
- To: gcc-help at gcc dot gnu dot org
- Cc: ashwanib at cadence dot com
- Date: Thu, 21 Sep 2006 16:02:27 +0300
- Subject: Re: Libraray issue on Linux x86_64
Ashwani Bhat wrote:
They include the archive files like "libiberty.a" and shared objects
like "libopcodes-2.16.1.so". Can we just copy these files from 32 bit
build under this directory ?
The first sounds being produced and installed by the binutils
build, not by GCC... The GCC build produces the 'libiberty.a'
for the '$host' too, but I think it going into the '$prefix/lib', not
into the '/lib' or '/usr/lib'. Anyway it should be 64-bit because
the $host is 64-bit ! With the '*lib' I meaned the '/lib' and the
'/usr/lib', you maybe the '$prefix/lib'... But IF the $prefix is the
'/usr', then the '$prefix/bin' is '/usr/lib' !
So please report this thing as a bug ! The default $prefix is
'/usr/local' but native GCCs are usually built using '--prefix=/usr'.
Some 'lapsus' probably made by the 64-bit/32-bit bi-arch GCC
maintainer(s) ...
I really cannot say where the 64-bit libs produced for the $host
should be put in this case.
But using the option '--enable-version-specific-runtime-libs' in the
GCC configure the two libiberty's produced for the $target will be
installed into the GCC-version specific directories. And then they will
be found before the ones in '$prefix/lib' when linking !