The SSP_ALL_CFLAGS in nptl arch CFLAGS leaks out and forces things
like dl-support.c, brk.c, sbrk.c memcpy, etc to be built with
-fstack-protector-all. This is bad when linking statically since
initializing TLS will call those functions before SSP is initialized.
The libpthread itself will still
On Wed, Nov 10, 2010 at 04:04:06PM -0600, Rob Landley wrote:
Look: Linux has to deal with binary only modules, which the developers hate.
To compensate for this, they go out of their way to avoid having a stable
internal API (which could argualy be used as a copyright barrier and thus
On Tue, Oct 05, 2010 at 09:23:13AM -0500, Steven J. Magnani wrote:
This patch series restores support for the Microblaze arch,
specifically the big-endian noMMU flavor.
Applied, thanks!
___
uClibc mailing list
uClibc@uclibc.org
On Thu, Nov 11, 2010 at 03:10:01PM +, Natanael Copa wrote:
The SSP_ALL_CFLAGS in nptl arch CFLAGS leaks out and forces things
like dl-support.c, brk.c, sbrk.c memcpy, etc to be built with
-fstack-protector-all. This is bad when linking statically since
initializing TLS will call those
On Thursday 11 November 2010 09:51:34 Jonathan Corbet wrote:
Hi, Rob,
Look: Linux has to deal with binary only modules, which the developers
hate. To compensate for this, they go out of their way to avoid having a
stable internal API (which could argualy be used as a copyright barrier
On Thursday 11 November 2010 09:07:31 Mark Brown wrote:
On Wed, Nov 10, 2010 at 04:04:06PM -0600, Rob Landley wrote:
Look: Linux has to deal with binary only modules, which the developers
hate. To compensate for this, they go out of their way to avoid having a
stable internal API (which
