> The first step is to reproduce the problem outside of rpmbuild:
> /usr/bin/strip /home/mydir/RPM/BinaryName
> The next step is to identify the format of BinaryName. One way is
> file /home/mydir/RPM/BinaryName
> The file should be ELF format. This command will display what is in
> the ELF file:
> readelf -a /home/mydir/RPM/BinaryName
> Additional information is needed to diagnose your problem and suggest
> best solution.
> Meanwhile, if you simply edit /usr/lib/rpm/redhat/brp-strip, and add
> exit 0
> at the top, then rpmbuild will not attempt stripping the file. One can
> achieve the same effect by changing a macro to not attempt running
> But putting a band-aid, by not attempting stripping, to avoid the
> problem solves nothing.
> There is also eu-strip that can be used instead of /usr/bin/strip.
> eu-strip (from elfutils) is often smarter
> about ELF internals.
Jeff, thank you very much for your reply! I got more information today
that helps better formulate my question.
We do have to include several binaries that are not stripped in our RPM
packages (I confirmed via "file <binary>" that the problem files are not
stripped). Therefore, my question should have been, is there a way to
configure RPM to not run strip at all? The band-aid methods above will
work, but we'd prefer not changing the RPM distribution code if at all
Thanks again for your assistance!
Received on Tue Apr 8 03:49:38 2008