public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "charlet at gcc dot gnu dot org" <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, 10 Feb 2004 11:03:00 -0000 [thread overview] Message-ID: <20040210110358.15402.qmail@sources.redhat.com> (raw) In-Reply-To: <20020310104601.5911.zack@codesourcery.com> ------- Additional Comments From charlet at gcc dot gnu dot org 2004-02-10 11:03 ------- libada-branch now merged, so it is no longer necessary to do a make -C gcc gnatlib_and_tools to build Ada, as well as handling of cross compilers and --enable-shared. Keeping this PR open for the issue of supporting multilib. I am not familiar with how multilib works, so this will likely require help from someone that knows this area. Arno -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5911
next prev parent reply other threads:[~2004-02-10 11:03 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 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 [this message] 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=20040210110358.15402.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: 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).