From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 51848 invoked by alias); 24 Jun 2015 18:57:02 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 51835 invoked by uid 89); 24 Jun 2015 18:57:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qc0-f181.google.com Received: from mail-qc0-f181.google.com (HELO mail-qc0-f181.google.com) (209.85.216.181) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 24 Jun 2015 18:57:00 +0000 Received: by qcji3 with SMTP id i3so14762458qcj.1 for ; Wed, 24 Jun 2015 11:56:58 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.90.99 with SMTP id w90mr53030216qgd.57.1435172218682; Wed, 24 Jun 2015 11:56:58 -0700 (PDT) Received: by 10.140.43.102 with HTTP; Wed, 24 Jun 2015 11:56:58 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jun 2015 18:57:00 -0000 Message-ID: Subject: Re: Custom gcc installation include files From: Jonathan Wakely To: Siddhartha Jain Cc: gcc-help Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-06/txt/msg00166.txt.bz2 On 24 June 2015 at 19:38, Siddhartha Jain wrote: > /usr/include/string.h:548:5: error: =E2=80=98__locale_t=E2=80=99 has not = been declared > __locale_t __loc) This indicates you are either doing something wrong or your C library is severely messed up. /usr/include/string.h is part of the C library, and the type __locale_t should be defined by another header in the C library, /usr/include/xlocale.h > there are a couple of other similar errors but this is the first one > and I thought it might be because the system gcc is 4.4.7 and it's > using the executable for gcc 4.8.1 No, that should work fine (and it does, I use such a setup frequently). I suggest you stop adding anything to C_INCLUDE_PATH. If you just invoke gcc 4.8.1 it should know how to find all the standard C and C++ headers it needs, without your help. If that still doesn't work and you want further help you will need to show the exact gcc or g++ command that causes the error, as well as any environment variables such as C_INCLUDE_PATH and CXX that you might have set that would confuse things. We can't guess what the problem is if you don't tell us exactly what you're doing.