From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, Stan Shebs <shebs@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] Updates to gdbint.texinfo
Date: Wed, 04 Jul 2001 11:25:00 -0000 [thread overview]
Message-ID: <3B435E8C.9000304@cygnus.com> (raw)
In-Reply-To: <1483-Fri29Jun2001221859+0300-eliz@is.elta.co.il>
>> + behavour.}
>
>
> There's a typo in the last word.
And I did use Ispell this time :-/
>> ! @end example
>> !
>> ! and not:
>> > + @example
>
> The "and not:" part above needs a @noindent before it.
Done.
>> + @subsection File Names
>> +
>> + Any file that is used to build @value{GDBN} on either DJGPP or Cygwin
>> + must be 8.3 compliant.
>
>
> I suggest to add here that file names which match but for the letter
> case will make trouble on DOS and Windows, even if long file names are
> supported.
I reworded it. It talks about the build process.
@subsection File Names
Any file used when building the core of @value{GDBN} must be in lower
case. Any file used when building the core of @value{GDBN} must be 8.3
unique. These requirements apply to both source and generated files.
@emph{Pragmatics: The core of @value{GDBN} must be buildable on many
platforms including DJGPP and MacOS/HFS. Every time an unfriendly file
is introduced to the build process both @file{Makefile.in} and
@file{configure.in} need to be modified accordingly. Compare the
convoluted conversion process needed to transform @file{COPYING} into
@file{copying.c} with the conversion needed to transform
@file{version.in} into @file{version.c}.}
Any file non 8.3 compliant file (that is not used when building the core
of @value{GDBN}) must be added to @file{gdb/config/djgpp/fnchange.lst}.
@emph{Pragmatics: This is clearly a compromise.}
When @value{GDBN} has a local version of a system header file (ex
@file{string.h}) the file name based on the POSIX header prefixed with
@file{gdb_} (@file{gdb_string.h}).
For other files @samp{-} is used as the separator.
next prev parent reply other threads:[~2001-07-04 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 11:19 Andrew Cagney
[not found] ` <1483-Fri29Jun2001221859+0300-eliz@is.elta.co.il>
2001-06-29 13:41 ` Christopher Faylor
2001-06-29 13:46 ` Stan Shebs
2001-07-01 16:36 ` Andrew Cagney
2001-07-04 11:25 ` Andrew Cagney [this message]
2001-07-04 11:48 ` Eli Zaretskii
2001-07-04 13:49 ` Andrew Cagney
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=3B435E8C.9000304@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=shebs@apple.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