From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: How to defeat new check for presence of Ada compiler
Date: Thu, 22 Nov 2001 08:37:00 -0000 [thread overview]
Message-ID: <10111300136.AA24820@vlsi1.ultra.nyu.edu> (raw)
Err, I'd expect it to be the same now, since the configure test
is for the *host* ada compiler, not the target ada compiler.
No, it's the target. The mechanism is this:
(1) Build a cross-compiler to the target.
(2) On the host, do "make stage1" and "make gnat-cross".
(3) On the target, bootstrap and install for just C.
(4) On the target, configure to build Ada and run "make" until it
fails.
(5) Copy .s files make in step (2) to the target and redo "make".
However, my suggestion is just to symlink a gnatgcc to be, e.g., /bin/true.
WARNING: multiple messages have this Message-ID
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: How to defeat new check for presence of Ada compiler
Date: Thu, 29 Nov 2001 17:42:00 -0000 [thread overview]
Message-ID: <10111300136.AA24820@vlsi1.ultra.nyu.edu> (raw)
Message-ID: <20011129174200.PPG5kiiIFg_RcvfJCqgsu1WwSVjuWSqnhc8qUOvv4Yo@z> (raw)
Err, I'd expect it to be the same now, since the configure test
is for the *host* ada compiler, not the target ada compiler.
No, it's the target. The mechanism is this:
(1) Build a cross-compiler to the target.
(2) On the host, do "make stage1" and "make gnat-cross".
(3) On the target, bootstrap and install for just C.
(4) On the target, configure to build Ada and run "make" until it
fails.
(5) Copy .s files make in step (2) to the target and redo "make".
However, my suggestion is just to symlink a gnatgcc to be, e.g., /bin/true.
next reply other threads:[~2001-11-30 1:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 8:37 Richard Kenner [this message]
2001-11-29 17:42 ` Richard Kenner
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 5:10 mike stump
2001-11-22 5:23 ` Geert Bosch
2001-11-29 17:10 ` Geert Bosch
2001-11-29 17:04 ` mike stump
2001-11-22 1:04 Geert bosch
2001-11-22 3:59 ` DJ Delorie
2001-11-29 16:46 ` DJ Delorie
2001-11-22 4:51 ` Richard Henderson
2001-11-22 5:01 ` Geert Bosch
2001-11-22 13:07 ` Richard Henderson
2001-11-23 2:33 ` Geert Bosch
2001-11-30 8:40 ` Geert Bosch
2001-11-29 18:37 ` Richard Henderson
2001-11-29 16:57 ` Geert Bosch
2001-11-29 16:52 ` Richard Henderson
2001-11-29 15:23 ` Geert bosch
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=10111300136.AA24820@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).