Re: no rule to make target gnatlib_and_tools

[u_int32_t <u_int32_t@whocares.com>]

On Sun, 19 Dec 2004 10:56:52 -0800, christov wrote:

> That's very odd.  It usually works fine for me on, say, RH 9.0.
> 
> The top-level configure output is fairly short.  It should say which
> directories (targets) the build is configured for.  It should also let
> you know if it can not find the Ada-enabled gcc.  GNAT 3.15p must be
> before any other compiler in your PATH to use it.  Since FSF gcc 3.3
> was deemed good enough to bootstrap later Ada compilers, the option to
> have seperate Ada and C bootstrap compilers was removed.
> 
> You can also look in /extra/src/build/gcc for gnat1 and gnatbind after
> the bootstrap.  If you can't find those then the build never made an
> Ada compiler.  Gcc will *always* make a C compiler because that is
> needed during the bootstrap process.  I usually explicitly configure C
> anyway just as a reminder.
> 
> Thinking about your symptoms, the most likely thing is that configure
> is not finding the installed GNAT before some other C compiler that
> doesn't know about Ada.

In fact, I do have gnat installed, the "problem" is that it is prefixed
with gnat*. I suppose I could try aliasing gcc=gnatgcc or something like
that as that obviously would have the C compiler built in.

Thanks