[Mono-bugs] [Bug 708392] New: installed components sometimes go under /usr/lib/mono and other times under /usr/lib64 mono

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue Jul 26 11:59:31 EDT 2011



           Summary: installed components sometimes go under /usr/lib/mono
                    and other times under /usr/lib64 mono
    Classification: Mono
           Product: Mono: Tools
           Version: 2.10.x
          Platform: x86-64
        OS/Version: Linux
            Status: NEW
          Severity: Minor
          Priority: P5 - None
         Component: tools
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: g.trentalancia at libero.it
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:5.0.1) Gecko/20110719

Possibly because of a trivial bug in the configure script,
dbus-sharp-glib-0.5.0 from http://www.github.com/mono/dbus-sharp does not look
in lib64 dependencies and it fails to build because it only searches under

There is a lot of confusion about this in other packages as well when they are
build on x86 64-bit platforms !

Despite always passing --libdir=/usr/lib64 to configure, here is the actual

# ls /usr/lib/mono
1.0  3.5  compat-2.0  gecko-sharp-2.0  gtk-sharp-2.0              monodoc      
2.0  4.0  gac         gmime-sharp-2.6  mono-configuration-crypto  webkit-sharp 

# ls /usr/lib64/mono
dbus-sharp-1.0  dbus-sharp-glib-1.0  gac  mono-addins  xbuild

so that now I have to manually move anything to one directory under /usr/lib64
and symlink the other one.

There is something to enhance here, I suppose...

Reproducible: Always

Steps to Reproduce:
1. pass --libdir=/usr/lib64 to the configure script
Actual Results:  
sometimes components are installed under /usr/lib instead of /usr/lib64 as
explicitly required.

Expected Results:  
configure should always honor --libdir

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list