From owner-freebsd-threads@FreeBSD.ORG Fri Jun 27 00:56:08 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 DA04837B401; Fri, 27 Jun 2003 00:56:08 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C26343FE9; Fri, 27 Jun 2003 00:56:08 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5R7u7DZ022323; Fri, 27 Jun 2003 00:56:07 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5R7u7hn042238; Fri, 27 Jun 2003 00:56:07 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h5R7u7SZ042237; Fri, 27 Jun 2003 00:56:07 -0700 (PDT) (envelope-from marcel) Date: Fri, 27 Jun 2003 00:56:07 -0700 From: Marcel Moolenaar To: threads@FreeBSD.org, ru@FreeBSD.org Message-ID: <20030627075607.GA42198@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: 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 07:56:09 -0000 [Ruslan added for his insights] Ok, 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. 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? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net