Re: 32/64-bit Library Separation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4 April 2012 16:56, Brian McGrew wrote:
>  gcc for some testing we're doing, using the vendor's configuration
> options (printed via gcc -v)

What exactly are those options?  Those options are what controls how
GCC is built and where it's installed, and we don't all have a CentOS
6.2 box lying around to check them.

You might not want to copy those options verbatim, as the distro's GCC
might be built in an atypical way in order to ship separate RPMs for
e.g. gcc, libgcc.i686, libgcc.x86_64 etc.

If you use 'rpm -ql' on the distro packages you'll see nothing goes in
/usr/lib64, the 64-bit libs go in
/usr/lib/gcc/x86_64-redhat-linux/x.y.z and the 32-bit libs go in a
sub-directory of that called 32.  Again, you might not want to copy
the vendor's options exactly.


> So, when I'm linking I end up with errors.

What errors?



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux