> I'm not sure how to force a dynamically linked program to use compat-glibc > instead of the default glibc...maybe some convoluted chroot trickery?
I think that's the purpose of the compat-glibc package. I think you tell it with some environment variable. The wonders of dynamic linking... > > In the meantime, I found an old source rpm for glibc 2.5-65. As soon as a > I > finish building and installing it I'll let everyone know how it goes. If > it > works, I'll post an ftp link to the rebuilt rpm's. Very cool. John > > -Alex > > On Fri, Aug 10, 2012 at 9:00 AM, John Ford <[email protected]> wrote: > >> > I've been trying to get all the mssge toolflow stuff running on a new >> SL >> > 5.8 machine. Everything works except that compilation fails at xst >> > synthesis for even the simplest designs with a lot of complaints from >> > glibc. >> > >> > A while back there was a thread describing some very similar issues. I >> > believe it was concluded that ISE 11 doesn't work with newer versions >> of >> > glibc. The NRAO wiki seems to agree, saying that the latest glibc that >> > works is 2.5-65 (see >> > https://safe.nrao.edu/wiki/bin/view/Ccs/CasperReferenceGuide) >> > >> > The trouble is, the oldest glibc package I can find anywhere is >> 2.5-81, >> > which I tried to no avail. Does anyone have any advice for getting all >> the >> > requisite 2.5-65 rpms or building release 65? >> >> One of our linux folks wondered if you tried the compat-glibc package? >> I >> think it allows you to install multiple glibc versions at once. >> >> John >> >> > >> > Thanks, >> > Alex >> > >> >> >> >
