public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm at polyomino dot org dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/5911] Ada runtime and utilities should be broken out to their own directory
Date: Tue, 21 Oct 2003 16:18:00 -0000 [thread overview]
Message-ID: <20031021161002.20907.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020310104601.5911.zack@codesourcery.com>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5911
------- Additional Comments From jsm at polyomino dot org dot uk 2003-10-21 16:09 -------
Subject: Re: Ada runtime and utilities should be broken out
to their own directory
On Tue, 21 Oct 2003, charlet at gcc dot gnu dot org wrote:
> For one thing, I started looking at how you add a new e.g. libada directory
> (and enable its configuration and build from the top level directory) and
> I must admit that it is not at all clear how to to that (I'm not a configure
> expert anyway).
>
> Assuming "someone" would add a dummy libada directory
> that would get configured and built (e.g. with an empty Makefile and configure)
> automatically, I could then start working on providing an actual
> configure.in and Makefile.in to make it work for real.
I expect Nathanael can advise on this - and also on anything special
needed in that directory to ensure that such things as multilibs and
Canadian crosses work properly. (Current documentation in this area is
rather lacking, though there's the old etc/configure.texi included in
binutils that documents the *old* toplevel system.)
next prev parent reply other threads:[~2003-10-21 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020310104601.5911.zack@codesourcery.com>
2003-07-07 2:30 ` pinskia at physics dot uc dot edu
2003-07-19 17:46 ` pinskia at physics dot uc dot edu
2003-09-14 16:48 ` zack at gcc dot gnu dot org
2003-10-09 1:44 ` pinskia at gcc dot gnu dot org
2003-10-21 13:02 ` charlet at gcc dot gnu dot org
2003-10-21 16:18 ` jsm at polyomino dot org dot uk [this message]
2003-10-21 17:00 ` charlet at gcc dot gnu dot org
2004-01-27 16:31 ` pinskia at gcc dot gnu dot org
2004-02-10 10:44 ` cvs-commit at gcc dot gnu dot org
2004-02-10 10:51 ` cvs-commit at gcc dot gnu dot org
2004-02-10 10:54 ` cvs-commit at gcc dot gnu dot org
2004-02-10 11:03 ` charlet at gcc dot gnu dot org
2004-02-12 16:44 ` [Bug ada/5911] Support for multilib in Ada charlet at gcc dot gnu dot org
2004-02-12 16:48 ` pinskia at gcc dot gnu dot org
2005-01-28 6:23 ` pinskia at gcc dot gnu dot org
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=20031021161002.20907.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).