From owner-freebsd-current Sun Feb 19 20:00:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA28059 for current-outgoing; Sun, 19 Feb 1995 20:00:21 -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 UAA28050 for ; Sun, 19 Feb 1995 20:00:14 -0800 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id TAA18198; Sun, 19 Feb 1995 19:59:21 -0800 From: "Rodney W. Grimes" Message-Id: <199502200359.TAA18198@gndrsh.aac.dev.com> Subject: Re: libcompat and shlib conflict To: nate@trout.sri.MT.net (Nate Williams) Date: Sun, 19 Feb 1995 19:59:21 -0800 (PST) Cc: current@freefall.cdrom.com In-Reply-To: <199502200135.SAA29159@trout.sri.MT.net> from "Nate Williams" at Feb 19, 95 06:35:40 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1100 Sender: current-owner@FreeBSD.org Precedence: bulk > > Umm, forgive me if this sounds silly, but does the old shared library > loader NOT complain about multiply defined symbols when it tries to > build libcompat? The reason I'm asking is that I'm attempting to bring > in the newest ld (once more) to hopefully finish off the shilb code > merge. 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. > > I suspect the older ld does not have problems, but as I'm a ways into > the test phase, I'd rather not back out the changes I've made to make > sure, but rather move forward and figure out how to resolve this > conflict. I just rebuilt it and see no errors or no warnings from the build of libcompat :-(, this is on 2.0 current as of 4:00 this afternoon :-(. > > Any hints or suggestions are welcome, Sorry :-( -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD