From: Danny Backx <danny.backx@scarlet.be>
To: gdb@sourceware.org
Subject: Build question
Date: Fri, 21 Aug 2009 00:24:00 -0000 [thread overview]
Message-ID: <1250803105.11282.96.camel@pavilion> (raw)
Advice wanted on how to patch gdb's build.
I have a cross-gdb working between my linux PC and a i386-mingw32ce
target running gdbserver.
My question is about the i386-mingw32ce-gdb build.
The issue I need to solve is that HAVE_DOS_BASED_FILE_SYSTEM doesn't get
defined. I can manipulate the build so things work, but I'd like to make
a clean patch.
HAVE_DOS_BASED_FILE_SYSTEM doesn't get set in my cross-compile, because
gdb gets compiled by the host gcc, which doesn't set _WIN32. So the
HAVE_DOS_BASED_FILE_SYSTEM never gets defined. This happens both in
gdb/* and in libiberty/* .
So where should I change this properly ?
I would like it to come from somewhere in the configuration scripts (and
I'm now asking where would be the best place).
Another thing to edit is then include/filenames.h - it needs to grab
this and do the right thing, instead of just reacting to _WIN32 and
such. But that's a trivial fix.
Thanks,
Danny
--
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info
next reply other threads:[~2009-08-20 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 0:24 Danny Backx [this message]
2009-08-21 17:30 ` Tom Tromey
2009-08-21 17:57 ` Eli Zaretskii
2009-08-21 18:23 ` Danny Backx
2009-08-21 18:51 ` Eli Zaretskii
2009-08-21 20:15 ` Danny Backx
2009-08-21 21:57 ` Eli Zaretskii
2009-08-22 9:03 ` Tom Tromey
2009-08-22 9:55 ` Danny Backx
2009-08-22 11:07 ` Eli Zaretskii
2009-08-24 10:11 ` Danny Backx
2009-09-01 18:03 ` Danny Backx
2009-09-01 19:34 ` Eli Zaretskii
2009-09-01 20:10 ` Danny Backx
2009-09-02 3:25 ` Eli Zaretskii
2009-09-05 9:33 ` Danny Backx
2009-09-01 19:35 ` Eli Zaretskii
2009-08-22 22:01 ` Daniel Jacobowitz
2009-08-23 7:28 ` Joel Brobecker
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=1250803105.11282.96.camel@pavilion \
--to=danny.backx@scarlet.be \
--cc=gdb@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