From owner-freebsd-current Sun Feb 19 23:44:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id XAA01070 for current-outgoing; Sun, 19 Feb 1995 23:44:27 -0800 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id XAA01061 for ; Sun, 19 Feb 1995 23:44:23 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id XAA18530; Sun, 19 Feb 1995 23:43:31 -0800 From: "Rodney W. Grimes" Message-Id: <199502200743.XAA18530@gndrsh.aac.dev.com> Subject: Re: libcompat and shlib conflict To: nate@trout.sri.MT.net (Nate Williams) Date: Sun, 19 Feb 1995 23:43:31 -0800 (PST) Cc: current@freefall.cdrom.com In-Reply-To: <199502200534.WAA01333@trout.sri.MT.net> from "Nate Williams" at Feb 19, 95 10:34:04 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1716 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? I am not much of an export on this issue, but we defanitly need to do something about cleaning it up. Another anomoly caused by this is: hookturn# man -k regerr regcomp(3), regexec(3), regerror(3), regfree(3) - regular-expression library regcomp(3), regexec(3), regsub(3), regerror(3) - regular expression handlers I can get the first man page for sure with `man regfree' and the second one with `man regsub' but I am not sure where the links for the other ones point :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD