Re: How to fix 'Could not locate executable on path: gnatmake'

[resander <kresander@yahoo.com>]

On May 7, 4:47 pm, Ludovic Brenta <ludo...@ludovic-brenta.org> wrote:
> Gautier write-only writes on comp.lang.ada:
>
> > Ludovic Brenta wrote:
> > [...]
> >> Or, simply upgrade to Debian :)
>
> > I knew it! It had to happen!
>
> That's because each time I see someone with $PATH or similar
> installation problems, I just smile.  For me, everything works right out
> of the box.  No fuss, no muss.
>
> You made me smile, too :)
>
> --
> Ludovic Brenta.




My addition to the end of the bashrc startup file is:

# the line below is for GNAT GPL Ada
PATH=/usr/gnat/bin:$PATH; export PATH

After execution of bashrc on entry to ken (where I want to develop
programs) the PATH is:

/usr/gnat/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/
bin:/usr/games

Compiler works when I start GPS from the command line (as Ludovic
Brenta Georg Bauhaus predicted), and again as I mentioned before it
does not work when invoked from the gui menu.

BUT

I have just installed GNAP GPL in usr/local and found that GPS
compilation works when GPS is invoked from the gui menu. I would have
expected this to have failed in the same way as above.

So I can just delete the /usr/gnat install directory and remember to
always install into /usr/local and that would be the end of the
problem, but I would like to understand this better.

The GNAT content of /usr/local/bin and /usr/gnat/bin are identical
after installation and yet only one worked.

Could it be that GPS code has the path /usr/local/bin hardwired or is /
usr/local/bin special in some other way?