YAQ on /usr/bin/ld

Bill McGonigle bill at bfccomputing.com
Wed Jul 23 13:47:17 EDT 2008


On Jul 23, 2008, at 13:21, Labitt, Bruce wrote:

> /lib
> is seen before /lib64.  What does this mean?

well, that reflects the search order, but that shouldn't be a problem  
if it finds the correct one.  If ldconfig is seeing it, ld should  
know about it...

> WRT adding paths, how does one name the file?  I presume the contents
> are the desired path.


Right, and the filenames are just for humans' sake.

I'd be inclined to name it the same as the basename of whichever RPM  
package provides the file.

i.e., if:

   yum whatprovides /lib64/foo/bar

says:

   libbar.3.2.4-i386

then call it libbar, just for sanity's sake down the line.

But it sounds like you don't need to do this.  I'm not current on 64  
bit linking - anybody know if this can be caused by the presence of a  
32-bit library getting in the way?  I'm guessing linux doesn't know  
how to link 32bit and 64bit libraries to each other?

-Bill

-----
Bill McGonigle, Owner           Work: 603.448.4440
BFC Computing, LLC              Home: 603.448.1668
bill at bfccomputing.com		Cell: 603.252.2606
http://www.bfccomputing.com/    Page: 603.442.1833
Blog: http://blog.bfccomputing.com/
VCard: http://bfccomputing.com/vcard/bill.vcf



More information about the gnhlug-discuss mailing list