From owner-freebsd-current@FreeBSD.ORG Fri Jul 30 09:21:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06E7516A4CE; Fri, 30 Jul 2004 09:21:42 +0000 (GMT) Received: from web.portaone.com (support.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7257C43D41; Fri, 30 Jul 2004 09:21:41 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.20] (portacare.portaone.com [195.140.247.242]) (authenticated bits=0) by web.portaone.com (8.12.8p2/8.12.8) with ESMTP id i6U9LWWq015044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Jul 2004 11:21:33 +0200 (CEST) (envelope-from sobomax@portaone.com) Message-ID: <410A130B.3020900@portaone.com> Date: Fri, 30 Jul 2004 12:21:15 +0300 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <410A1176.8050906@portaone.com> In-Reply-To: <410A1176.8050906@portaone.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: False alarm! [Was: strip(1) - POLA breakage] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Jul 2004 09:21:42 -0000 Please ignore this message - the problem was caused by adding binary into CVS without binary flag set, not by strip(1). I am sorry for the confusion. Regards, Maxim Maxim Sobolev wrote: > Hi, > > I've noticed that strip(1) has departured from its historic behaviour - > now when I do `strip foo' on a FreeBSD ELF executable, the resulting > binary can't be executed giving the following error from the dynamic > linker: > > /libexec/ld-elf.so.1: ./foo: Shared object has no run-time symbol table > > This have to be fixed, since it can break lot of ports that assume > previous behaviour. > > -Maxim >