From owner-freebsd-threads@FreeBSD.ORG Fri Jun 27 01:06:00 2003 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39C2F37B401 for ; Fri, 27 Jun 2003 01:06:00 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30B5F43FBD for ; Fri, 27 Jun 2003 01:05:55 -0700 (PDT) (envelope-from ru@sunbay.com) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h5R85oVd049106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Jun 2003 11:05:50 +0300 (EEST) (envelope-from ru@sunbay.com) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h5R85oiW049101; Fri, 27 Jun 2003 11:05:50 +0300 (EEST) (envelope-from ru) Date: Fri, 27 Jun 2003 11:05:50 +0300 From: Ruslan Ermilov To: Marcel Moolenaar Message-ID: <20030627080550.GA48342@sunbay.com> References: <20030627075607.GA42198@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Content-Disposition: inline In-Reply-To: <20030627075607.GA42198@dhcp01.pn.xcllnt.net> User-Agent: Mutt/1.5.4i cc: threads@FreeBSD.org Subject: Re: Obsoleting libc_r: How to create compat links X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 08:06:00 -0000 --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Funny thing: reading your commit mail, and right after that receiving this message. :-) On Fri, Jun 27, 2003 at 12:56:07AM -0700, Marcel Moolenaar wrote: > [Ruslan added for his insights] >=20 > Ok, >=20 > I decided to obsolete libc_r on ia64 so that I can de-pessimize the > setjmp/longjmp code some time before 5.2 and have sufficient time to > deal with problems due to not having libc_r. >=20 > One thing we probably want to do is create compatibility links from > libc_r* to libthr* or libkse*. At this time I libthr is tested on > ia64, so I opt to have libc_r linked to libthr. What's the best way > to do that, so that it can be used for other platforms in due time? >=20 First off, symlinking won't help old binaries that were linked dynamically with libc_r.so.X, but you're supposed to well know that already. :-) So, the only useful option that is left is to symlink the static and dymanic libraries (.a and .so, but not .so.X), and this can be done in libc_r/Makefile using SYMLINKS (for MACHINE_ARCH of ia64 only). Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE++/rdUkv4P6juNwoRAkE4AJ9khMzeLqQzmvc+L7Aupmsod2d3KQCbBacH 1U0mZ+eWtRt4/gAbT9QjCRw= =Hgzp -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--