From: Florian Weimer <fw@deneb.enyo.de>
To: guerby@acm.org
Cc: bosch@gnat.com, zack@codesourcery.com, minyard@acm.org,
gcc@gcc.gnu.org
Subject: Re: Ada build now requires gnatmake?
Date: Tue, 04 Dec 2001 14:32:00 -0000 [thread overview]
Message-ID: <87667m7fvq.fsf@deneb.enyo.de> (raw)
In-Reply-To: <200112042113.fB4LDft31185@ulmo.localdomain> (<guerby@acm.org>'s message of "Tue, 4 Dec 2001 22:13:41 +0100")
<guerby@acm.org> writes:
> I reread the discussions, and no message carries a patch that applies
> cleanly any longer. While I'm at it I'll submit a patch that merges
> some common code for those Ada file generating tools (xtreeprs,
> xsinfo, xeinfo and xnmake - 1665 SLOC total), provides a wrapper tool
> and a Makefile target that does not use gnatmake to get things done
> and is parallel-safe.
If you want to eliminate the use of gnatmake in order to enable
building with a minimal GNAT version, I'm not sure if you will achieve
this goal with your approach. IIRC, some of the tools use the
GNAT.Spitbol packages, which in turn depend on Ada.Strings.Unbounded,
which is not available with a minimal GNAT installation (at least
there's an undocumented coding requirement in this direction).
next prev parent reply other threads:[~2001-12-04 22:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 10:56 Corey Minyard
2001-12-04 11:15 ` Geert Bosch
2001-12-04 11:22 ` Zack Weinberg
2001-12-04 11:40 ` Joseph S. Myers
2001-12-04 11:46 ` guerby
2001-12-04 11:51 ` Joseph S. Myers
2001-12-04 11:56 ` Geert Bosch
2001-12-04 12:24 ` guerby
2001-12-04 12:28 ` Geert Bosch
2001-12-04 13:23 ` guerby
2001-12-04 14:32 ` Florian Weimer [this message]
2001-12-04 14:58 ` guerby
2001-12-04 15:06 ` Geert Bosch
2001-12-04 13:25 dewar
2001-12-04 16:08 Richard Kenner
2001-12-04 16:49 ` Joe Buck
2001-12-05 4:30 ` guerby
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=87667m7fvq.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.org \
--cc=minyard@acm.org \
--cc=zack@codesourcery.com \
/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).