From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13087 invoked by alias); 14 Feb 2012 20:37:51 -0000 Received: (qmail 13063 invoked by uid 22791); 14 Feb 2012 20:37:50 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from toast.topped-with-meat.com (HELO topped-with-meat.com) (204.197.218.159) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 14 Feb 2012 20:37:37 +0000 Received: by topped-with-meat.com (Postfix, from userid 5281) id E56FA2C080; Tue, 14 Feb 2012 12:37:36 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Roland McGrath To: David Miller Cc: joseph@codesourcery.com, libc-alpha@sourceware.org, libc-ports@sourceware.org Subject: Re: Arch maintainers: new approach for crti.o and crtn.o In-Reply-To: David Miller's message of Tuesday, 14 February 2012 15:23:57 -0500 <20120214.152357.1056020502119248076.davem@davemloft.net> References: <20120214.145651.1071842129336322771.davem@davemloft.net> <20120214200953.71FD12C081@topped-with-meat.com> <20120214.152357.1056020502119248076.davem@davemloft.net> Message-Id: <20120214203736.E56FA2C080@topped-with-meat.com> Date: Tue, 14 Feb 2012 20:37:00 -0000 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.0 cv=fe7WOzsF c=1 sm=1 a=9jnp3Hz6ipsA:10 a=kj9zAlcOel0A:10 a=KetBEl5QWv-iWMmARxwA:9 a=CjuIK1q_8ugA:10 a=WkljmVdYkabdwxfqvArNOQ==:117 X-IsSubscribed: yes Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: libc-ports-owner@sourceware.org X-SW-Source: 2012-02/txt/msg00041.txt.bz2 > Are you then going to do something with symlinks or similar to end up > with the crt{n,i}.o names in the end? It seems likely that having those names will make things easiest all around. So yes, I'd figured we'd probably have: $(objpfx)crti.o $(objpfx)crtn.o: $(objpfx)%.o: $(objpfx)%.os ln -f $< $@ or something like that. Thanks, Roland