From owner-freebsd-current Sun Feb 19 21:30:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id VAA29333 for current-outgoing; Sun, 19 Feb 1995 21:30:35 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id VAA29327 for ; Sun, 19 Feb 1995 21:30:30 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id WAA01333; Sun, 19 Feb 1995 22:34:04 -0700 Date: Sun, 19 Feb 1995 22:34:04 -0700 From: Nate Williams Message-Id: <199502200534.WAA01333@trout.sri.MT.net> In-Reply-To: "Rodney W. Grimes" "Re: libcompat and shlib conflict" (Feb 19, 7:59pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" Subject: Re: libcompat and shlib conflict Cc: current@freefall.cdrom.com Sender: current-owner@FreeBSD.org Precedence: bulk [ Multiple definitions of regerror() in libcompat ] > > However, the newest ld is giving me errors trying to build > > libcompat (correctly so) with multiple definitions of the function > > regerror(), which is defined in both libcompat/4.3/regex.c and > > libcompat/regexp/regerror.c. Does anyone know what should be done here? NetBSD just ignores the problem by not making a shared library. The problem still exists though since at link time I'm not sure which version of regerror() will get used, and a quick perusal of the code makes it obvious that they can't be combined into one function. I'm sure the function that is first found would be the first function linked in, but that could change depending on the other functions in the library and tsort. We either need to completely remove one of the functions, or ignore the problem and only build a static library which avoids the error at the cost of later problems in code. (But, I suppose folks shouldn't be using the compat libraries anyway, right. :( ) What say you? Nate