public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Geert Bosch <bosch@gnat.com>
Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, gcc@gcc.gnu.org
Subject: Re: [Ada]: failure to build on Mandrake 8.1 / x86
Date: Thu, 11 Oct 2001 18:39:00 -0000	[thread overview]
Message-ID: <20011011183907.A10548@codesourcery.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10110112118340.27247-100000@nile.gnat.com>

On Thu, Oct 11, 2001 at 09:22:26PM -0400, Geert Bosch wrote:
> On Fri, 12 Oct 2001, Joseph S. Myers wrote:
>   
>   Generated files *not in CVS* should be generated from gcc_release.  The
>   normal method is for a bootstrap to put them in the source directory, but
>   if building puts them in the build directory instead then special
>   treatment is needed (and is currently present for the message catalogs).
> 
> I get conflicting messages on two points, could you answer these:
>   * Should the autogenerated files be checked in or not?
>   * Should the files be put in the source directory or in the build directory?

At present, the generated files require fairly exotic tools (i.e. a
complete prior GNAT installation) to create, so they should remain in
CVS.  That unfortunately means they need to be generated into the
source directory, or people will forget to copy new versions into the
source directory when they make changes to the original files.

Is it possible to enforce checking in fresh derived files with the
CVS commit script?

zw

  parent reply	other threads:[~2001-10-11 18:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 12:28 guerby
2001-10-11 10:40 ` guerby
2001-10-11 11:55   ` Geert Bosch
2001-10-11 15:46     ` guerby
2001-10-11 15:53       ` Geert Bosch
2001-10-11 16:31         ` guerby
2001-10-11 18:04           ` Richard Henderson
2001-10-11 18:07             ` Geert Bosch
2001-10-11 18:17               ` Joseph S. Myers
2001-10-11 18:22                 ` Geert Bosch
2001-10-11 18:38                   ` Joseph S. Myers
2001-10-11 18:39                   ` Zack Weinberg [this message]
2001-10-11 14:32   ` Florian Weimer

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=20011011183907.A10548@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=bosch@gnat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    /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).