On Tue, 25 Apr 2006 22:50:28 +0100, Paul wrote: > Hi, > > > > The problem is this. When you compile mono from source, if you say > > > --libdir=/usr/lib64, everything goes into /usr/lib64 happily and the .pc > > > files go into /usr/lib64/pkgconfig. However, when compiling via a spec > > > file, even if you define libdir as /usr/lib, bits move > > > to /usr/lib64/pkgconfig and it doesn't matter what is passed in the % > > > configure line. Then that is a packaging bug. > > What are the Makefile lines responsible for installing the misplaced > > files? Perhaps there's a make macro you can set to put them in the right > > place? > > The problem is that the configure file is picking up the packages from > whereever their .pc files are. For example, gtksourceview-sharp picks up > gtksharp. gtksharp has it's pc file in /usr/lib irrespective of the > architecture (as /usr/lib/pkgconfig/../..). The paths looks to be taken > relative to where it finds the pkgconfig files. Then that is a packaging bug, too. Or broken by design. > Problem comes if you're using a 64 bit machine. The .pc files end up > in /usr/lib64 as that's where pkgconfig says to put things. However, the > package expects things to be in /usr/lib/pkgconfig > > Is there a way to override pkgconfig so that it always goes > to /usr/lib/pkgconfig. Failing that, my finding here supports my bug > report that mono is packaged incorrectly for x86_64. At run-time? You could override $PKG_CONFIG_PATH and insert /usr/lib/pkgconfig at the beginning, but that would only work around more fundamental problems. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
