library directory used in csc not always correct on 64-bit systems

[felix winkelmann]

Adam Young pointed out an error in csc:

*** csc.scm.orig	2010-03-31 19:55:22.831032315 -0400
--- csc.scm	2010-03-31 19:56:47.520908976 -0400
***************
*** 253,259 ****
  (define linking-optimization-options default-linking-optimization-options)
  
  (define library-dir
!   (prefix "" "lib"
           (if host-mode
               INSTALL_LIB_HOME
               TARGET_LIB_HOME)) )
--- 253,259 ----
  (define linking-optimization-options default-linking-optimization-options)
  
  (define library-dir
!   (prefix "" "lib64"
           (if host-mode
               INSTALL_LIB_HOME
               TARGET_LIB_HOME)) )

It has to be checked, whether this is needed for all linux (or other UNIXoid) systems.

[felix winkelmann]

(of course only for 64-bit systems)

[Jim Ursetto]

On my ubuntu install /usr/lib64 is a symlink to /usr/lib so it is not needed. I guess it would not hurt there, BUT looking at installed packages, they all install into "/usr/lib".

And when you build using ./configure, it always installs into /usr/lib.

Does Fedora really need to manually specify /usr/lib64? That seems stupid. What does /usr/lib point to on a 64-bit Fedora 12 system?

[sjamaan]

For NetBSD (and I *think* other BSDs as well), there is no such thing as "lib64". Everything is compiled for the target architecture, there's no 32-bit stuff at all. I don't remember seeing it on 64-bit Solaris for SPARC either. I think it's purely a Linuxism...

[sjamaan]

This should probably be marked invalid, unless the original poster comes with more info.

[felix winkelmann]

It should be sufficient to override LIBDIR at build-time. I will document this in the README.