[20164] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: [PATCH] Use PKG_CHECK_MODULES to system library com_err

daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Sep 8 15:25:19 2020

To: <anonymous.maarten@gmail.com>, <krbdev@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <b2d62ed0-8f97-7329-3b33-ce7e642b19b1@mit.edu>
Date: Tue, 8 Sep 2020 15:24:53 -0400
MIME-Version: 1.0
In-Reply-To: <20200903192535.14878-1-anonymous.maarten@gmail.com>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu

On 9/3/20 3:25 PM, anonymous.maarten@gmail.com wrote:
> When having a static com_err system library, linking to this static
> library fails because of missing symbols. The system com_err needs to
> link to -lrt too (when using com_err from e2fsutils).

I created a pull request for the patch at
https://github.com/krb5/krb5/pull/1111 .

There are a couple of things I am unclear on:

* On my systems, "pkg-config --libs com_err" displays "-lcom_err".  If I
add "--static", "-lpthreads" is also displayed.  I don't know where the
librt dependency is needed.

* In the pkg.m4 modules we use, there is a PKG_CHECK_MODULES_STATIC
macro, but we don't currently use it, and nothing else seems to add
--static to the pkg-config options.  In your environment, does
"pkg-config --libs com_err" display library dependencies even without
the --static option?
_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post