This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: glibc 2.2 in CVS and gcc problem.
- To: "H . J . Lu" <hjl at lucon dot org>
- Subject: Re: glibc 2.2 in CVS and gcc problem.
- From: "Gabor Z. Papp" <gzp at gzp dot org dot hu>
- Date: Mon, 19 Mar 2001 18:24:07 +0100
- Cc: GNU C Library <libc-alpha at sourceware dot cygnus dot com>
- Organization: gzp
- References: <20010318223003.A1333@gzp2.gzp.hu> <20010318133852.A25902@lucon.org> <20010318224501.A1094@gzp2.gzp.hu> <20010318164100.A13028@lucon.org> <20010318164805.A22420@lucon.org> <20010319081756.A323@gzp2.gzp.hu> <20010319084021.A11139@lucon.org>
* "H . J . Lu" <hjl@lucon.org>:
| > | http://gcc.gnu.org/ml/gcc-patches/2001-03/msg01187.html
| >
| > This is for which version of gcc?
|
| If you ask me, the current gcc in CVS is broken under Linux. I will
| recommend
|
| 1. gcc from RedHat Rawhide. Or
| 2. gcc 2.95.3 + the patch above.
Finally I manually patched 2.95.3 with the above patch, and
glibc now plays fine with atexit, but I have this weird
problem:
PAM unable to dlopen(/usr/lib/security/pam_rootok.so)
PAM [dlerror: libgcc_s.so.0: cannot load shared object file: No such file or directory]
And several apps have this problem. I'm wondering what is
this libgcc_s.so.0 and why apps asking for it.
Anybody know the solution?