uppc kmod installation problem

Kostik Belousov kostikbel at gmail.com
Fri Aug 3 12:43:59 UTC 2007


On Fri, Aug 03, 2007 at 03:23:18PM +0300, Andriy Gapon wrote:
> on 02/08/2007 15:46 Kostik Belousov said the following:
> > On Wed, Aug 01, 2007 at 07:40:53PM +0300, Andriy Gapon wrote:
> >> on 26/07/2007 17:13 Andriy Gapon said the following:
> >>> It seems that installation action of uppc-kmod port (do-install target)
> >>> uses incorrect tool to put uppc.ko in its destination. It seems that the
> >>> tool (${INSTALL_PROGRAM}) corrupts the .ko, so that it is not a valid
> >>> kernel module anymore. If I put uppc.ko into /boot/kernel and do kldxref
> >>> then kldxref complains about missing symbol table in uppc.ko and dumps
> >>> core. If the module is loaded then it crashes my system.
> >>>
> >>> On the other hand, if I simply copy uppc.ko from work directory then it
> >>> works ok.
> >> [snip]
> >>> Some system info:
> >>> FreeBSD 6.2-RELEASE-p3 amd64
> >> [snip]
> >>
> >> This problem seems to be the same as the one described here:
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=100703
> >>
> >> There seems to be something special about amd64, kernel modules and
> >> 'install -s' / strip.
> > You cannot strip kernel modules on amd64, because modules are elf object
> > files, as opposed to shared objects on all other archs. Strip strips the
> > object file symbol table, that is used by the static linker and in-kernel
> > linker on amd64. On the other hand, shared object contains also a dynamic
> > symbol table, that is not stripped and used by in-kernel linker on !amd64.
> 
> Kostik,
> 
> would you be comfortable to apply a patch from the PR mentioned above
> (or something similar) to palm/uppc-kmod port ? Current maintainer for
> the port is ports@,

I am not a port committer.

Also, some time ago there was a conversation about some unification of
install procedure for kernel modules. In particular, I asked about some
common location for modules.

I do not know whether somebody actually start the work, but, if yes,
this problem shall be solved among other.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20070803/8622041c/attachment.pgp


More information about the freebsd-ports mailing list