Re: libxf86config.a can't be used by shared libraries
Sebastian Kügler <email@example.com> writes:
> On Sunday 06 February 2005 00:29, Goswin von Brederlow wrote:
>> Sebastian Kügler <firstname.lastname@example.org> writes:
>> > These are exactly identical files, hence the error from linking to either
>> > one is the same.
>> > miro.sebas(~): md5sum /usr/X11R6/lib/libxf86config*.a
>> > 27db885b4c292588c6c55ae951c85132 /usr/X11R6/lib/libxf86config.a
>> > 27db885b4c292588c6c55ae951c85132 /usr/X11R6/lib/libxf86config_pic.a
>> If you are nice you could download the i386 (or some other arch) debs
>> and check them. If they are also identical there report it as a
>> serious policy violation. If not then just a normal bug.
> Sure. This is the output on my i386 machine:
> 5b4617462ecf1b40b2185bdbf6a8bc86 /usr/X11R6/lib/libxf86config.a
> 5b4617462ecf1b40b2185bdbf6a8bc86 /usr/X11R6/lib/libxf86config_pic.a
> ... also identical. How do I proceed? I'm not quite experienced with that,
> so ... I.e. is there a bugzilla for the - I think still unofficial - pure64?
> Since I'm not encountering said problems on i386, I'm not sure it's a valid
> bug for bugs.debian.org.
Amd64 bugs (and this isn't even one since i386 has it too) are in the
normal BTS too. Just for amd64 specific things the severity should be
more moderate. Amd64 won't be in sarge so its bugs can't be RC.
So just run "reportbug -f /usr/X11R6/lib/libxf86config.a".