RPM Upgrade

[David Relson]

At 09:40 AM 5/22/03, Andreas Metzler wrote:
>David Relson wrote:
> >> Wouldn't the binaries be humungous?  If I link bogofilter statically on
> >> linux/glibc-2.2.5 I get a size of 3,675,399 bytes.  Stripped, it's
> >> still 1,273,468.  That compares with 245,376 for the dynamically-linked
> >> version.
>
> > I agree.  Their size and attendant load time are two good reasons not to
> > use static linking.  However linking with glibc-2.3 creates problems for
> > people with glibc-2.2.  I _could_ create a bogofilter-static-0.13.0.
>
> > As indicated, I'd prefer a solution that allows me to dynamically link
> > against the older glibc.  The question is _how_ to do this.
>
>Sorry, I missed the beginning ot the thread, but I assume the problem
>is that somebody using RedHatXX wants to generate packages for
>RedHat(XX-2)?
>
>I'd suggest doing a minimal install of the old version in separate
>partition, move its content to /old/rh(XX-2) and use
>chroot /old/rh(XX-2)
>to build packages for the old system.
>                  cu andreas

Andreas,

Close, but not quite.  The problem is that have upgraded my Mandrake 9.0 
from glibc-2.2 to glibc-2.3.  This results in a dependency in 
bogofilter...i586.rpm that prevents it loading/running on glibc-2.2 
systems.  I still have copies of glibc-2.2 available.  The big question is 
how to make "make rpm" use them.  I've experimented and found that using 
"make LDFLAGS=xxx rpm" I can modify the parameters used when linking the 
executables.  So the question become "how does one tell ld to build an ELF 
executable with an older glibc?"

David