From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <asmwarrior@gmail.com>, <brobecker@adacore.com>, <dje@google.com>,
<gdb-patches@sourceware.org>
Subject: RE: Building GDB 7.3.92 with MinGW
Date: Sun, 15 Jan 2012 18:01:00 -0000 [thread overview]
Message-ID: <000301ccd3a7$3db8c460$b92a4d20$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83sjjhips3.fsf@gnu.org>
Eli,
I also wrongly supposed that configure prefix or related entries should
be msys pathes.
It seems that using directly a mingw32 path for prefix
works well. This allows to get a working relocate_gdb_directory
call in main.c
Of course, this only works for really existing directories, but
from what I read in the sources, this was by design.
A configured directory should only be substituted if the substitute result
is an existing directory.
So I used
--prefix=e:/pas/fpc-2.6.0
to run configure
ran 'make all install'
and got a first installation in e:\pas\fpc-2.6.0
I then tried
make install prefix=e:/pas/fpc-2.7.1/gdb
and debugged GDB with itself in e:\pas\fpc-2.7.1\gdb\bin
gdb ./gdb
added a break relocate_gdb_directory
and could check that
e:/pas/fpc-2.6.0/share/gdb
was transformed into
e:\pas\fpc-2.7.1\gdb\share\gdb
> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : dimanche 15 janvier 2012 04:55
> À : Pierre Muller
> Cc : asmwarrior@gmail.com; brobecker@adacore.com; dje@google.com; gdb-
> patches@sourceware.org
> Objet : 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.
I also thought that msys system required
real msys pathes to function correctly, but it seems to handle
Mingw32 pathes starting with X:/ correctly also
which solves the problem.
I am still surprised that in fact, we really need to do
this in order to get the correct behavior.
> 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.
That not true in case you really have other mount points
I personally have my different GDB sources located inside cygwin
/usr/local/src
subdirectories, and I also have
this cygwin /usr/local/src mounted as /usr/local/src on mysys,
which is nice in a way, but leads me to not be able to
remember in with Windows directory the sources really are ...
> Alternatively, did you try to use MinGW file names in --prefix when
> configuring in the first place?
As said above, it seems that this is the right answer!
Pierre Muller
next prev parent reply other threads:[~2012-01-15 17:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 18:46 Eli Zaretskii
2012-01-10 18:59 ` Doug Evans
2012-01-10 20:56 ` Eli Zaretskii
2012-01-13 11:28 ` Eli Zaretskii
2012-01-10 19:25 ` Tom Tromey
2012-01-10 20:55 ` Joseph S. Myers
2012-01-10 20:58 ` Eli Zaretskii
2012-01-10 21:00 ` Eli Zaretskii
2012-01-10 19:31 ` Alfred M. Szmidt
2012-01-10 21:01 ` Eli Zaretskii
2012-01-10 21:26 ` Doug Evans
2012-01-11 0:37 ` asmwarrior
2012-01-11 4:08 ` Eli Zaretskii
2012-01-11 4:54 ` asmwarrior
2012-01-11 17:54 ` Doug Evans
2012-01-12 0:17 ` asmwarrior
2012-01-12 6:47 ` Eli Zaretskii
2012-01-12 8:07 ` Joel Brobecker
2012-01-12 11:54 ` Eli Zaretskii
2012-01-12 12:35 ` Joel Brobecker
2012-01-12 16:59 ` Eli Zaretskii
2012-01-13 14:29 ` asmwarrior
2012-01-13 16:55 ` Eli Zaretskii
2012-01-14 13:53 ` asmwarrior
[not found] ` <4F117B33.8080906@gmail.com>
2012-01-14 18:15 ` Eli Zaretskii
2012-01-15 3:33 ` Pierre Muller
[not found] ` <18546.4176851839$1326580387@news.gmane.org>
2012-01-15 3:54 ` asmwarrior
[not found] ` <000001ccd30c$5ce854e0$16b8fea0$%muller@ics-cnrs.unistra.fr>
2012-01-15 13:35 ` Eli Zaretskii
2012-01-15 17:01 ` Joel Brobecker
2012-01-15 18:55 ` Eli Zaretskii
2012-01-15 18:01 ` Pierre Muller [this message]
[not found] ` <000301ccd3a7$3db8c460$b92a4d20$%muller@ics-cnrs.unistra.fr>
2012-01-15 18:55 ` Eli Zaretskii
2012-01-16 3:08 ` Pierre Muller
2012-01-10 21:33 ` Tom Tromey
2012-01-11 1:31 ` asmwarrior
2012-01-11 4:30 ` Eli Zaretskii
2012-01-11 4:30 ` asmwarrior
2012-01-11 3:32 ` Joel Brobecker
2012-01-13 11:06 ` Eli Zaretskii
2012-01-13 12:39 ` Joel Brobecker
2012-01-13 13:56 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000301ccd3a7$3db8c460$b92a4d20$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=asmwarrior@gmail.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).