This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Building GDB 7.3.92 with MinGW


> From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> Cc: <brobecker@adacore.com>, <dje@google.com>, <gdb-patches@sourceware.org>
> 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?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]