Date: Thu, 27 Jul 1995 11:20:36 -0700 From: "Amancio Hasty Jr." <hasty@rah.star-gate.com> To: nate@sneezy.sri.com (Nate Williams) Cc: hackers@FreeBSD.org Subject: Re: ld.so: ivs: libcompat.so.2.0: Undefined error: 0 Message-ID: <199507271820.LAA07766@rah.star-gate.com> In-Reply-To: Your message of "Thu, 27 Jul 1995 08:46:32 MDT." <199507271446.IAA01203@rocky.sri.MT.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> Nate Williams said: > > That is why it must be compiled shared. A *bug* in the loader prior to > 2.0.5 allowed it to build shlibs with symbols that had multiple > definitions. So, the symbol which was used depended on it's position in > the build at creation time. In all honesty, this problem still exists > with the static libraries as well, but since the loader isn't aware of > multiply defined symbols because each .o file is unique it's not seen. > > The solution is to remove the dependency of libcompat in whatever > program requires libcompat and send the changes back to the maintainer. > Does mwm depend on libcompat? Tnks, Amancio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507271820.LAA07766>