On Thu, 2003-08-28 at 12:31, Daniel Kraft wrote: > Just in case it helps somehow (otherwise ignore): I just had this same > error. The reason in my case was that I had (accidentally still) set > LD_LIBRARY_PATH to a path with libc6 2.3.1 (while having 2.3.2 > installed regularly) when calling gcc; the mix that results during > compilation seems to produce the undefined symbol above, then.
Seems like a plausible explanation. Jose, Josselin, Stefan: are you still experiencing this problem? If so, do you have LD_LIBRARY_PATH set in your environment? p. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
