X-pop3-spooler: POP3MAIL 2.1.0 b 4 980420 -bs- X-Authentication-Warning: basis.Desk.nl: listserv set sender to owner-pgcc-list AT basis DOT desk DOT nl using -f Date: Wed, 25 Nov 1998 05:30:46 -0600 (CST) From: ksparger X-Sender: ksparger AT vaevictis To: pgcc-list AT desk DOT nl cc: ksparger AT concentric DOT net Subject: Possible bug in glibc binary? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Marc Lehmann Status: RO X-Status: A Content-Length: 2279 Lines: 44 I feel rather like an ass for writing this, because I have a nagging feeling I just screwed up the installation somehow, or that the bug itself is really with the glibc I installed, but frankly, I find that this is the most likely source for aid that I am currently aware of, so I ask for your help first. I had been running PGCC under libc5 for a decent amount of time without any problems of import, but I got brave and decided to try and upgrade to glibc2, and I'm now regretting it :) I'm using the slackware 3.6 distribution of glibc2 (version 2.0.7, it appears to be), so if you know of any bugs in it, that may very well be the source of my problems. The most obvious example of the incorrect behaviour pgcc is generating problems for me is the fact that ircII 4.4 compiled under the libc6/pgcc libc6 combination reports the time to be exactly 6 hours LATER than it really is (no, this is not a system problem, because programs such as date, compiled for libc5 under the libc5 pgcc work fine) Problems extend to any complex program that I use, but this is the only one with an example that I have been able to narrow down to a specific part of the program. Further, until I installed a link /usr/local/pgcc/lib/gcc-lib to /usr/lib/gcc-lib, I received the following error whenever attempting to compile any program which included limit.h: In file included from /usr/include/sys/param.h:23, from ../include/irc.h:53, from alias.c:15: /usr/include/limits.h:46: No include path in which to find limits.h Is this normal behaviour? When I set the link, pgcc then APPEARED to compile programs properly, even though it didn't. So, that's a potential problem (perhaps it thinks it's getting the right header files, but really isn't), maybe I set the link incorrectly. I assumed (yes, I know, assumptions are a bad thing) that it simply didn't know where to look for it's own limits.h, so I ran strings on the gcc binary, and put a link to the real location of gcc-lib in a place it seemed that it may have been looking. Thanks your time, and please be gentle if I did something stupid ;) Kyle Sparger (ps, if any replies are sent to the pgcc list, please keep me in the cc, as I am currently not subscribed to the pgcc mailing list)