Behold, Dave Jones <davej@xxxxxxxxxx> hath decreed:
> On Mon, 2004-06-07 at 13:50, Aaron Gaudio wrote:
>
> > > If you don't care about it you can unset CONFIG_DEBUG_INFO
> > > and it won't generate it.
> > Is there a convenient way to manually strip the debug info from
> > the files after they are compiled? In other words, how does rpm
> > do it?
>
> You know, I'm not actually sure.
> Taking a peek inside the .spec file, there's this gem..
>
> # mark modules executable so that strip-to-file can strip them
> find $RPM_BUILD_ROOT/lib/modules/$KernelVer -name "*.ko" -type f |
> xargs chmod u+x
>
> Which seems to be something magical that rpm invokes.
>
Not very magical: it is just changing the permissions on all
the kernel modules to be executable by their owner.
The comment is helpful though, because it seems to imply that
rpm is just using some option to or version of the strip command.
--
prothonotar at tarnation.dyndns.org
"Every man is a mob, a chain gang of idiots."
- Jonathan Nolan, /Memento Mori/
Attachment:
pgpg5aTa6JS9E.pgp
Description: PGP signature
