Le sam 30/08/2003 à 19:07, Philip Blundell a écrit : > 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? Interesting point. I'm still experiencing the same issues with regxpcom and gcc -ldl, but I'm afraid there is no such explanation on my system. LD_LIBRARY_PATH is unset, and I have no other copies of glibc lying around. Regards, -- .''`. Josselin Mouette /\./\ : :' : josselin.mouette@ens-lyon.org `. `' joss@debian.org `- Debian GNU/Linux -- The power of freedom
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=