From: mike stump <mrs@windriver.com>
To: bosch@gnat.com, gcc@gcc.gnu.org
Subject: Re: How to defeat new check for presence of Ada compiler
Date: Thu, 22 Nov 2001 05:10:00 -0000 [thread overview]
Message-ID: <200111300103.RAA24217@kankakee.wrs.com> (raw)
> Date: Thu, 29 Nov 2001 18:23:35 -0500
> From: Geert bosch <bosch@gnat.com>
> To: gcc@gcc.gnu.org
> Since I want to compile GNAT on a new platform, for which I need
> to use the native assembler (no cross-binutils), I want to do that
> by creating the .s files for the Ada sources using a cross-compiler
> and then do the rest of the bootstrap on the target platform.
> This used to be simple, just configure and wait for an error due
> to the missing compiler. Then copy the .s files and that's it.
> But with the recent change to configure, it is not so easy anymore
> to have configure do its job for the ada directory as well.
> Are there any workarounds for this?
Set up a target as (if you choose the right name, it will just work),
and have it be a shell script that rcps (remote copies) the file to
the other machine, and then calls /bin/as (or whatever), and then
copies the results back, and then stores them in the right place.
I did this eons ago. Method should be sound and still work.
Otherwise -save-temps, and AS_FOR_TARGET=true!
If you get something that works for you, consider docing it in the
manual.
WARNING: multiple messages have this Message-ID
From: mike stump <mrs@windriver.com>
To: bosch@gnat.com, gcc@gcc.gnu.org
Subject: Re: How to defeat new check for presence of Ada compiler
Date: Thu, 29 Nov 2001 17:04:00 -0000 [thread overview]
Message-ID: <200111300103.RAA24217@kankakee.wrs.com> (raw)
Message-ID: <20011129170400.2HXlt2WCI9HXEE2uefmE9cGZkzvL0BpjswHgP4eK7GM@z> (raw)
> Date: Thu, 29 Nov 2001 18:23:35 -0500
> From: Geert bosch <bosch@gnat.com>
> To: gcc@gcc.gnu.org
> Since I want to compile GNAT on a new platform, for which I need
> to use the native assembler (no cross-binutils), I want to do that
> by creating the .s files for the Ada sources using a cross-compiler
> and then do the rest of the bootstrap on the target platform.
> This used to be simple, just configure and wait for an error due
> to the missing compiler. Then copy the .s files and that's it.
> But with the recent change to configure, it is not so easy anymore
> to have configure do its job for the ada directory as well.
> Are there any workarounds for this?
Set up a target as (if you choose the right name, it will just work),
and have it be a shell script that rcps (remote copies) the file to
the other machine, and then calls /bin/as (or whatever), and then
copies the results back, and then stores them in the right place.
I did this eons ago. Method should be sound and still work.
Otherwise -save-temps, and AS_FOR_TARGET=true!
If you get something that works for you, consider docing it in the
manual.
next reply other threads:[~2001-11-30 1:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 5:10 mike stump [this message]
2001-11-22 5:23 ` Geert Bosch
2001-11-29 17:10 ` Geert Bosch
2001-11-29 17:04 ` mike stump
-- strict thread matches above, loose matches on Subject: below --
2001-11-22 8:37 Richard Kenner
2001-11-29 17:42 ` Richard Kenner
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=200111300103.RAA24217@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=bosch@gnat.com \
--cc=gcc@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).