Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Feb 1995 22:34:04 -0700
From:      Nate Williams <nate@trout.sri.MT.net>
To:        "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
Cc:        current@freefall.cdrom.com
Subject:   Re: libcompat and shlib conflict
Message-ID:  <199502200534.WAA01333@trout.sri.MT.net>
In-Reply-To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> "Re: libcompat and shlib conflict" (Feb 19,  7:59pm)

next in thread | previous in thread | raw e-mail | index | archive | help
[ 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




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