Closed Bug 172788 Opened 23 years ago Closed 23 years ago

Phoenix-0.2 will not run because of missing libstdc++

Categories

(Firefox :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: tenthumbs, Assigned: bugzilla)

Details

I have a libstdc++ for every released gcc version from 2.7.2.3 up but the 0.2 tarball wants libstdc++-libc6.2-2.so.3. A little searching shows that this tarball was built with GCC: (GNU) 2.96 20000731 (Red Hat Linux 7.3 2.96-110) so you require a proprietary library not available to many people. Do you really want to do that? Haven't checked the nightlies yet.
What's proprietary about it? FWIW, this version is in Debian 3.0 as package "libstdc++2.10-glibc2.2". I would imagine that it's also in RH 8.0 and is installable on 7.3, theough presumably requiring the presence of libc6 2.2.4.
Maybe not proprietary, but certainly not universal. My brand-spanking-new Gentoo didn't have it, and I wasn't sure how to get it. So I had to copy it from an old RedHat install. Can't really speak as to what would be better to use (maybe /usr/lib/libstdc++-libc6.1-1.so.2), but I would gather that libstdc++-libc6.2-2.so.3 isn't ideal.
libstdc++-libc6.2-2.so.3 doesn't exist on RH 6.2 systems, either. I have not yet been able to successfully build phoenix on my 6.2 machine (it was fine on my 7.x), but I don't know if the two are related.
It's probably legal for me to download Redhat's compiler source and build it, assuming I wanted to. It's less clear to me that it's legitimate for me to download a single rpm and extract one file from it (assuming I can find the right package). Maybe I'm supposed to download the entire system. Who knows. I don't want to waste my time finding out. In any event, I would have to build rpm just for that. Debian's about the same. I would have to build dpkg from scratch. Limiting testing to only those who can find this library doesn't seem like a smart idea. Phoenix could easily find itself depending on a Redhat feature/bug. Besides, 2.96 is known to be very buggy. The glibc 2.2.x dependency is another issue that will cause problems.
FYI, regarding comment #4, you don't to download rpm or dpkg to unpack rpm/deb archives. Search google for rpm2targz (from Slackware) and deb2targz. The deb format can be extracted using "ar file.deb". Or send me an e-mail and I will mail them to you. Also, on my LinuxFromScratch system, libstdc++-libc6.2-2.so.3 is symlinked to libstdc++-3-libc6.2-2-2.10.0.so (from gcc-2.95.3 gnu release available at gcc.gnu.org). I did not create the link manually, it was automatically created during installation of gcc-2.95.3.
not a bug.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
Mass-verifying of old bugs.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.