Marco:
FWIW, the Red Hat kernel RPMs effectively do the following when they
package kernel modules:
strip -g
This is done via the script:
/usr/lib/rpm/brp-strip
which is implicitly run on all executable files packaged in the RPM.
If you ensure that the module .ko file
005 11:24 PM
>To: linux-kernel@vger.kernel.org
>Subject: Stripping in module
>
>Hi,
>
>at the moment I am packaging a Linux module as an RPM archive.
>
>Therefor I would like to remove some of the not exported/needed
>symbols (like e.g. static functions or constants) from
Michael Tokarev wrote:
> Wakko Warner wrote:
> []
> > I would also be interested in this. For instance the AIC7xxx driver has
> > every PCI id in the module I think in the .modinfo section which is not
> > truely required once depmod has been run. []
>
> The .modinfo section, for example the PCI
Wakko Warner wrote:
[]
> I would also be interested in this. For instance the AIC7xxx driver has
> every PCI id in the module I think in the .modinfo section which is not
> truely required once depmod has been run. []
The .modinfo section, for example the PCI IDs, IS required for the
module to
Jan Engelhardt wrote:
> >What is the best way to do this with v2.6.
> >
> >I have tried e.g. to remove all symbols starting with "telos"
> >from the module like this (after kbuild):
> >
> > strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
>
> Yes, I'd also be interested in what
>What is the best way to do this with v2.6.
>
>I have tried e.g. to remove all symbols starting with "telos"
>from the module like this (after kbuild):
>
> strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
Yes, I'd also be interested in what sections can actually be stripped, if
Hi,
at the moment I am packaging a Linux module as an RPM archive.
Therefor I would like to remove some of the not exported/needed
symbols (like e.g. static functions or constants) from the
Linux module.
What is the best way to do this with v2.6.
I have tried e.g. to remove all symbols
Hi,
at the moment I am packaging a Linux module as an RPM archive.
Therefor I would like to remove some of the not exported/needed
symbols (like e.g. static functions or constants) from the
Linux module.
What is the best way to do this with v2.6.
I have tried e.g. to remove all symbols
What is the best way to do this with v2.6.
I have tried e.g. to remove all symbols starting with telos
from the module like this (after kbuild):
strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
Yes, I'd also be interested in what sections can actually be stripped, if any.
Jan Engelhardt wrote:
What is the best way to do this with v2.6.
I have tried e.g. to remove all symbols starting with telos
from the module like this (after kbuild):
strip -w -K '!telos*' -K 'telosi2c_usb_driver' telosi2c_linux.ko
Yes, I'd also be interested in what sections can
Wakko Warner wrote:
[]
I would also be interested in this. For instance the AIC7xxx driver has
every PCI id in the module I think in the .modinfo section which is not
truely required once depmod has been run. []
The .modinfo section, for example the PCI IDs, IS required for the
module to
Michael Tokarev wrote:
Wakko Warner wrote:
[]
I would also be interested in this. For instance the AIC7xxx driver has
every PCI id in the module I think in the .modinfo section which is not
truely required once depmod has been run. []
The .modinfo section, for example the PCI IDs, IS
To: linux-kernel@vger.kernel.org
Subject: Stripping in module
Hi,
at the moment I am packaging a Linux module as an RPM archive.
Therefor I would like to remove some of the not exported/needed
symbols (like e.g. static functions or constants) from the
Linux module.
What is the best way to do
Marco:
FWIW, the Red Hat kernel RPMs effectively do the following when they
package kernel modules:
strip -g module.ko
This is done via the script:
/usr/lib/rpm/brp-strip
which is implicitly run on all executable files packaged in the RPM.
If you ensure that the module
14 matches
Mail list logo
