Top White Papers
LinuxPlanet: .comment: British Beer, American Politics, and glibc-2.2Nov 22, 2000, 13:32 (12 Talkback[s])
(Other stories by Dennis E. Powell)
"Some time ago I was told that there was a gcc flag that would optimize code for use on my K6-2 machine. I tried it and it didn't work, but I was using EGCS-1.1.2. Then, beginning about the first of the month, I was hitting all kinds of errors when I tried to compile the KDE2 CVS tree. EGCS is getting a little long in the tooth, anyway, so I thought I'd upgrade. Easiest way, seemed to me, was to grab the RPMs from Caldera's Linux Technology Preview directory, on their ftp site. I did that and was disappointed when the RPMs wouldn't install -- the failed dependency was glibc-2.2."
"There were no glibc-2.2 RPMs in the LTP directory. In fact, far as I knew, there was no actual glibc-2.2 at all. A visit to the gnu site taught me that glibc-2.2 had just been released, and the source could be downloaded."
"Now. It was not long ago that Linus suggested on the kernel mailing list that people who compile their own glibc probably have a screw loose. And I've compiled earlier versions of gcc myself several times in the past, uneventfully, and know that it can be done against glibc-2.1. The sensible thing, then, would have been to download the source for gcc-2.95 and compile it. But, as in Florida, things were following their own twisted path here. I had the gcc-2.95 RPMs. They required glibc-2.2. If I were to get glibc-2.2 I would have to build it myself. Case closed."
0 Talkback[s] (click to add your comment)