Hi Kai, Even if we specify '--enable-version-specific-runtime-libs' in the configure, "libiberty.a" is getting built under *lib and not under *lib64 and it is 64 bit :(. I would ideally like to have it under *lib64. Is this a bug ? Moreover, I am doing this installation under some private space, not /usr/local. Thanks and regards, Ashwani -----Original Message----- From: Ashwani Bhat Sent: Friday, September 22, 2006 10:54 AM To: Kai Ruottu; gcc-help@xxxxxxxxxxx Subject: RE: Libraray issue on Linux x86_64 Hi Kai, You are right, these libraries are from the binutils. But if I do a build without extracting binutils under the install directory, "libiberty.a" inside /lib is still 64 bit and 32 bit file is generated under lib/32. I will try with the '--enable-version-specific-runtime-libs' and see if "libiberty.a" is generated under specific directories. Thanks for your help !! Regards, Ashwani -----Original Message----- From: Kai Ruottu [mailto:karuottu@xxxxxxxx] Sent: Thursday, September 21, 2006 6:32 PM To: gcc-help@xxxxxxxxxxx Cc: Ashwani Bhat 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 !
