From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23549 invoked by alias); 15 Jan 2012 03:54:48 -0000 Received: (qmail 23541 invoked by uid 22791); 15 Jan 2012 03:54:47 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 15 Jan 2012 03:54:31 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0LXT00F00MQXH700@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Sun, 15 Jan 2012 05:54:30 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.126.65.106]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LXT00FLPMUS7QA0@a-mtaout21.012.net.il>; Sun, 15 Jan 2012 05:54:30 +0200 (IST) Date: Sun, 15 Jan 2012 13:35:00 -0000 From: Eli Zaretskii Subject: Re: Building GDB 7.3.92 with MinGW In-reply-to: <000001ccd30c$5ce854e0$16b8fea0$%muller@ics-cnrs.unistra.fr> To: Pierre Muller Cc: asmwarrior@gmail.com, brobecker@adacore.com, dje@google.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83sjjhips3.fsf@gnu.org> References: <83hb03e9sx.fsf@gnu.org> <838vlfe0k9.fsf@gnu.org> <4F0CD948.8080909@gmail.com> <4F0E266C.8080208@gmail.com> <20120112064721.GN31383@adacore.com> <20120112115355.GO31383@adacore.com> <838vlclv4r.fsf@gnu.org> <4F103C20.8070204@gmail.com> <83ipkfk3hg.fsf@gnu.org> <4F117B33.8080906@gmail.com> <834nvyjsqj.fsf@gnu.org> <000001ccd30c$5ce854e0$16b8fea0$%muller@ics-cnrs.unistra.fr> X-IsSubscribed: yes 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 X-SW-Source: 2012-01/txt/msg00519.txt.bz2 > From: "Pierre Muller" > Cc: , , > Date: Sat, 14 Jan 2012 23:32:10 +0100 > > After some debugging, > I believe that the main problem is related to the fact > that we use msys environment (which has msys specific mounts) > to compile a mingw32 GDB executable that knows nothing about those msys > mount points! > > config.h > get several entries with directories. > All but WITH_PYTHON_PATH (which is mingw32 compatible) > are msys paths: > DEBUGDIR, GDB_DATADIR and JIT_READER_DIR > but those msys pathes are not interpreted correctly by > a mingw32 executable (i.e. gdb.exe itself). This might explain how it works for me: I manually edit config.h to convert MSYS file names to native Windows ones, before building GDB. Perhaps Joel could tell where and how the relocation of the standard directories happens for him, and then we could try stepping through that code with a debugger. > I do believe that this is an error in the mingw32 configuration > and that it should be fixed in those configuration files... A simple Sed script will do, but it must be injected into the configure script. Alternatively, did you try to use MinGW file names in --prefix when configuring in the first place?