[mythtv] Compiling on AMD64

Michael J. Lynch mlynch at gcom.com
Thu Feb 2 20:55:51 UTC 2006

Isaac Richards wrote:
> On Thursday 02 February 2006 15:18, Jarod Wilson wrote:
>>On Thursday 02 February 2006 12:13, Colin Guthrie wrote:
>>>Tony Brummett wrote:
>>>>I'm compiling myth for the first time on an AMD64 machine with the
>>>>x86_64 version of Fedora Core 4.  ./configure was complaining about
>>>>not being able to find libmp3lame until I added /lib64 and /usr/lib64
>>>>to /etc/ld.so.conf
>>>>I was just windering if this was normal?  I figured that either those
>>>>directories would be put in ld.so.conf by the OS installer, or that
>>>>configure would know if the arch is x86_64, then you have to look in
>>>>the 64-bit lib directories for some libs.
>>>I get that on my distro too, but as no-one else complained I didn't open
>>>a ticket.
>>>The attached diffs fix things for me.
>>>I can open a ticket if this is OK for commit,but not tested on any other
>>>distro than Mandrake 2006.0. Other systems may not use the /lib64
>>>prefix. It could be make more intelligent to check for the existance of
>>>those directories too I guess.
>>ATrpms.net MythTV builds work around the problem in a similar fashion,
>>replacing /lib with rpm's %{_lib} macro, which points appropriately to /lib
>>or /lib64, depending on the target arch.
> IMO, putting the native libraries of a system in anything other than /lib is 
> completely wacky.

Solaris does this seperate directories thing for 32 and 64 libraries
too.  It's done that way because the libraries can be named the same.
The really cute thing Solaris does is locate the 32 bit directories in
someplace other than /lib.  In /lib are libraries that are essentially
wrappers that dynamically select at runtime either th 32 or 64 bit 
library based on the word size of the application being run.

Michael J. Lynch

What if the hokey pokey IS what it's all about -- author unknown

More information about the mythtv-dev mailing list