Apparently the first time I sent this it was lost in the ether...let's see if this one makes it.
I just wanted to follow up on a conversation I had with Jim G. at #cross-lfs relative to the program interpreter path on pure-64 x86-64 systems a week or so ago. A little background. The nVidia 64-bit installer fails on pure-64 bit systems because it is looking for ld-linux-x86-64.so.2 in the /lib64 directory (Sun's 64-bit Java installer does too). There is no /lib64 if you follow the CLFS instructions for a pure 64 system. I contacted the nVidia engineers with a request to accommodate pure-64 systems that would have the interpreter in /lib (my interpretation of the FHS would use /lib on a pure-64). The nVidia engineer's response was, "According to the SysV processor-specific ABI supplement draft on http://refspecs.freestandards.org/, the standard Linux program interpreter for x86-64 systems is /lib64/ld-linux-x86-64.so.2." This draft standard states, "There is one valid program interpreter for programs conforming to the x86-64 ABI: /lib/ld64.so.1. However, Linux puts this in /lib64/ld-linux-x86-64.so.2" These apparently conflicting standards have caused issues with at least a couple people that have built pure 64 systems. It's easy to work around, but I thought it might be worth kicking around how to address the issue (if at all) in future CLFS revisions. Since sending this message originally, I've contacted the FHS folks. Their responses, "x86-64 is a multilib system and FHS explicit says that you have to use /lib64..." and "amd64 is considered a multilib system, and will remain that way." Not much more, but the full thread is here http://sourceforge.net/mailarchive/forum.php?thread_id=31785924&forum_id=3128 Regards, Andrew "Weibullguy" Rowland _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
