[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150210145434.GA21294@cream.2f30.org>
Date: Tue, 10 Feb 2015 14:54:34 +0000
From: Dimitris Papastamos <sin@...0.org>
To: musl@...ts.openwall.com
Subject: Re: standalone fortify source implementation
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
