From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4D88A13877A for ; Tue, 5 Aug 2014 23:46:04 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4B173E09C4; Tue, 5 Aug 2014 23:45:57 +0000 (UTC) Received: from s108.avahost.net (s108.avahost.net [174.34.254.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3B37FE07DD for ; Tue, 5 Aug 2014 23:45:56 +0000 (UTC) Received: from c-24-18-233-198.hsd1.wa.comcast.net ([24.18.233.198]:43903 helo=localhost.localnet) by s108.avahost.net with esmtpsa (UNKNOWN:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1XEoQV-000Csq-Ml for gentoo-user@lists.gentoo.org; Tue, 05 Aug 2014 19:45:55 -0400 From: "((RayDar))" To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: glibc-2.17 fails and warning: setlocale: LC_ALL error Date: Tue, 05 Aug 2014 16:48:20 -0700 Message-ID: <4053153.tmzZyFxl9M@localhost> User-Agent: KMail/4.12.5 (Linux/3.12.21-gentoo-r1; KDE/4.12.5; i686; ; ) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - s108.avahost.net X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - raydarllc.com X-Get-Message-Sender-Via: s108.avahost.net: authenticated_id: hrayda14/from_h X-Archives-Salt: 84e59f63-b5ec-4221-804f-6c8a11a41919 X-Archives-Hash: 85730af5091ef64f643cc30ab0f2510f Hello, I think I can offer some some more clues to the problem in thread started by Dale, as archived here: https://www.mail-archive.com/gentoo-user@lists.gentoo.org/msg147315.html I too get the "Your old kernel is broken. You need to update it to a newer version as syscall() will break." message whenever I try to emerge glibc-2.17. This happens on all three of my machines, which are kept up to date and have slightly different configurations. It is likely that many people are in a broken state, but they don't know it because they haven't tried re- emerging glibc. Previously in this thread, I see that Hinnerk van Bruinehsen asked: > Can you run; > printf "#include \n#include \nint main(){return \ > syscall(1000)!=-1;}\n" > syscall.c && make syscall && ./syscall && echo $? When I try this on each of my systems, I get the same output: cc syscall.c -o syscall Notice that the line with the 0 is missing. I found a work around: move to an earlier kernel. This problem happens for me on kernel-3.14.14 and for Dale on kernel-3.15.5. But, it DOESN'T happen for me on 3.12.21-r1. When I boot into the 3.12.21-r1 kernel, the printf() above outputs: cc syscall.c -o syscall 0 as it should. Could the emerge glibc fail be due to a required kernel configuration option that didn't make it into 3.14.14 or above?