public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Arnaud Charlet <charlet@adacore.com>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, ADA, DOC] PR 15479: Crossrefs and links
Date: Tue, 18 Mar 2008 22:05:00 -0000	[thread overview]
Message-ID: <20080318220220.GA17497@adacore.com> (raw)
In-Reply-To: <20080318214745.GG2094@ins.uni-bonn.de>

> Should it still be possible to build the VMS version of the User's Guide
> as well as the UNW version using xgnatugn,

Yes. But both will never end up under the same directory, so they can end
up with the same name.

> but both should now have the
> same name?  Or should just the UNW version be renamed to gnat_ugn.info?
> Should it still be possible with xgnatugn to generate an UNW version
> with the gnat_ugn_unw name?

Preferably, yes. In other words, if you could keep xgnatugn as it is today,
that'd be easier to handle.

> Asking here because I assume that there is some build process external
> to GCC which generates the VMS version (the code in gcc/ada/Make-lang.in

Indeed, for the FSF version, currently only the unw version is generated,
although I guess in theory, we could generate the other (when doing
a VMS build, which probably nobody outside AdaCore does these days).

Let me know if you have further questions.

Arno

  reply	other threads:[~2008-03-18 22:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 14:12 Ralf Wildenhues
2008-03-16 18:32 ` Arnaud Charlet
2008-03-16 22:08   ` Ralf Wildenhues
2008-03-17  9:47     ` Arnaud Charlet
2008-03-17 20:56       ` Ralf Wildenhues
2008-03-18  9:05         ` Arnaud Charlet
2008-03-18 21:55           ` Ralf Wildenhues
2008-03-18 22:05             ` Arnaud Charlet [this message]
2008-03-18 22:27               ` Ralf Wildenhues
2008-03-19  8:44                 ` Arnaud Charlet
2008-03-20 19:58                   ` Ralf Wildenhues
2008-03-21 11:38                     ` Arnaud Charlet

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=20080318220220.GA17497@adacore.com \
    --to=charlet@adacore.com \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=gcc-patches@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).