From owner-freebsd-ports@FreeBSD.ORG Wed Feb 5 05:48:39 2014 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2349860C for ; Wed, 5 Feb 2014 05:48:39 +0000 (UTC) Received: from vps.rulingia.com (vps.rulingia.com [103.243.244.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6AF9410F5 for ; Wed, 5 Feb 2014 05:48:37 +0000 (UTC) Received: from server.rulingia.com (c220-239-239-176.belrs5.nsw.optusnet.com.au [220.239.239.176]) by vps.rulingia.com (8.14.7/8.14.7) with ESMTP id s155fm4q009466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Feb 2014 16:41:49 +1100 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.7/8.14.7) with ESMTP id s155fhH5013285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Feb 2014 16:41:43 +1100 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.7/8.14.7/Submit) id s155fhe6013284; Wed, 5 Feb 2014 16:41:43 +1100 (EST) (envelope-from peter) Date: Wed, 5 Feb 2014 16:41:42 +1100 From: Peter Jeremy To: "Montgomery-Smith, Stephen" Subject: Re: Solved - was: Problems with linking on FreeBSD-10 Message-ID: <20140205054142.GB12626@server.rulingia.com> References: <52EAEC1D.9040502@missouri.edu> <20140131132504.GZ24664@kib.kiev.ua> <52EBDDDC.7000702@missouri.edu> <52F15DDA.3000101@missouri.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <52F15DDA.3000101@missouri.edu> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.22 (2013-10-16) Cc: Konstantin Belousov , FreeBSD Ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Feb 2014 05:48:39 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2014-Feb-04 21:38:42 +0000, "Montgomery-Smith, Stephen" wrote: >/usr/home/stephen/sage/work/sage-6.0/local/lib contained >libreadline.so.6. But for ld to work, it also had to contain a link >libreadline.so->libreadline.so.6. > >(Is this sort of behavior documented anywhere?) I think it's sort-of communal mind knowlegde rather than being specifically written down: If the loader sees '-lfoo', it looks for libfoo.so or libfoo= =2Ea in locations specified by -L. If it finds libfoo.so then it will read at internal name out of it (eg libfoo.so.5) and store that in the executable. The rtld will then look for libfoo.so.5 using -rpath locations. ISTR having to manually craft some libfoo.so -> libfoo.so.N during my sage porting efforts. The sage build process knows far too much about toolchain innards. --=20 Peter Jeremy --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iKYEARECAGYFAlLxzxZfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDBCRjc3QTcyNTg5NEVCRTY0RjREN0VFRUZF OEE0N0JGRjAwRkI4ODcACgkQ/opHv/APuIf0RACeN+Eyg7Cuyhp+DH6P4UJLCnlD RPoAoIpmXVYg0gf488pCsayMXfqizb5i =yc3F -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO--