Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 20 Feb 1995 14:02:25 +0300
From:      "Andrey A. Chernov, Black Mage" <ache@astral.msk.su>
To:        current@freefall.cdrom.com, Nate Williams <nate@trout.sri.MT.net>
Subject:   Re: libcompat and shlib conflict
Message-ID:  <HG1R7Ilec2@astral.msk.su>
In-Reply-To: <199502200135.SAA29159@trout.sri.MT.net>; from Nate Williams at Sun, 19 Feb 1995 18:35:40 -0700
References:  <199502200135.SAA29159@trout.sri.MT.net>

next in thread | previous in thread | raw e-mail | index | archive | help
In message <199502200135.SAA29159@trout.sri.MT.net> Nate Williams
    writes:

>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.

Only one of those modules normally picked, not both. So, conflict
never happens. It is error in newest ld.
-- 
Andrey A. Chernov        : And I rest so composedly,  /Now, in my bed,
ache@astral.msk.su       : That any beholder  /Might fancy me dead -
FidoNet: 2:5020/230.3    : Might start at beholding me,  /Thinking me dead.
RELCOM Team,FreeBSD Team :         E.A.Poe         From "For Annie" 1849



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?HG1R7Ilec2>