"Juliano Morais Barbosa" <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Mon, 03 Jul 2006 16:24:41 -0300:
> When I try updating kdm I receive this message. First, you are thread hijacking. You replied with a KDM error to a thread about serial ATA. It's an entirely different subject. Please start an entirely different thread. (New message, not reply.) Second, normally emerge errors like this should be filed as bugs, not posted to the mailinglist/newsgroup. An exception would be if for some reason you suspect it's due to an unrelated problem on your system, with this as part of the evidence, or if it's otherwise a problem that you don't think is limited to that package or that could be serious enough that others need to know about it. Meanwhile, altho I'm running unstable ~amd64, and thus already have kdm-3.5.3-r2 merged, and am running gcc-4.1.1, I did just do a quick test of kdm-3.5.2-r1, doing the unpack/compile/fake-install steps using "ebuild /$PORTDIR/kde-base/kdm/kdm-3.5.2-r1.ebuild install", and it worked just fine, no errors (in particular not the -fPIC error you got), so it /can/ work. FWIW, -fPIC errors aren't unusual on AMD64, where libraries need compiled with -fPIC or they won't work. However, most Gentoo packages have already fixed the problem if it existed, and it would cause problems for everyone on amd64 compiling the package if that were the real problem. Therefore, I think you have some other problem, perhaps a CXXFLAGS issue or something else on your system that caused the error -- which it wrongly called an -fPIC error for some reason. The error would appear to be related to the fact that it's using libXdmcp.a, the static library, instead of libXdmcp.so, the shared object, which would explain the -fPIC error since the static libs can't be linked that way. Why it's using the wrong one, I'm not sure, but it's something that will probably need to be sorted out on a bug, as the Gentoo/KDE folks will then take a look at it, and probably know enough more about the KDE configure and library scan process to figure out why it's trying to build against the static lib instead of the shared-object lib. One thing you can check, however. You DO have a libXdmcp.so, right? Here's the files I have as part of the libXdmcp package: $equery f libXdmcp [ Searching for packages matching libXdmcp... ] * Contents of x11-libs/libXdmcp-1.0.1: /usr /usr/include /usr/include/X11 /usr/include/X11/Xdmcp.h /usr/lib64 /usr/lib64/libXdmcp.a /usr/lib64/libXdmcp.la /usr/lib64/libXdmcp.so -> libXdmcp.so.6.0.0 /usr/lib64/libXdmcp.so.6 -> libXdmcp.so.6.0.0 /usr/lib64/libXdmcp.so.6.0.0 /usr/lib64/pkgconfig /usr/lib64/pkgconfig/xdmcp.pc If you are missing libXdmcp.so.6.0.0 or its symlinks, that would explain your problem. In that case, you'd need to remerge it. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
