From da49d63dc247207d59ae56ce11d7afc89d51c821 Mon Sep 17 00:00:00 2001 From: Matthew Dempsky Date: Fri, 24 Aug 2012 01:28:55 +0000 Subject: Don't attempt to warn about uninitialized __guard values yet. It's too early to assume that everyone has updated their compiler toolchains, and it seems to cause problems at least on armish when an out-of-date binutils is used. --- lib/libc/sys/stack_protector.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib') diff --git a/lib/libc/sys/stack_protector.c b/lib/libc/sys/stack_protector.c index 2aa187afbed..a6b147c1e22 100644 --- a/lib/libc/sys/stack_protector.c +++ b/lib/libc/sys/stack_protector.c @@ -1,4 +1,4 @@ -/* $OpenBSD: stack_protector.c,v 1.11 2012/08/22 17:06:39 matthew Exp $ */ +/* $OpenBSD: stack_protector.c,v 1.12 2012/08/24 01:28:54 matthew Exp $ */ /* * Copyright (c) 2002 Hiroaki Etoh, Federico G. Schwindt, and Miodrag Vallat. @@ -55,7 +55,7 @@ __guard_setup(void) if (__guard[i] != 0) return; -#ifdef __ELF__ +#if 0 { struct syslog_data sdata = SYSLOG_DATA_INIT; syslog_r(LOG_WARNING, &sdata, "__guard not initialized"); -- cgit v1.2.3