From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5636 invoked by alias); 25 Mar 2013 08:28:50 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 5446 invoked by uid 89); 25 Mar 2013 08:28:43 -0000 X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 Received: from mail-ia0-f171.google.com (HELO mail-ia0-f171.google.com) (209.85.210.171) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 25 Mar 2013 08:28:41 +0000 Received: by mail-ia0-f171.google.com with SMTP id z13so5315184iaz.30 for ; Mon, 25 Mar 2013 01:28:39 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.7.242 with SMTP id m18mr10785202iga.53.1364200119707; Mon, 25 Mar 2013 01:28:39 -0700 (PDT) Received: by 10.64.14.129 with HTTP; Mon, 25 Mar 2013 01:28:39 -0700 (PDT) In-Reply-To: <515009B1.5030500@codesourcery.com> References: <83ip4s4ixc.fsf@gnu.org> <1363407692-18959-1-git-send-email-yao@codesourcery.com> <1363407692-18959-4-git-send-email-yao@codesourcery.com> <51492077.30307@codesourcery.com> <83sj3qyogk.fsf@gnu.org> <87vc8m7z1d.fsf@fleche.redhat.com> <514FA117.9030604@gmail.com> <83hajz3oef.fsf@gnu.org> <515009B1.5030500@codesourcery.com> Date: Mon, 25 Mar 2013 10:12:00 -0000 Message-ID: Subject: Re: [MinGW-w64]Build gdb/ctf.c failed From: Kai Tietz To: Yao Qi Cc: Eli Zaretskii , asmwarrior , tromey@redhat.com, gdb-patches@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 X-SW-Source: 2013-03/txt/msg00920.txt.bz2 2013/3/25 Yao Qi : > On 03/25/2013 04:06 PM, Kai Tietz wrote: >> The function 'mkdir' (please note it is without leading underscore), >> is declared in io.h header, which is of course include within unistd.h >> header. > > Right, 'mkdir' is declared io.h, which is included in unistd.h. Looks > like we should use "mkdir" instead of "_mkdir". How about the patch > below? It unbreaks the build of using mingw-w64 toolchain, while > mingw32 toolchain doesn't complain about it. I can't approve it, but it looks fine to me. Thanks, Kai