From owner-freebsd-current Mon Feb 20 11:54:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id LAA05132 for current-outgoing; Mon, 20 Feb 1995 11:54:41 -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 LAA05126 for ; Mon, 20 Feb 1995 11:54:36 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id MAA07136; Mon, 20 Feb 1995 12:58:09 -0700 Date: Mon, 20 Feb 1995 12:58:09 -0700 From: Nate Williams Message-Id: <199502201958.MAA07136@trout.sri.MT.net> In-Reply-To: "Andrey A. Chernov, Black Mage" "Re: libcompat and shlib conflict" (Feb 20, 10:32pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Andrey A. Chernov, Black Mage" , current@freefall.cdrom.com Subject: Re: libcompat and shlib conflict Sender: current-owner@FreeBSD.org Precedence: bulk > >[ Two modules defining regerror ] > > >> Only one of those modules normally picked, not both. So, conflict > >> never happens. It is error in newest ld. > > >Umm, which modules gets picked? What if I want one module, and not the > >other? There *is* a conflict in that two modules in the same library > >are defining the same function. > > As I already say in previous letter, you can got conflict only > in one _very-very_rare_ case: > 1) You use regex module. > 2) You use regerror() before any regex functions. > All other cases handled correctly. It is *possible* that order of the library will change, and conflicts will occur if a new module is added, or an old one is removed. This is unacceptable behavior. We can not depend on the current ordering of the library being the same as it is now. Nate