From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Danny Backx <danny.backx@scarlet.be>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: shared lib dos filename style - one more question
Date: Tue, 13 Oct 2009 15:51:00 -0000 [thread overview]
Message-ID: <20091013155136.GA30684@caradoc.them.org> (raw)
In-Reply-To: <20091013052101.GI5272@adacore.com>
On Mon, Oct 12, 2009 at 10:21:01PM -0700, Joel Brobecker wrote:
> > There's nothing straightforward that this latter approach could do for
> > case-sensitivity problems, though - is there? I'd prefer not to
> > completely rule out handling this case.
>
> Hmmm, I was indeed carefully side-stepping this issue, busted :).
> I was hoping that this wasn't going to matter in practice...
I've worked with a build system (for a mobile phone OS) that uppercase
all filenames halfway through the build process. So which case you
get in debug info is pretty hard to predict.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-10-13 15:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 13:49 Danny Backx
2009-10-07 20:05 ` Danny Backx
2009-10-07 20:11 ` Daniel Jacobowitz
2009-10-08 16:01 ` Danny Backx
2009-10-09 17:36 ` Joel Brobecker
2009-10-09 18:58 ` Danny Backx
2009-10-10 2:19 ` Joel Brobecker
2009-10-12 20:05 ` Danny Backx
2009-10-12 20:28 ` Eli Zaretskii
2009-10-13 5:24 ` Joel Brobecker
2009-10-13 10:57 ` Pedro Alves
2009-10-13 15:30 ` Joel Brobecker
2009-10-13 18:23 ` Eli Zaretskii
2009-10-13 18:12 ` Eli Zaretskii
2009-10-13 18:19 ` Daniel Jacobowitz
2009-10-12 20:45 ` Daniel Jacobowitz
2009-10-13 5:21 ` Joel Brobecker
2009-10-13 15:51 ` Daniel Jacobowitz [this message]
2009-10-14 20:18 ` Danny Backx
2009-10-17 4:16 ` 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=20091013155136.GA30684@caradoc.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=danny.backx@scarlet.be \
--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