[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#511650: marked as done (libxdmcp-dev is missing libXdmcp.la on amd64)



Your message dated Fri, 16 Jan 2009 01:17:01 +0100
with message-id <1232065021.7083.5.camel@radis.liafa.jussieu.fr>
and subject line Re: Bug#511650: libxdmcp-dev is missing libXdmcp.la on amd64
has caused the Debian Bug report #511650,
regarding libxdmcp-dev is missing libXdmcp.la on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
511650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511650
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libxdmcp-dev
Version: 1.3-16

When I try to link programs (like libXv), they fail on trying to link
against /usr/lib64/libXdmcp.la. This bug exists at least on Lenny and
prevents you from compiling xorg server so the file should be added to
the package. I've heard from an i386 user that it exists on the i386
version of the package.

I'm using Debian Lenny on an amd64 system with libc6_2.7-16.



--- End Message ---
--- Begin Message ---
On Wed, 2009-01-14 at 14:21 +0200, Seppo Yli-Olli wrote:
> I was attempting to install a newer version of X.org suite (read: a
> much more up-to-date version from git trees) on the side of the old one
> into /usr/local. While installing libXv, I ran into linker errors when
> trying to link against libXdcmp and it complained about the lack of
> libXdcmp.la. I suspect you could work around the problem by telling it
> not to use libtool and tell it the library paths directly but the
> default behaviour for libXv compiling seemed to require the existence
> of the file. If the build log is relevant, I can attempt to re-obtain
> it.

I suspect one of your locally installed libs has a reference to a
libXdmcp.la, but it could only get such a reference if you installed
libXdmcp locally, because the package has never done so.  You could
remove all the .la files in /usr/local/lib as a workaround.  In any case
I'm closing this bug since I'm pretty sure this isn't due to the
libxdmcp packages.

Cheers,
Julien


--- End Message ---

Reply to: