Bug 79574 - statically linked binary is stripped when building rpm
statically linked binary is stripped when building rpm
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: rpm-build (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-13 11:45 EST by Marius Andreiana
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-23 16:54:04 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marius Andreiana 2002-12-13 11:45:14 EST
I'm trying to make a rpm on RedHat 8.0 with race (
http://race.sourceforge.net/ ). I've downloaded the compiled version.

Everything goes fine, but the final rpm has a binary executable of 92
bytes instead of the original 800k. The original race executable is
statically-linked ( ldd says it's not dynamic ) and it seems that on
brp-strip-comment-note step it gets 'stripped'.

If I put another binary, dynamically linked, it works fine.

I asked on redhat mailing list how could I convince rpm to leave the executable
as it is, got no answer in a month, so I'm filling this.

thanks
Comment 1 Jeff Johnson 2002-12-23 16:54:04 EST
You need to disable the stripping policies when building
your package:
    %define __spec_install_post :
will disable all post %install policies.

Note You need to log in before you can comment on or make changes to this bug.