Rebuilding RHEL3 libc.so from source

Michael ODonnell michael.odonnell at comcast.net
Fri Jul 13 17:17:57 EDT 2007



> you were rebuilding from source but getting a very
> different between the "official" Red Hat binaries and
> the ones you built yourself.  The article you linked to
> doesn't seem to have anything to do with that.  No?

I've modified my approach somewhat.  I had first naively
thought I could just explode the source RPM and run a
build that would leave all the resultant objs and libs
in the build area where I could (A) verify that they were
(effectively) the same as the currently installed pre-built
versions as a basic sanity check before (B) commencing the
classic edit-compile-crash cycle as I inflicted our local
instrumentation on the sources, working within that build area.

But for whatever reason (probably my unfamiliarity with RPM
technology, though nobody I've described my situation to
has told me I was doing anything wrong) the libc.so that I
ended up with seems to be wildly different from the pre-built
version(s) so I did not have confidence that I could start
making my local modifications from a known state.

My new approach is (will be) inspired by the one outlined
in that writeup, involving some sequence or cycle of:

 - Explode the RPM
 - Make local modifications.
 - Generate patch file reflecting those changes.
 - Mention that patch file in a local spec file derived
   from the one originally in the SRPM.
 - rpmbuild a new RPM from the SRPM
 - Install (or something) from that new RPM
 - crash
 


More information about the gnhlug-discuss mailing list