public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/5911: Ada runtime and utilities should be broken out to their own directory Date: Sun, 10 Mar 2002 13:56:00 -0000 [thread overview] Message-ID: <20020310215601.12669.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/5911; it has been noted by GNATS. From: Florian Weimer <fw@deneb.enyo.de> To: zack@codesourcery.com Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: ada/5911: Ada runtime and utilities should be broken out to their own directory Date: Sun, 10 Mar 2002 22:47:15 +0100 zack@codesourcery.com writes: > The location of the Ada runtime and utilities is inconsistent > with the location of all other language runtimes. They > should be moved to their own toplevel subdirectory, and their > build harness brought into line with the other languages. For technical reasons, the GNAT front end is built using the run-time library sources which come with the compiler sources, and not using the installed GNAT run-time library on the host system. In other words, the compiler depends on a (rather small) subset of the run-time library sources. However, there is no reason why a large part of the run-time library could not be moved to a separate directory. For the build, we should use another separate directory, IMHO.
next reply other threads:[~2002-03-10 21:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-10 13:56 Florian Weimer [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-12 21:17 neroden 2002-03-11 2:36 Florian Weimer 2002-03-11 2:16 Zack Weinberg 2002-03-11 2:06 Zack Weinberg 2002-03-10 11:06 Joseph S. Myers 2002-03-10 10:46 zack
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=20020310215601.12669.qmail@sources.redhat.com \ --to=fw@deneb.enyo.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).