[Pkg-xen-devel] Unstripped stuff
Guido Trotter
ultrotter at debian.org
Mon Feb 20 18:47:54 UTC 2006
Hi!
I was running lintian on our package... Among the copious errors and warnings
there are:
W: xen-utils: manpage-has-errors-from-man usr/share/man/man1/xm.1.gz 668: warning: can't find numbered character 160
Should we try to fix this, perhaps?
E: xen-hypervisor-pae: unstripped-binary-or-object ./boot/xen_pae-syms-3.0.1
E: xen-hypervisor: unstripped-binary-or-object ./boot/xen-syms-3.0.1
What are these syms files? Are they useful? Should we ship them? Can we strip
them?
W: libxen3.0: package-name-doesnt-match-sonames libxenguest3.0 libxenctrl3.0
???
E: libxen3.0: unstripped-binary-or-object ./usr/lib/xen/boot/vmxloader
E: libxen3.0: statically-linked-binary ./usr/lib/xen/boot/vmxloader
vmxloader is the thing needed to boot unmodified guests with processor support,
right? So I guess it's statically linked because it cannot rely on having
libraries available when it runs... How about stripping? Can we go ahead? ;)
E: libxen-dev: no-shlibs-control-file usr/lib/libxenstore.so
W: libxen-dev: package-name-doesnt-match-sonames libxenstore
This is interesting... It seems libxenstore.so rather than linking to the
library IS the library... this screws up our -dev package, and probably our
policy compliance too... Can we fix this? Do we have to give a soname to the
library and enter into other library black magic? help! ;)
Guido
More information about the Pkg-xen-devel
mailing list