Re: Building GDB 7.3.92 with MinGW

[Eli Zaretskii <eliz at gnu dot org>]

> Date: Sun, 15 Jan 2012 17:34:27 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>, asmwarrior@gmail.com,
> 	dje@google.com, gdb-patches@sourceware.org
> 
> I am not too sure whether the problems with MSYS also happen on cygwin
> or whether you have different issues. But I *think* we solve the problem
> by using semi-absolute paths (a path that looks absolute in a Unix
> environment, but is only missing the drive letter in the windows
> environment). To make it work, we use a directory name that works
> in both environments. For instance, if one could have directory c:/gnu/,
> and setup cygwin to mount c:/gnu into /gnu.
> 
> And then, one could configure GDB with a prefix such as --prefix=/gnu.
> As long as the other directories are configured as a subdirectory of
> that prefix, it should work as well as it does for me.

If so, that's not what I was looking for.  I was looking for a way for
GDB to "auto-configure" its directories based on the directory where
gdb.exe lives.

> > 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.
> 
> The relocation happens during startup. Search for "relocate" in
> main.c (I think - it should be inside function "captured_main").
> 
> During your debugging, it would be good to know whether the relocation
> is turned off, of whether it is failing.  A good way to figure this
> out, is to look at the generated gdb/config.h file. Search for "RELOCAT",
> and in particular: PYTHON_PATH_RELOCATABLE (I think that's what
> matters).

Thanks for the pointers, I will have a look.  But from what's been
said here, I suspect that it "fails" by design.