Date: Thu, 12 Feb 2015 18:33:44 +0100 From: Baptiste Daroussin <bapt@freebsd.org> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: current@freebsd.org Subject: Re: /usr/lib/private and static linking? Message-ID: <20150212173344.GH29891@ivaldir.etoilebsd.net> In-Reply-To: <alpine.GSO.1.10.1502121158050.3953@multics.mit.edu> References: <alpine.GSO.1.10.1502121158050.3953@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--cTOVv4IlZiYEQ88H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 12, 2015 at 12:01:41PM -0500, Benjamin Kaduk wrote: > I have a machine running -current from December (r276480), and trying to > link with "cc -static [...] $(krb5-config --libs)" yields a linker error: >=20 > /usr/lib/libkrb5.a(kcm.o): In function `krb5_kcm_call': > /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/kcm/kcm.c= :(.text+0x10e): > undefined reference to `heim_ipc_init_context' > /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/kcm/kcm.c= :(.text+0x162): > undefined reference to `heim_ipc_call' >=20 > Should I update my system? Is static linking against libraries which > consume libraries in /usr/lib/private no longer supported? >=20 > Thanks, >=20 In the last modification of the private libraries we removed everything whi= ch is development related, maybe the .a files should be kept to allow linking to a public library which consumes a private one. Best regards, Bapt --cTOVv4IlZiYEQ88H Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlTc4/gACgkQ8kTtMUmk6EyTqgCgqyr3DR2dZkQgBCLtD8o2VFBV jLUAn3JtNQLejbBCyJkkPNcdOkauvo/M =AONJ -----END PGP SIGNATURE----- --cTOVv4IlZiYEQ88H--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150212173344.GH29891>