Thanks, Jim. Does that include both problems, or just the first one? I'm still stuck on the second problem, so any hints would be greatly appreciated!
janine On Jun 27, 2005, at 5:28 AM, Jim Davidson wrote:
Odd -- I caught this error just last night and fixed. I'll checkin later today or tomorrow. I think it's a more strict warning for gcc4.0 -- the code has technically worked for years :) -jim On Jun 26, 2005, at 8:46 PM, Janine Sisk wrote:I started out with this error: conn.c: In function ‘NsTclConnObjCmd’: conn.c:843: error: invalid lvalue in assignment Line 843 looks like this: connPtr = (Conn *) conn = itPtr->conn; The gcc version here is # gcc --version gcc (GCC) 4.0.0 20050519 (Red Hat 4.0.0-8) The exact same tarball was compiled a few weeks ago on an RHEL 4 system with no problems. The gcc version there is: # gcc --version gcc (GCC) 3.4.3 20050227 (Red Hat 3.4.3-22.1) As a test, I just went back to the RHEL system and touched conn.c. I got a warning instead of an error. conn.c: In function `NsTclConnObjCmd': conn.c:843: warning: use of cast expressions as lvalues is deprecated I checked the version in CVS and this line has not been changed. My C skills are a tad rusty but I went in and changed it to this, and it compiled under FC4: // connPtr = (Conn *) conn = itPtr->conn; conn = itPtr->conn; connPtr = (Conn *) conn; Is this valid? I thought I had saved the day, but I ended up stuck on this: libnsd.so: undefined reference to `pthread_kill_other_threads_np' That's in nsd/unix.c, in FatalSignalHandler: #ifdef __linux /* * LinuxThreads thread manager needs to kill all child threads * on fatal signals, else they get left behind as dead threads. * As of glibc 2.3 with NPTL, this should be a no-op. */ pthread_kill_other_threads_np(); #endif This system has glibc 2.3.5,, but I don't know if I have NPTL or not. The system on which this builds just fine has glibc 2.3.4. Suggestions? thanks, janine -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
