From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb@sources.redhat.com
Subject: Re: host_makefile_frag and cross debugging
Date: Fri, 24 Jun 2005 18:56:00 -0000 [thread overview]
Message-ID: <u7jgjh6l7.fsf@gnu.org> (raw)
In-Reply-To: <op.ssvp4glpo669wz@terrorhawk.bri.st.com> (message from Andrew STUBBS on Fri, 24 Jun 2005 15:49:18 +0100)
> Cc: gdb@sources.redhat.com
> Date: Fri, 24 Jun 2005 15:49:18 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
>
> > Autoconf mostly. The xm files are gone; do the test elsewhere. Check
> > what CVS does for path separators. Eli fixed these not long ago.
>
> Ah, I've found it. There's a preprocessor test in defs.h. Way too simple
> for any autoconf project surely :-)
It didn't seem to me justified to use The Great Guns of Autoconf to
make a test whose results are known in advance: we know precisely
which platforms use `;' as path separator, and the list of those
platforms is not likely to change any time soon.
prev parent reply other threads:[~2005-06-24 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 11:46 Andrew STUBBS
2005-06-24 14:09 ` Daniel Jacobowitz
2005-06-24 14:33 ` Andrew STUBBS
2005-06-24 14:37 ` Daniel Jacobowitz
2005-06-24 14:52 ` Andrew STUBBS
2005-06-24 18:56 ` Eli Zaretskii [this message]
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=u7jgjh6l7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=gdb@sources.redhat.com \
/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