Date: Fri, 3 Aug 2007 15:43:44 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Andriy Gapon <avg@icyb.net.ua> Cc: Sam Lawrance <boris@brooknet.com.au>, freebsd-ports@freebsd.org Subject: Re: uppc kmod installation problem Message-ID: <20070803124344.GL2738@deviant.kiev.zoral.com.ua> In-Reply-To: <46B31E36.2030305@icyb.net.ua> References: <46A8AC15.4080509@icyb.net.ua> <46B0B795.5070106@icyb.net.ua> <20070802124603.GC2738@deviant.kiev.zoral.com.ua> <46B31E36.2030305@icyb.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
--00hq2S6J2Jlg6EbK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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 targe=
t)
> >>> 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 kldx=
ref
> >>> 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=3D100703
> >>
> >> 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-kern=
el
> > linker on amd64. On the other hand, shared object contains also a dynam=
ic
> > symbol table, that is not stripped and used by in-kernel linker on !amd=
64.
>=20
> Kostik,
>=20
> 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.
--00hq2S6J2Jlg6EbK
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)
iD8DBQFGsyL/C3+MBN1Mb4gRAtmkAJ95dPluLJA1UoAhITKrQG3PZnOU2wCeN+hx
uIeXoc8i1mD8A2R8BjX6Ob8=
=gsew
-----END PGP SIGNATURE-----
--00hq2S6J2Jlg6EbK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070803124344.GL2738>