From: Tom Tromey <tromey@redhat.com>
To: danny.backx@scarlet.be
Cc: Eli Zaretskii <eliz@gnu.org>, gdb@sourceware.org
Subject: Re: Build question
Date: Sat, 22 Aug 2009 09:03:00 -0000 [thread overview]
Message-ID: <m3r5v425lu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1250880746.11282.128.camel@pavilion> (Danny Backx's message of "Fri, 21 Aug 2009 20:52:26 +0200")
>>>>> "Danny" == Danny Backx <danny.backx@scarlet.be> writes:
Danny> I am building i386-mingw32ce-gdb (or arm-mingw32ce-gdb). The targets
Danny> specified are Windows CE based, so they all have this "DOS BASED" file
Danny> system. So why test this at run time ?
IIUC, the problem is that gdb doesn't really differentiate between
target file names and host file names. This matters because some things
are searched for on the host but some on the target.
If you want to always define HAVE_DOS_BASED_FILE_SYSTEM, I guess that is
possible. It is hard to picture when that would be appropriate for CVS
GDB, though, due to --enable-targets=all.
If you don't want to mix different kinds of file names, then could you
further explain this note?
http://sourceware.org/ml/gdb-patches/2009-08/msg00160.html
It looks to me that the "good" scenario here mixes Unix-like and
DOS-like filenames, but I don't understand that.
Tom
next prev parent reply other threads:[~2009-08-21 21:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 0:24 Danny Backx
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 [this message]
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=m3r5v425lu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=danny.backx@scarlet.be \
--cc=eliz@gnu.org \
--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