It seems that "make install" does not install libXxf86dga.so.1 Steps to reproduce: 1. Download and install SuSE 9.1 in a VMware VM 2. Grab Xorg trunk 3. Compile it: % make World 2>&1 | tee -a buildlog.log 4. Install it % make install % make install.man 5. Run xdpyinfo Result: % xdpyinfo xdpyinfo: error while loading shared libraries: libXxf86dga.so.1: cannot open shared object file: No such file or directory Same problems occurs for libXxf86misc.so.1 Expected result: Working xdpyinfo
Weired. Copying the libs to /usr/X11R6/lib/ does not help, only xorg_cvs/xc # cp ./exports/lib/libXxf86dga.so.1 /usr/X11R6/lib/. xorg_cvs/xc # cp ./exports/lib/libXxf86misc.so.1 /usr/X11R6/lib/. cures the problem. Maybe the install process only screws up the linker search path (e.g. -L<path> -R<path> ...) ... ;-(
Egbert/sndirsch: Can you take this bug, please ?
I can't reproduce this. When I build xorg 6.7.0 or CVS head as of Tuesday the 3rd of August, I get these files once the build is complete. Can you confirm wether this problem still exists or is fixed?
I'm sorry, but I cannot reproduce this problem with current CVS (04-08-03).
This happened for me also using 6.7.0 on mandrake10; Running ldconfig manually (and making sure the x11r6 lib is in your ld.so.conf path first) fixes this issue. So it is not that it doesn't get installed. (In reply to comment #0) > It seems that "make install" does not install libXxf86dga.so.1 > > Steps to reproduce: > 1. Download and install SuSE 9.1 in a VMware VM > 2. Grab Xorg trunk > 3. Compile it: > % make World 2>&1 | tee -a buildlog.log > 4. Install it > % make install > % make install.man > 5. Run xdpyinfo > > Result: > % xdpyinfo > xdpyinfo: error while loading shared libraries: libXxf86dga.so.1: cannot open > shared object file: No such file or directory > > Same problems occurs for libXxf86misc.so.1 > > Expected result: > Working xdpyinfo
unable to reproduce this with HEAD, closing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.