From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/6962 Path: news.gmane.org!not-for-mail From: Dimitris Papastamos Newsgroups: gmane.linux.lib.musl.general Subject: Re: standalone fortify source implementation Date: Tue, 10 Feb 2015 14:54:34 +0000 Message-ID: <20150210145434.GA21294@cream.2f30.org> References: <20150204160214.GA3717@cream.2f30.org> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1423580096 19902 80.91.229.3 (10 Feb 2015 14:54:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 10 Feb 2015 14:54:56 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-6975-gllmg-musl=m.gmane.org@lists.openwall.com Tue Feb 10 15:54:55 2015 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1YLCDE-00061N-MS for gllmg-musl@m.gmane.org; Tue, 10 Feb 2015 15:54:52 +0100 Original-Received: (qmail 25791 invoked by uid 550); 10 Feb 2015 14:54:51 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 25777 invoked from network); 10 Feb 2015 14:54:50 -0000 Content-Disposition: inline In-Reply-To: <20150204160214.GA3717@cream.2f30.org> User-Agent: Mutt/1.5.23 (2014-03-12) Xref: news.gmane.org gmane.linux.lib.musl.general:6962 Archived-At: Hi all, Having had a chat with the Alpine Linux developers, I'd like some feedback on what is the recommended way of integrating this standalone fortify implementation by default in a distribution. Would it simply be a matter of adding another include dir in gcc specs that gets preference over /usr/include? In regards to glibc binary compatibility, will the __*_chk() symbols be part of musl or would it be in a separate glibc compat shared library? Cheers, Dimitris