This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: How to defeat new check for presence of Ada compiler
- From: mike stump <mrs at windriver dot com>
- To: bosch at gnat dot com, gcc at gcc dot gnu dot org
- Date: Thu, 29 Nov 2001 17:03:31 -0800 (PST)
- Subject: Re: How to defeat new check for presence of Ada compiler
> 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.